[
https://issues.apache.org/jira/browse/SOLR-12902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664187#comment-16664187
]
Anshum Gupta commented on SOLR-12902:
-------------------------------------
[~varunthacker] I'll take a look. I just glanced through this and seemed like a
decent starting point. I've worked on a bunch of things for update/core/schema
side of things, but that is different w.r.t. where it hooks in. Whatever we do,
we should think about how we expose the settings and have them all seem
connected at both query and update side.
> Block Expensive Queries custom Solr component
> ---------------------------------------------
>
> Key: SOLR-12902
> URL: https://issues.apache.org/jira/browse/SOLR-12902
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Tirth Rajen Mehta
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Added a Block Expensive Queries custom Solr component (
> [https://github.com/apache/lucene-solr/pull/47|https://github.com/apache/lucene-solr/pull/477)]
> ) :
> * This search component can be plugged into your SearchHandler if you would
> like to block some well known expensive queries.
> * The queries that are blocked and failed by component currently are deep
> pagination queries as they are known to consume lot of memory and CPU. These
> are
> *
> ** queries with a start offset which is greater than the configured
> maxStartOffset config parameter value
> ** queries with a row param value which is greater than the configured
> maxRowsFetch config parameter value
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
