You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2014/05/30 11:28:02 UTC

[jira] [Reopened] (LUCENE-5708) Remove IndexWriterConfig.clone

     [ https://issues.apache.org/jira/browse/LUCENE-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Muir reopened LUCENE-5708:
---------------------------------


Can we remove the "fix test bugs" commits and fix the true underlying issue?

Tests arent testing what they should, we need to fix the disease or back this change out.

> 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, 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org