[
https://issues.apache.org/jira/browse/LUCENE-5493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922358#comment-13922358
]
Robert Muir commented on LUCENE-5493:
-------------------------------------
Another reason is that IndexSearcher knows about Sort already. so this would
give us a path if we want a better integration here in the future.
If we did it right, no additional info/apis from the user would be needed other
than setting the mergePolicy at index-time: indexSearcher.search(query, filter,
int, sort) for example could do the right thing for a segment, if the passed in
query-time sort is "covered" by the sort order of the index. But thats for the
future.
> Rename Sorter, NumericDocValuesSorter, and fix javadocs
> -------------------------------------------------------
>
> Key: LUCENE-5493
> URL: https://issues.apache.org/jira/browse/LUCENE-5493
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Assignee: Robert Muir
>
> Its not clear to users that these are for this super-expert thing of
> pre-sorting the index. From the names and documentation they think they
> should use them instead of Sort/SortField.
> These need to be renamed or, even better, the API fixed so they aren't public
> classes.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
