Yes, right now this constraint could be implemented in either the web app or Solr. I see now that many of the QTimes on these queries are <10 ms (probably due to caching), so I'm a bit less concerned.
On Wed, Oct 16, 2013 at 2:13 AM, Furkan KAMACI <furkankam...@gmail.com>wrote: > I just wonder that: Don't you implement a custom API that interacts with > Solr and limits such kinds of requestst? (I know that you are asking about > how to do that in Solr but I handle such situations at my custom search > APIs and want to learn what fellows do) > > > 9 Ekim 2013 Çarşamba tarihinde Michael Sokolov < > msoko...@safaribooksonline.com> adlı kullanıcı şöyle yazdı: > > On 10/8/13 6:51 PM, Peter Keegan wrote: > >> > >> Is there a way to configure Solr 'defaults/appends/invariants' such that > >> the product of the 'start' and 'rows' parameters doesn't exceed a given > >> value? This would be to prevent deep pagination. Or would this require > a > >> custom requestHandler? > >> > >> Peter > >> > > Just wondering -- isn't it the sum that you should be concerned about > rather than the product? Actually I think what we usually do is limit both > independently, with slightly different concerns, since. eg start=1, > rows=1000 causes memory problems if you have large fields in your results, > where start=1000, rows=1 may not actually be a problem > > > > -Mike > > >
