[
https://issues.apache.org/jira/browse/LUCENE-7398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Elschot updated LUCENE-7398:
---------------------------------
Attachment: LUCENE-7398-20160925.patch
Patch of 25 Sep 2016.
Compared to the previous patch, this removes the ORDERED_STARTPOS case, because
I don't know whether that is needed.
Also this restores backward compatibility.
Compared to master, this has:
Four MatchNear methods, two are the current ones, they are called ORDERED_LAZY
and UNORDERED_LAZY, and these are used when the current builder and
constructors use a boolean ordered argument.
The third case is ORDERED_LOOKAHEAD, which is from the patch of 18 August.
The last case is UNORDERED_STARTPOS, which is simpler than UNORDERED_LAZY,
hopefully a little faster, and with better completeness of the result.
Javadocs for all four cases have been added.
All test cases from here have been added, and where necessary they have been
modified to use ORDERED_LOOKAHEAD and to not do span collection. These tests
pass.
For the last case, UNORDERED_STARTPOS, no test cases have been added yet. This
is still to be done. Does anyone have more difficult cases?
Minor point: the collect() method was moved to the superclass ConjunctionSpans.
Feedback welcome, especially on the javadocs of SpanNearQuery.MatchNear.
Instead of adding backtracking methods, it might be better to do counting of
input spans in a matching window. I'm hoping that the UNORDERED_STARTPOS case
can be extended for that. Any ideas there?
> 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-20160924.patch,
> LUCENE-7398-20160925.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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
