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 wrote:
> I just wonder that: Don't you implement
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 Michae
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 wo
I'd recommend a custom "first-components" SearchComponent. Then it could
simply validate (or adjust) the parameters or throw an exception.
Knowing Tomás - that's probably what he'd really do :)
Erik
On Oct 8, 2013, at 19:34, Tomás Fernández Löbbe wrote:
> I don't know of any OOTB w
I don't know of any OOTB way to do that, I'd write a custom request handler
as you suggested.
Tomás
On Tue, Oct 8, 2013 at 3: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
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
