You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Christine Poerschke (JIRA)" <ji...@apache.org> on 2017/01/09 12:48:58 UTC
[jira] [Commented] (LUCENE-7624) Consider moving TermsQuery to core
[ https://issues.apache.org/jira/browse/LUCENE-7624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15811696#comment-15811696 ]
Christine Poerschke commented on LUCENE-7624:
---------------------------------------------
bq. ... I think it's a generally useful query, and would fit in perfectly well in core.
I agree. Already (singular) TermQuery is in core and it would be logical for (plural) TermsQuery to be in the same module. Historically (pre LUCENE-6270) TermsQuery used to be TermsFilter which perhaps explains its location in the queries rather than the core module.
> 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
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org