[
https://issues.apache.org/jira/browse/LUCENE-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797307#comment-13797307
]
Greg Dearing commented on LUCENE-3229:
--------------------------------------
Have been successfully using the provided fix since 3.6. (Thanks ludovic and
Paul).
Since the original patches haven't applied cleanly for a while, I thought I'd
upload the version we've been using. It preserves the logic from Paul
Elschot's version, except re-based against version 4.5 and with some minor
javadoc fixes.
If there's anything else that would be helpful, please comment and I'll see
what I can do.
> 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
> Fix For: 4.6
>
> Attachments: LUCENE-3229.patch, LUCENE-3229.patch, LUCENE-3229.patch,
> SpanOverlap2.diff, SpanOverlap.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.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
