Yonik Seeley created LUCENE-7880:
------------------------------------
Summary: 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
