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

Paul Elschot commented on LUCENE-7398:
--------------------------------------

[~mikemccand], the patch is as you stated, and having MatchNear as an enum to 
choose the matching method is easy to extend.
I would not mind to have some more opinions on whether the progress is enough 
to actually add the code.

I know this MG4J paper and it could well be that theorem 11 in there proves 
that no lazy algorithm is possible for the general case with more than 2 
subqueries, but for now I cannot really follow their terminology.  In 
particular I'd like to know whether or not these efficient algorithms 
correspond to the current lazy implementations in Lucene. I'm hoping that they 
do not, because then there might be some room for improvement in Lucene without 
losing speed.

As [~gol...@detego-software.de] stated above:
bq.  I want a higher score if the user-query matches for more than one variant
I don't think the ORDERED_LOOKAHEAD of the patch does  that, because it only 
matches one variant.
I hope that there is a non backtracking implementation that can do this, but 
I'm not sure.



> 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, 
> 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

Reply via email to