Paul Elschot commented on LUCENE-7398:

The idea is to allow full backward compatibility, as well as more matching 

UNORDERED_LAZY is the current unordered,
UNORDERED_STARTPOS is even simpler, it only uses span start positions, so it 
should be complete.
ORDERED_LAZY is the current ordered,
ORDERED_LOOKAHEAD is in the patch of 14 August 2016,
ORDERED_STARTPOS is also only uses start positions, so it should be complete.

The complete ORDERED and UNORDERED cases that use start and end positions and 
need backtracking are left for later.


> Nested Span Queries are buggy
> -----------------------------
>                 Key: LUCENE-7398
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7398
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/search
>    Affects Versions: 5.5, 6.x
>            Reporter: Christoph Goller
>            Assignee: Alan Woodward
>            Priority: Critical
>         Attachments: LUCENE-7398-20160814.patch, LUCENE-7398.patch, 
> LUCENE-7398.patch, TestSpanCollection.java
> Example for a nested SpanQuery that is not working:
> Document: Human Genome Organization , HUGO , is trying to coordinate gene 
> mapping research worldwide.
> Query: spanNear([body:coordinate, spanOr([spanNear([body:gene, body:mapping], 
> 0, true), body:gene]), body:research], 0, true)
> The query should match "coordinate gene mapping research" as well as 
> "coordinate gene research". It does not match  "coordinate gene mapping 
> research" with Lucene 5.5 or 6.1, it did however match with Lucene 4.10.4. It 
> probably stopped working with the changes on SpanQueries in 5.3. I will 
> attach a unit test that shows the problem.

This message was sent by Atlassian JIRA

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

Reply via email to