[
https://issues.apache.org/jira/browse/SOLR-12902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16667690#comment-16667690
]
Tirth Rajen Mehta commented on SOLR-12902:
------------------------------------------
Hi [~anshumg], I have added a test-case in the code to explain the scenario in
which the custom component will be helpful. There are 2 parameters that I take
directly in the solrconfig.xml file which provides the user to gain flexibility
in choosing the parameters upfront. Incase, the user forgets to add them in the
solrconfig.xml, the code will pick up default values to handle that case.
> 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]
