[
https://issues.apache.org/jira/browse/LUCENE-7624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15833001#comment-15833001
]
ASF GitHub Bot commented on LUCENE-7624:
----------------------------------------
GitHub user PaulElschot opened a pull request:
https://github.com/apache/lucene-solr/pull/141
Minor corrections, see also LUCENE-7624
LUCENE-7637
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/PaulElschot/lucene-solr lucene7637
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/lucene-solr/pull/141.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #141
----
commit 59d8bd27df50f280e8530e757e946fceaa1cc37a
Author: Paul Elschot <[email protected]>
Date: 2017-01-21T14:32:02Z
Minor corrections, see also LUCENE-7624
----
> 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]
