[
https://issues.apache.org/jira/browse/LUCENE-4975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13650731#comment-13650731
]
Shai Erera commented on LUCENE-4975:
------------------------------------
I'm having reservations about creating a replicator/facet module which contains
2 classes ... Maybe we should proceed with the code as-is, and then refactor if
it creates a problem, or the module grows? Perhaps the breakout won't be to
replicator/common and replicator/facet but to replicator/infra (or common) and
replicator/extras which will serve like a catchall for other modules too (e.g.
facet, suggest).
Another way is to break out replicator to common and framework/infra/impl such
that common contains only whatever other modules require to compile against
(i.e Revision, ReplicationHandler, maybe Replicator). Then we can add the facet
replication code to facet/ with a dependency on replicator/common.
But really, I think we should just get it in and start to work with it, have
deeper reviews and refactor as we go.
> Add Replication module to Lucene
> --------------------------------
>
> Key: LUCENE-4975
> URL: https://issues.apache.org/jira/browse/LUCENE-4975
> 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
>
>
> 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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
