[
https://issues.apache.org/jira/browse/LUCENE-7568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferenczi Jim updated LUCENE-7568:
---------------------------------
Attachment: LUCENE-7568.patch
Here is a first patch that detects if an index is already sorted and makes this
information available through MergeState. This information is then used by all
the merge strategy to activate (or not) some optimizations.
> Optimize merge when index sorting is used but the index is already sorted
> -------------------------------------------------------------------------
>
> Key: LUCENE-7568
> URL: https://issues.apache.org/jira/browse/LUCENE-7568
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/index
> Reporter: Ferenczi Jim
> Attachments: LUCENE-7568.patch
>
>
> When the index sorting is defined a lot of optimizations are disabled during
> the merge. For instance the bulk merge of the compressing stored fields is
> disabled since documents are not merged sequentially. Though it can happen
> that index sorting is enabled but the index is already in sorted order (the
> sort field is not filled or filled with the same value for all documents). In
> such case we can detect that the sort is not needed and activate the merge
> optimization.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
