[LUCENE-6871] Move SpanQueries out of .spans package

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 5.4, 6.0
• Lucene Fields: New
• Assignee: Unassigned
• Reporter: Alan Woodward
• Created: 30/Oct/15 10:51
• Updated: 28/Aug/22 14:45
• Resolved: 20/Mar/19 12:12

Description

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.