Chris, I agree, having the ability to make rows something like -1 to bring back everything would be convenient. However, the 2 call approach (q=blah&rows=0 followed by q=blah&rows=numFound) isn't that slow, and does give you more information up front. You can optimize your Array or List<> sizes in advance, you could make sure that it isn't a runaway query and you are about to be overloaded with data, you could split it up into parallel processes, ie:
Thread(q=blah&start=0&rows=numFound/4) Thread(q=blah&start=numFound/4&rows=numFound/4) Thread(q=blah&start=(numFound/4 *2)&rows=numFound/4) Thread(q=blah&start=(numFound/4*3)&rows=numFound/4) (not sure my math is right, did it quickly, but you get the point). Anyway, having that number can be very useful for more than just knowing max results. Ken -- View this message in context: http://lucene.472066.n3.nabble.com/Get-all-results-from-a-solr-query-tp1515125p1516751.html Sent from the Solr - User mailing list archive at Nabble.com.
