[
https://issues.apache.org/jira/browse/LUCENE-8839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16861832#comment-16861832
]
Atri Sharma commented on LUCENE-8839:
-------------------------------------
[~jpountz] I agree that we can open up utility methods for checks like query
types, and those should definitely be done outside searcher code. However, I
think we should let the max clause count still be an intrinsic value belonging
to IndexSearcher (similar to what we allow for BooleanQueries, just not a
global static value). With LUCENE-8811, it should be a much simpler task to set
it per searcher. WDYT?
> Add IndexSearcher Level Query Max Clause Count Limits
> -----------------------------------------------------
>
> Key: LUCENE-8839
> URL: https://issues.apache.org/jira/browse/LUCENE-8839
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Atri Sharma
> Priority: Major
>
> This should allow much better fine-grained control, such as restricting
> complexity of queries on specific indices or users
--
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
