[ https://issues.apache.org/jira/browse/LUCENE-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13604777#comment-13604777 ]
Robert Muir commented on LUCENE-4845: ------------------------------------- Wouldnt the straightforward impl be to put the suffixes of the suggestions into the FST? so for "this is a test" you also add "is a test", "a test", ... I feel like this could be done with just a tokenfilter used only at build-time + analyzingsuggester, and would be more performant. > Add AnalyzingInfixSuggester > --------------------------- > > Key: LUCENE-4845 > URL: https://issues.apache.org/jira/browse/LUCENE-4845 > Project: Lucene - Core > Issue Type: Improvement > Components: modules/spellchecker > Reporter: Michael McCandless > Assignee: Michael McCandless > Fix For: 5.0, 4.3 > > Attachments: infixSuggest.png, LUCENE-4845.patch > > > Our current suggester impls do prefix matching of the incoming text > against all compiled suggestions, but in some cases it's useful to > allow infix matching. E.g, Netflix does infix suggestions in their > search box. > I did a straightforward impl, just using a normal Lucene index, and > using PostingsHighlighter to highlight matching tokens in the > suggestions. > I think this likely only works well when your suggestions have a > strong prior ranking (weight input to build), eg Netflix knows > the popularity of movies. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org