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

Dawid Weiss commented on SOLR-2378:
-----------------------------------

Thanks Ryan. Well, I'll just allocate off the heap, hoping it'll fit in TLB.

I will also need a reasonably large list of suggestions to test/benchmark. By 
realistic I mean something that folks actually use in production (terms & 
weights) would be great; a sample of a few hundred thousand terms would be 
probably good enough (?). I can come up with something of my own (based on 
wikipedia or Carrot2 data), but a real data set would be better.

> FST-based Lookup (suggestions) for prefix matches.
> --------------------------------------------------
>
>                 Key: SOLR-2378
>                 URL: https://issues.apache.org/jira/browse/SOLR-2378
>             Project: Solr
>          Issue Type: New Feature
>          Components: spellchecker
>            Reporter: Dawid Weiss
>            Assignee: Dawid Weiss
>              Labels: lookup, prefix
>             Fix For: 4.0
>
>
> Implement a subclass of Lookup based on finite state automata/ transducers 
> (Lucene FST package). This issue is for implementing a relatively basic 
> prefix matcher, we will handle infixes and other types of input matches 
> gradually. Impl. phases:
> - write a DFA based suggester effectively identical to ternary tree based 
> solution right now,
> - baseline benchmark against tern. tree (memory consumption, rebuilding 
> speed, indexing speed; reuse Andrzej's benchmark code)
> - modify DFA to encode term weights directly in the automaton (optimize for 
> onlyMostPopular case)
> - benchmark again
> - add infix suggestion support with prefix matches boosted higher (?)
> - benchmark again
> - modify the tutorial on the wiki [http://wiki.apache.org/solr/Suggester]

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to