[
https://issues.apache.org/jira/browse/LUCENE-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826675#comment-15826675
]
Michael McCandless commented on LUCENE-5012:
--------------------------------------------
I think we really should advance this: the synonym filter here already handles
incoming graphs correctly, and the token stream API improvements here make it
much easier to consume and create graph token streams. I think this will only
get more important with time, e.g. the new {{WordDelimiterGraphFilter}} now
creates correct graphs, but if you want to run the current
{{SynonymGraphFilter}} after it, it won't work.
That said, there is still a lot of work to make this committable. I think we
need to find a way to make the stage-based analysis components interchangeable
with the current API to give us the freedom to gradually cutover the many
tokenizers and tokenfilters Lucene has today.
> Make graph-based TokenFilters easier
> ------------------------------------
>
> Key: LUCENE-5012
> URL: https://issues.apache.org/jira/browse/LUCENE-5012
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/analysis
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Attachments: LUCENE-5012.patch
>
>
> SynonymFilter has two limitations today:
> * It cannot create positions, so eg dns -> domain name service
> creates blatantly wrong highlights (SOLR-3390, LUCENE-4499 and
> others).
> * It cannot consume a graph, so e.g. if you try to apply synonyms
> after Kuromoji tokenizer I'm not sure what will happen.
> I've thought about how to fix these issues but it's really quite
> difficult with the current PosInc/PosLen graph representation, so I'd
> like to explore an alternative approach.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
