[
https://issues.apache.org/jira/browse/LUCENE-6871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14987031#comment-14987031
]
Alan Woodward commented on LUCENE-6871:
---------------------------------------
Right, but SpanNot and SpanOr will still be separate queries from BooleanQuery.
Moving packages just means that some queries (like Term and Phrase) that can
conceptually be both a standard query and a span query can actually be that.
> Move SpanQueries out of .spans package
> --------------------------------------
>
> Key: LUCENE-6871
> URL: https://issues.apache.org/jira/browse/LUCENE-6871
> Project: Lucene - Core
> Issue Type: Improvement
> Affects Versions: Trunk, 5.4
> Reporter: Alan Woodward
> Attachments: LUCENE-6871.patch
>
>
> SpanQueries are now essentially the same as a standard query, restricted to a
> single field and with an extra scorer type returned by getSpans(). There are
> a number of existing queries that fit this contract, including TermQuery and
> PhraseQuery, and it should be possible to make them SpanQueries as well
> without impacting their existing performance. However, we can't do this
> while SpanQuery and its associated Weight and Spans classes are in their own
> package.
> I'd like to remove the o.a.l.search.spans package entirely, in a few stages:
> 1) Move SpanQuery, SpanWeight, Spans, SpanCollector and FilterSpans to
> o.a.l.search
> 2) Remove SpanTermQuery and merge its functionality into TermQuery
> 3) Move SpanNear, SpanNot, SpanOr and SpanMultiTermQueryWrapper to
> o.a.l.search
> 4) Move the remaining SpanQueries to the queries package
> Then we can look at, eg, making PhraseQuery a SpanQuery, removing
> SpanMTQWrapper and making MultiTermQuery a SpanQuery, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
