[ https://issues.apache.org/jira/browse/LUCENE-6871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Woodward resolved LUCENE-6871. ----------------------------------- Resolution: Won't Fix > 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: 5.4, 6.0 > Reporter: Alan Woodward > Priority: Major > Attachments: LUCENE-6871.patch, 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 (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org