[jira] Commented: (LUCENE-1642) IndexWriter.addIndexesNoOptimize ignores the compound file setting of the destination index

["John Wang (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LUCENE-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710620#action_12710620 ] 

John Wang commented on LUCENE-1642:
-----------------------------------

2.4.0 branch: IndexWriter.java, method: resolveExternalSegments, line 3072:
  final MergePolicy.OneMerge newMerge = new MergePolicy.OneMerge(segmentInfos.range(i, 1+i), info.getUseCompoundFile());

info.getUseCompoundFile() seems to be wrong, this is on the src index, not the target index, should be getUseCompoundFile() instead.

> IndexWriter.addIndexesNoOptimize ignores the compound file setting of the destination index
> -------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-1642
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1642
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>            Reporter: Yasuhiro Matsuda
>            Priority: Minor
>
> IndexWriter.addIndexesNoOptimize(Directory[]) ignores the compound file setting of the destination index. It is using the compound file flags of segments in the source indexes.
> This sometimes causes undesired increase of the number of files in the destination index when non-compound file indexes are added until merge kicks in.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org