[ 
https://issues.apache.org/jira/browse/SOLR-12902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664178#comment-16664178
 ] 

Varun Thacker commented on SOLR-12902:
--------------------------------------

Hi Tirth,

I've left a few comments on the PR . I think continuing the review on the PR 
would be the best approach

Future ideas could be block facet requests with rows=-1  , wildcards in the 
middle ( you've already mentioned leading wildcards in the docs )  etc.

 

[~anshumg]  @Tomas do you guys have any thoughts on this approach?

> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to