[
https://issues.apache.org/jira/browse/LUCENE-7619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826278#comment-15826278
]
ASF subversion and git services commented on LUCENE-7619:
---------------------------------------------------------
Commit 4e4ec082caa7c1fc8fca24ddfb6a8633a4ae9506 in lucene-solr's branch
refs/heads/branch_6x from Mike McCandless
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=4e4ec08 ]
LUCENE-7619: add WordDelimiterGraphFilter (replacing WordDelimiterFilter) to
produce a correct token stream graph when splitting words
> 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.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
