[
https://issues.apache.org/jira/browse/LUCENE-7624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823710#comment-15823710
]
ASF subversion and git services commented on LUCENE-7624:
---------------------------------------------------------
Commit 929fba34d95a9d3b168b38839203f2835be1060f in lucene-solr's branch
refs/heads/branch_6_4 from [~jpountz]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=929fba3 ]
Revert "LUCENE-7624: Move TermsQuery into core as TermInSetQuery"
This reverts commit 8511f9e6991679f71e7a82c6ef9cf1b774d090aa.
> 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.5
>
> 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]
