http://www.google.com/search?q=%229999999..99999999999999999...
Seems the Unix Bourne shell is seeping in - single quotes are for real, double quotes allow param substitution ...
This range works: 99999..1000000
Increment that first digit and it will fail though.
I'm a bit confused to see this so highly upvoted. I'm not sure you understand what MapReduce is for. MapReduce is not a technology designed for executing a search query in under 100ms, it's for massive data processing jobs. MapReduce is what you would use to do to prepare an index, not to query it.
> You can imagine why that's a bad idea, and some aggressive timeouts are probably what stop it from going too far.
As you yourself noted, this is blocked to prevent people from searching for SSN/credit card/etc. dumps.
11..22 would be to search for all integers between 11 and 22.
The effect is that the search is too broad. The problem is more likely to be that the range search is a mapreduce that performs a search for each item in the range.
You can imagine why that's a bad idea, and some aggressive timeouts are probably what stop it from going too far.
Plus the numbers in the range of the OP search are likely to fall in the ranges of sensitive numbers, credit cards being the most sensitive... which are likely to be explicitly blocked.