lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shai Erera (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4975) Add Replication module to Lucene
Date Wed, 08 May 2013 12:37:16 GMT


Shai Erera commented on LUCENE-4975:

bq. The bug is that IndexWriter.close() waits for merges and commits. Lets quit kidding ourselves

Not sure I agree .. the bug is real, and if somebody did new IW().commit().close() without
making any change, he might be surprised about that commit too, and also IW would overwrite
any existing file. The only thing "close-not-committing" would solve in this case is that
I won't need to call rollback(), but close(). The bug won't disappear.
> Add Replication module to Lucene
> --------------------------------
>                 Key: LUCENE-4975
>                 URL:
>             Project: Lucene - Core
>          Issue Type: New Feature
>            Reporter: Shai Erera
>            Assignee: Shai Erera
>         Attachments: LUCENE-4975.patch, LUCENE-4975.patch, LUCENE-4975.patch, LUCENE-4975.patch,
LUCENE-4975.patch, LUCENE-4975.patch
> I wrote a replication module which I think will be useful to Lucene users who want to
replicate their indexes for e.g high-availability, taking hot backups etc.
> I will upload a patch soon where I'll describe in general how it works.

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