[
https://issues.apache.org/jira/browse/SOLR-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654103#action_12654103
]
Grant Ingersoll commented on SOLR-877:
--------------------------------------
Noble, have you done any performance testing of this approach versus the radix
tree (or other tree/trie approaches)?
AIUI, if you do the tree approach, doesn't that mean you need to build the tree
from all of the terms in a given field? And then what about if you want to go
across multiple fields? Seems like that would be a pretty large footprint. In
some sense, the Term dictionary in Lucene is already very similar to this
structure, except it can't do the character matching like you are proposing
(but it does very efficiently encodes the terms)
> Access to Lucene's TermEnum capabilities
> ----------------------------------------
>
> Key: SOLR-877
> URL: https://issues.apache.org/jira/browse/SOLR-877
> Project: Solr
> Issue Type: New Feature
> Reporter: Grant Ingersoll
> Assignee: Grant Ingersoll
> Priority: Minor
> Fix For: 1.4
>
> Attachments: SOLR-877.patch, SOLR-877.patch, SOLR-877.patch
>
>
> I wrote a simple SearchComponent on the plane the other day that gives access
> to Lucene's TermEnum capabilities. I think this will be useful for doing
> auto-suggest and other term based operations. My first draft is not
> distributed, but it probably should be made to do so eventually.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
