[
https://issues.apache.org/jira/browse/SOLR-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651715#action_12651715
]
Grant Ingersoll commented on SOLR-877:
--------------------------------------
bq. It's not about duplicating effort (implementation), it's about reusing
interface conventions, and what makes the most sense.
True, I see what you mean. For some reason, though, I tend to think of
TermEnum in the terms of lower bound and upper bound instead of offset, b/c
offset implies you are a certain number of items into an array (i.e. foo[10]),
whereas lower bound just feels looser to me. Semantics, I know. As for
term.limit, isn't that faceting duplicating the "rows" parameter?
----
I just committed several changes:
- Added terms.prefix so now the auto-suggest should be possible. See the Wiki
for an example
- Changed upr.incl -> upper.incl and lwr.incl -> lower.incl
- Fixed a but w/ lower.incl = false that skipped the next term even if the
first term was not a match for the input lower bound term.
Committed revision 721681.
> 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.
