[
https://issues.apache.org/jira/browse/LUCENE-9484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190053#comment-17190053
]
ASF subversion and git services commented on LUCENE-9484:
---------------------------------------------------------
Commit a7bdc6893e21954ed9f6d8bce256a4a9c917310b in lucene-solr's branch
refs/heads/branch_8x from Simon Willnauer
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=a7bdc68 ]
LUCENE-9484: Allow sorting an index after the fact (#1789)
Today we need to decide on an index sorting before we create the index.
In some situations it might make a lot of sense to sort an index afterwards
when the index doesn't change anymore or to compress older indices.
This change adds the ability to wrap readers from an unsorted index and merge it
into a sorted index by using IW#addIndices.
> Allow index sorting to happen after the fact
> --------------------------------------------
>
> Key: LUCENE-9484
> URL: https://issues.apache.org/jira/browse/LUCENE-9484
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Simon Willnauer
> Priority: Major
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> I did look into sorting an index after it was created and found that with
> some smallish modifications we can actually allow that by piggibacking on
> SortingLeafReader and addIndices in a pretty straight-forward and simple way.
> With some smallish modifications / fixes to SortingLeafReader we can just
> merge and unsorted index into a sorted index using a fresh index writer.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
