[
https://issues.apache.org/jira/browse/LUCENE-7880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16056272#comment-16056272
]
Erick Erickson commented on LUCENE-7880:
----------------------------------------
bq: It wouldn't be an issue if it was a cluster setting? What is the value of
letting one user generate huge boolean queries and prevent others?
This is where the focus on making it configurable per-query is confusing things
a bit I think. Making it per-query just provides a way to get around the static
nature of the variable and allow limits on a per-core basis is how I've been
interpreting it. And why I suggested thinking of it from a clean-slate
perspective.
Practically what I want to see is a way that each core can have a different
setting that's respected. I don't care if it's per-query or per-core. In the
Solr world at least it's becoming quite common for there to be replicas (cores)
from multiple collections hosted in the same JVM which may have very different
usage patterns. It may make sense that one collection has a much different
limit than the others in that case, which we can't do now.
And it's quite easy to blow past the 1024 limit. It doesn't even take a
horribly complex query when you start spreading it across 100 fields.
> 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]
