[
https://issues.apache.org/jira/browse/LUCENE-7880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16053001#comment-16053001
]
Yonik Seeley commented on LUCENE-7880:
--------------------------------------
bq. This is not the only arbitrary limit we have. For instance terms can't be
greater than 32KB and you can only use edit distances of 1 or 2 with FuzzyQuery.
At least some of these upper limits are certainly not arbitrary (and hence not
configurable). AFAIK, simply increasing these numbers would not result in
working code, hence the limits represent real technical limitations. IIRC, the
history behind the 32KB is that the length was packed in an java char (16 bits).
> 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]
