[jira] [Commented] (LUCENE-3229) SpanNearQuery: ordered spans should not overlap

["ludovic Boutros (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LUCENE-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212492#comment-14212492 ] 

ludovic Boutros commented on LUCENE-3229:
-----------------------------------------

Thank you Erik.

> SpanNearQuery: ordered spans should not overlap
> -----------------------------------------------
>
>                 Key: LUCENE-3229
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3229
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/search
>    Affects Versions: 3.1
>         Environment: Windows XP, Java 1.6
>            Reporter: ludovic Boutros
>            Assignee: Erik Hatcher
>             Fix For: 4.10.3, 5.0, Trunk
>
>         Attachments: LUCENE-3229.patch, LUCENE-3229.patch, LUCENE-3229.patch, LUCENE-3229.patch, LUCENE-3229.patch, SpanOverlap.diff, SpanOverlap2.diff, SpanOverlapTestUnit.diff
>
>
> While using Span queries I think I've found a little bug.
> With a document like this (from the TestNearSpansOrdered unit test) :
> "w1 w2 w3 w4 w5"
> If I try to search for this span query :
> spanNear([spanNear([field:w3, field:w5], 1, true), field:w4], 0, true)
> the above document is returned and I think it should not because 'w4' is not after 'w5'.
> The 2 spans are not ordered, because there is an overlap.
> I will add a test patch in the TestNearSpansOrdered unit test.
> I will add a patch to solve this issue too.
> Basicaly it modifies the two docSpansOrdered functions to make sure that the spans does not overlap.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org