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 Mon, 06 May 2013 11:48:16 GMT


Shai Erera commented on LUCENE-4975:

Ok, so there are 3 options I see: (1) have Replicator depend on Facet (and in the future on
other modules), (2) have Facet depend on Replicator and (3) move Revision and ReplicationHandler
(interfaces) someplace else, core or a new module we call 'commons' and Replicator and Facet
depend on it. Tests though will need to depend on replicator though, since they need ReplicationClient.

BTW, the jetty dependencies are tests only, but I don't know how to make ivy resolve the dependencies
just for tests. The only thing replicator depends on is servlet-api, for ReplicationService
and httpclient for ReplicationClient. I think these need to remain in the module ...

If we made Facet depend on Replicator (I'm not totally against it), would that require you
to have lucene-replicator.jar on the classpath, even if you don't use replication? If not,
then perhaps this dependency isn't so bad ... it's just a compile-time dependency. Tests will
still need to depend on replicator for runtime, but that's ok I think.
> 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,
> 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