lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "selckin (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4876) IndexWriterConfig.clone should clone the MergeScheduler
Date Fri, 26 Jul 2013 08:03:49 GMT


selckin commented on LUCENE-4876:

This is also encouraging to just 'return this' from clone() in DeletionPolicy, it is how i
fixed my app, how solr fixed it, and elasticsearch does it as well, so for future changes
you can't even assume the clone is being done, not to mention how cruel it is to expose clone
semantics on end-users

> IndexWriterConfig.clone should clone the MergeScheduler
> -------------------------------------------------------
>                 Key: LUCENE-4876
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Adrien Grand
>            Assignee: Adrien Grand
>             Fix For: 4.3
>         Attachments: LUCENE-4876.patch, LUCENE-4876.patch, LUCENE-4876.patch
> ConcurrentMergeScheduler has a List<MergeThread> member to track the running merging
threads, so IndexWriterConfig.clone should clone the merge scheduler so that both IndexWriterConfig
instances are independant.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message