[
https://issues.apache.org/jira/browse/LUCENE-7848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16053875#comment-16053875
]
Jim Ferenczi commented on LUCENE-7848:
--------------------------------------
Hi David,
Sorry I am also on vacations this week but looking at your example it seems
that it's a problem with graph token in general. If you have side paths with
different length at indexing time you need to use the flatten graph filter.
Though it will not be able to index the correct positions for this example
since "xxx,special" and "xxx", "special" should be indexed as a graph and
Lucene does not handle graph at indexing time. I wonder why your manual query
works, I might be missing something but this query should also not work unless
you used another configuration for the WDGF (preserve original = false for
instance should work at indexing time) ?
> QueryBuilder.analyzeGraphPhrase does not handle gaps correctly
> --------------------------------------------------------------
>
> Key: LUCENE-7848
> URL: https://issues.apache.org/jira/browse/LUCENE-7848
> Project: Lucene - Core
> Issue Type: Bug
> Affects Versions: 6.5, 6.6
> Reporter: Jim Ferenczi
> Attachments: capture-3.png, LUCENE-7848.patch, LUCENE-7848.patch
>
>
> Position increments greater than 1 are ignored when the query builder creates
> a graph phrase query.
> Instead it should use SpanNearQuery.addGap for pos incr > 1.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
