[
https://issues.apache.org/jira/browse/LUCENE-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand updated LUCENE-2880:
---------------------------------
Attachment: LUCENE-2880.patch
Here is an updated patch that moves the method to the Spans class as suggested.
SpanTermQuery now scores like TermQuery and an ordered SpanNearQuery scores
like a PhraseQuery where all terms are at consecutive positions (the common
case).
> SpanQuery scoring inconsistencies
> ---------------------------------
>
> Key: LUCENE-2880
> URL: https://issues.apache.org/jira/browse/LUCENE-2880
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Fix For: 4.9, Trunk
>
> Attachments: LUCENE-2880.patch, LUCENE-2880.patch
>
>
> Spinoff of LUCENE-2879.
> You can see a full description there, but the gist is that SpanQuery sums up
> freqs with "sloppyFreq".
> However this slop is simply spans.end() - spans.start()
> For a SpanTermQuery for example, this means its scoring 0.5 for TF versus
> TermQuery's 1.0.
> As you can imagine, I think in practical situations this would make it
> difficult for SpanQuery users to
> really use SpanQueries for effective ranking, especially in combination with
> non-Spanqueries (maybe via DisjunctionMaxQuery, etc)
> The problem is more general than this simple example: for example
> SpanNearQuery should be consistent with PhraseQuery's slop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
