[
https://issues.apache.org/jira/browse/LUCENE-7624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823709#comment-15823709
]
Adrien Grand commented on LUCENE-7624:
--------------------------------------
bq. Allowing more than one field for the terms also has an advantage in that
only one doc id set will be built for all the terms.
This is correct, but I think this is a very rare use-case? On the other end,
requiring a single field would simplify things I think. It would be more
consistent with other queries, eg. {{PointInSetQuery}} or would allow to
rewrite to an {{AutomatonQuery}} if that proves helpful in some cases (which
also works on a single field).
> Consider moving TermsQuery to core
> ----------------------------------
>
> Key: LUCENE-7624
> URL: https://issues.apache.org/jira/browse/LUCENE-7624
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Alan Woodward
> Assignee: Alan Woodward
> Fix For: master (7.0), 6.4
>
> Attachments: LUCENE-7624.patch
>
>
> TermsQuery current sits in the queries module, but it's used in both
> spatial-extras and in facets, and currently is the only reason that the
> facets module has a dependency on queries. I think it's a generally useful
> query, and would fit in perfectly well in core.
> This would also allow us to explore rewriting BooleanQuery to TermsQuery to
> avoid the max-clauses limit
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
