[
https://issues.apache.org/jira/browse/LUCENE-7615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Elschot updated LUCENE-7615:
---------------------------------
Attachment: LUCENE-7615.patch
Patch of 2 Jan 2017.
This can be used as proximity subquery whenever SynonymQuery is used now, i.e.
for synonym terms.
I think this improves span scoring somewhat, see the tests and the test output
when uncommenting showQueryResults for the test cases with two terms.
Implementation:
SynonymQuery exposes new methods getField() and SynonymWeight.getSimScorer()
for use in SpanSynonymQuery.
Improved use of o.a.l.index.Terms and TermsEnum in SynonymQuery, at most a
single TermsEnum will be used.
Aside: how about renaming Terms to FieldTerms?
This takes DisjunctionSpans out of SpanOrQuery.
This adds SynonymSpans as (an almost empty) subclass of DisjunctionSpans, for
later further scoring improvement.
PHRASE_TO_SPAN_TERM_POSITIONS_COST is used from SpanTermQuery and made package
private there.
> SpanSynonymQuery
> ----------------
>
> Key: LUCENE-7615
> URL: https://issues.apache.org/jira/browse/LUCENE-7615
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/search
> Affects Versions: master (7.0)
> Reporter: Paul Elschot
> Priority: Minor
> Attachments: LUCENE-7615.patch
>
>
> A SpanQuery that tries to score as SynonymQuery.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
