lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrien Grand (JIRA)" <>
Subject [jira] [Commented] (LUCENE-7880) Make boolean query clause limit configurable per-query
Date Sat, 17 Jun 2017 18:47:00 GMT


Adrien Grand commented on LUCENE-7880:

I think of the max clause count as something that should never be changed. What is the use-case
for having more than 1024 clauses? It sounds like the user is using a {{BooleanQuery}} when
he should actually use a {{TermInSetQuery}}? I am not a fan of adding a per-{{BooleanQuery}}
{{maxClauseCount}}. Moreover it feels like an unnecessary API to me: users can already check
the number of clauses by themselves, which is not harder than calling a setter?

> Make boolean query clause limit configurable per-query
> ------------------------------------------------------
>                 Key: LUCENE-7880
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message