[
https://issues.apache.org/jira/browse/LUCENE-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14011085#comment-14011085
]
Simon Willnauer commented on LUCENE-5708:
-----------------------------------------
part of the problem is that we holding IW state on MergePolicy and
MergeScheduler. Both classes should get the IW passed to the relevant methods
so we can share them across as many instances we want...
> Remove IndexWriterConfig.clone
> ------------------------------
>
> Key: LUCENE-5708
> URL: https://issues.apache.org/jira/browse/LUCENE-5708
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/index
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 4.9, 5.0
>
> Attachments: LUCENE-5708.patch, LUCENE-5708.patch
>
>
> We originally added this clone to allow a single IWC to be re-used against
> more than one IndexWriter, but I think this is a mis-feature: it adds
> complexity to hairy classes (merge policy/scheduler, DW thread pool, etc.), I
> think it's buggy today.
> I think we should just disallow sharing: you must make a new IWC for a new
> IndexWriter.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
