[
https://issues.apache.org/jira/browse/LUCENE-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710680#action_12710680
]
Michael McCandless commented on LUCENE-1642:
--------------------------------------------
Good catch! That's in the resolveExternalSegments method, which simply copies
over (one for one) any segments from the source index that didn't "need"
merging according to the merge policy. Were there any other places in
addIndexesNoOptimize where we don't preserve CFS properly?
Yasuhiro/John, could you work up a unit test showing the problem, w/ patch
showing that the test passes?
> 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
> Fix For: 2.9
>
>
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
