[
https://issues.apache.org/jira/browse/LUCENE-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592301#comment-13592301
]
David Smiley commented on LUCENE-3918:
--------------------------------------
bq. Global ordering over a multi-segment index seems less useful than the local
per-segment ordering - after all, the main use cases are compression
improvements and early termination strategies, both of which operate on a
per-segment basis.
Those are two "main use-cases" but there is a third that (to me) is far more
important than either -- locality of reference. Retrieving documents near each
other (according to the configured sort order) should ideally have their stored
fields data very close together. The early-termination use-case is clearly
important to you but is not the goal of LUCENE-4752.
> Port index sorter to trunk APIs
> -------------------------------
>
> Key: LUCENE-3918
> URL: https://issues.apache.org/jira/browse/LUCENE-3918
> Project: Lucene - Core
> Issue Type: Task
> Components: modules/other
> Affects Versions: 4.0-ALPHA
> Reporter: Robert Muir
> Fix For: 4.2, 5.0
>
> Attachments: LUCENE-3918.patch, LUCENE-3918.patch, LUCENE-3918.patch,
> LUCENE-3918.patch, LUCENE-3918.patch, LUCENE-3918.patch, LUCENE-3918.patch,
> LUCENE-3918.patch
>
>
> LUCENE-2482 added an IndexSorter to 3.x, but we need to port this
> functionality to 4.0 apis.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
