You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jim Ferenczi (JIRA)" <ji...@apache.org> on 2018/09/17 12:41:00 UTC
[jira] [Created] (LUCENE-8505) IndexWriter#addIndices should not
sort indices if they are not already sorted
Jim Ferenczi created LUCENE-8505:
------------------------------------
Summary: IndexWriter#addIndices should not sort indices if they are not already sorted
Key: LUCENE-8505
URL: https://issues.apache.org/jira/browse/LUCENE-8505
Project: Lucene - Core
Issue Type: Improvement
Reporter: Jim Ferenczi
Today IndexWriter#addIndices silently re-sort non-sorted indices when they are added in a sorted index. This is not safe because the sort is done entirely in memory and cannot handle big segments efficiently. This leniency was added because prior to 6.5, segments produced by flushes were not sorted, they had to wait for a merge to apply the index sorting. Now that segments are always sorted (LUCENE-7579) we should remove this ability and throw an error if the sort of the current index does not match with the candidate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org