[
https://issues.apache.org/jira/browse/LUCENE-7880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055078#comment-16055078
]
David Smiley commented on LUCENE-7880:
--------------------------------------
By the way, this {{maxBooleanClauseCount}} is, I think, extremely similar to
{{maxDeterminizeStates}} for AutomatonQuery (thus WildCardQuery, RegexpQuery).
Both ideas are self-imposed limits that _usually_ don't need to be increased
beyond the defaults but cases happen. In both cases, a RuntimeException
derivative is thrown if the limit is exceeded. maxDeterminizeStates is
configurable for the query instance, and the setting is configurable in the
classic query parser's QueryParserBase. maxBooleanClauseCount has neither.
Why the difference [~jpountz]?
> Make boolean query clause limit configurable per-query
> ------------------------------------------------------
>
> Key: LUCENE-7880
> URL: https://issues.apache.org/jira/browse/LUCENE-7880
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Yonik Seeley
>
> As we know, the magic BooleanQuery.maxClauseCount has bitten many people over
> time.
> It's also a static, which really hurts multi-tenancy (i.e. we can't have
> different settings for different users, clients, or use-cases).
> If we want to keep this static as a default, then at least we should allow it
> to be overridden on a per-query basis when we know it is the desired behavior
> and not a bug.
> Perhaps the simplest way to achieve this would be a setter on
> BooleanQuery.Builder that configures the limit for that instance only?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
