[
https://issues.apache.org/jira/browse/SOLR-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651717#action_12651717
]
Yonik Seeley commented on SOLR-877:
-----------------------------------
For the purposes of this component, I think of TermEnum as an implementation,
not the interface.... people will eventually want to do things like sort by
high docfreq (just as in faceting), or only list terms above a certain count,
or only list terms matching a certain pattern, etc. All of these can make
sense since we can do it more efficiently closer to the data.
bq. I tend to think of TermEnum in the terms of lower bound and upper bound
instead of offset
Right, offset doesn't make as much sense with the current semantics (but it
might later).
bq. As for term.limit, isn't that faceting duplicating the "rows" parameter?
Yes, we unfortunately have two ways of specifying this ("rows" and "limit"). I
think limit is the better name though (and this will be highly associated with
faceting in people's mind I think).
> 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
>
>
> 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.
