[
https://issues.apache.org/jira/browse/LUCENE-8845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16860252#comment-16860252
]
Jim Ferenczi commented on LUCENE-8845:
--------------------------------------
{quote}
2) I think this is covered by the javadocs and the 'expert' marking. Some users
really do need to see all expansions, and if they're aware of the trade-offs
involved then I don't think we need any further hard caps.
{quote}
I think we should try to prevent users to shoot themselves in the foot. IMO
this is more important than for other queries because reaching the limit throw
an error so I expect that users raise the limit until they find a number that
work for all queries. Can we add an hard limit equals to max_boolean_clause ?
This would be consistent with the discussion in
https://issues.apache.org/jira/browse/LUCENE-8811 that should also check the
number of sources in an interval query ?
> Allow maxExpansions to be set on multi-term Intervals
> -----------------------------------------------------
>
> Key: LUCENE-8845
> URL: https://issues.apache.org/jira/browse/LUCENE-8845
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Alan Woodward
> Assignee: Alan Woodward
> Priority: Major
> Fix For: 8.2
>
> Attachments: LUCENE-8845.patch
>
>
> MultiTermIntervalsSource has a maxExpansions parameter which is always set to
> 128 by the factory methods Intervals.prefix() and Intervals.wildcard(). We
> should keep 128 as the default, but also add additional methods that take a
> configurable maximum.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
