You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2017/03/01 13:13:45 UTC

[jira] [Commented] (LUCENE-7619) Add WordDelimiterGraphFilter

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

Michael McCandless commented on LUCENE-7619:
--------------------------------------------

Hi [~infodroids], besides WDGF itself, there have also been a number of changes to the query parser, to properly consume a graph and build the correct queries, e.g. LUCENE-7702, LUCENE-7699, LUCENE-7698, LUCENE-7638, etc.

It may be simpler for you to test a snapshot build of Lucene 6.5.0?

> Add WordDelimiterGraphFilter
> ----------------------------
>
>                 Key: LUCENE-7619
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7619
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: master (7.0), 6.5
>
>         Attachments: after.png, before.png, LUCENE-7619.patch, LUCENE-7619.patch, LUCENE-7619.patch
>
>
> Currently, {{WordDelimiterFilter}} doesn't try to set the {{posLen}} attribute and so it creates graphs like this:
> !before.png!
> but with this patch (still a work in progress) it creates this graph instead:
> !after.png!
> This means (today) positional queries when using WDF at search time are buggy, but since we fixed LUCENE-7603, with this change here you should be able to use positional queries with WDGF.
> I'm also trying to produce holes properly (removes logic from the current WDF that swallows a hole when whole token is just delimiters).
> Surprisingly, it's actually quite easy to tweak WDF to create a graph (unlike e.g. {{SynonymGraphFilter}}) because it's already creating the necessary new positions, and its output graph never has side paths, except for single tokens that skip nodes because they have {{posLen > 1}}.  I.e. the only fix to make, I think, is to set {{posLen}} properly.  And it really helps that it does its own "new token buffering + sorting" already.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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