[
https://issues.apache.org/jira/browse/SOLR-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654110#action_12654110
]
Grant Ingersoll commented on SOLR-877:
--------------------------------------
bq. So are you advocating deprecating facet.limit and adding facet.rows,
or that aligning the APIs doesn't matter in this case?
I don't know. Does every param need to be consistent? If that is the case,
then I guess we should either decide on rows or limit across all of them.
Otherwise, I mean, all of these end up having a prefix attached to them (i.e.
terms.rows), so it may not be a big deal, either. I'm fine either way, I
guess. Your call.
> 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.
