[
https://issues.apache.org/jira/browse/SOLR-12902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664209#comment-16664209
]
Varun Thacker commented on SOLR-12902:
--------------------------------------
Thanks Anshum! In the approach Tirth has taken , it's a search component. So to
configure what needs to be blocked one would need to configure the "defaults"
section of a request handler.
Would this model be consistent with the related hooks that you're referring to?
> 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]
