[
https://issues.apache.org/jira/browse/SOLR-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653201#action_12653201
]
Noble Paul commented on SOLR-877:
---------------------------------
autosuggest is a very commonly used feature. And when they are used , the hits
are just too many.
we can add extra options to optimize or not (say memTree=true/false).
If the option is set we can build a the data structure . Potentially this tree
can consume a lot of memory if there are too many terms . Users must have an
option to turn it off.
The feature may be added with faceting component or the TermComponent. The
problem here is that these components are already overloaded.with features.
Adding this small option into these can cause more confusion.
IMHO we should not pack too many features into one component unless we are sure
that they are mostly used together. (For instance faceting and autosuggest are
rarely done as a part of one request ).It would be better to write separate
components for each functionality . Internally the components can share code
and the users can mix and match if they need to
> 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.
