You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/02/07 13:04:41 UTC
[jira] [Commented] (LUCENE-7568) Optimize merge when index sorting
is used but the index is already sorted
[ https://issues.apache.org/jira/browse/LUCENE-7568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855935#comment-15855935 ]
ASF subversion and git services commented on LUCENE-7568:
---------------------------------------------------------
Commit 37b75bef3f39840227f85aa5c330337fd101b003 in lucene-solr's branch refs/heads/master from [~jim.ferenczi]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=37b75be ]
LUCENE-7568: Fix test that should never create segments with a single document.
> 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: Jim Ferenczi
> Fix For: master (7.0), 6.4
>
> Attachments: LUCENE-7568.patch, 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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org