[
https://issues.apache.org/jira/browse/LUCENE-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14595555#comment-14595555
]
Adrien Grand commented on LUCENE-6596:
--------------------------------------
Thanks for the javadocs correction.
+1 on making them more consistent, it also looks better to use the same formula
to compute whether there is a match and the score.
One thing I'm wondering about is if we should go even further and sum up the
widths of the holes in-between consecutive spans? For instance, if I understand
correctly, a SpanNearQuery over A, B, C in the following configuration would be
considered a perfect match because of its total span length, even though it has
holes:
||Sub span query||start pos||end pos||
|A|0|1|
|B|10|20|
|C|11|21|
> Make width of unordered near spans consistent with ordered
> ----------------------------------------------------------
>
> Key: LUCENE-6596
> URL: https://issues.apache.org/jira/browse/LUCENE-6596
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/search
> Affects Versions: Trunk
> Reporter: Paul Elschot
> Priority: Minor
> Fix For: Trunk
>
> Attachments: LUCENE-6596.patch
>
>
> Use actual slop for width in NearSpansUnordered.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
