[
https://issues.apache.org/jira/browse/LUCENE-6766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255371#comment-15255371
]
Michael McCandless commented on LUCENE-6766:
--------------------------------------------
This looks like a great patch! Probably we can make {{SortingLeafReader}}
private?
I think it's OK to restrict the allowed {{SortField}} that we need to support
and serialize/deserialize?
Can we fix IW to insist on open that the incoming index sort matches whatever
the current index has (if the current index exists)?
Since this patch, we moved {{SlowCompositeReaderWrapper}} out of core ... I
wonder if we can 1) fix flush to also write new segments in correct sort order,
and 2) fix default merge implementation to look at sort order? Merging should
be an efficient merge sort (vs. what {{SortingLeafReader}} on top of
{{SlowCompositeReaderWrapper}} does today).
> Make index sorting a first-class citizen
> ----------------------------------------
>
> Key: LUCENE-6766
> URL: https://issues.apache.org/jira/browse/LUCENE-6766
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Priority: Minor
> Attachments: LUCENE-6766.patch
>
>
> Today index sorting is a very expert feature. You need to use a custom merge
> policy, custom collectors, etc. I would like to explore making it a
> first-class citizen so that:
> - the sort order could be configured on IndexWriterConfig
> - segments would record the sort order that was used to write them
> - IndexSearcher could automatically early terminate when computing top docs
> on a sort order that is a prefix of the sort order of a segment (and if the
> user is not interested in totalHits).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
