Should it be acceptable to have a "rows" parameter larger than Integer.MAX_VALUE?

[Shawn Heisey]

I've come across something and I wonder if it should be considered a bug.
If a value larger than Integer.MAX_VALUE is sent with the "rows" 
parameter, Solr will immediately throw an exception:

org.apache.solr.common.SolrException: For input string: "3000000000"

It would be perfectly valid (though probably have terrible performance) 
to expect a value like that with distributed indexes.  The individual 
shard subqueries of course could never go that high.

This error also occurs in the cloud example with a distributed index.

Should this be considered a bug, or are we OK with current behavior?

Thanks,
Shawn