[
https://issues.apache.org/jira/browse/LUCENE-4975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649650#comment-13649650
]
Shai Erera commented on LUCENE-4975:
------------------------------------
As I said, arguments can be made both ways ... I don't know what's the best way
here. I can see your point, but I don't feel good about having facet depend on
replicator. I see Replicator as a higher-level service that besides providing
the replication framework, also comes pre-built for replicating Lucene stuff. I
don't mind seeing it grow to accommodate other Revision types in the future.
For example, IndexAndTaxonomyRevision is just an example for replicating
multiple indexes together. It can easily be duplicated to replicate few indexes
at once, e.g. a MultiIndexRevision. Where would that object be? Cannot be in
core, so why should IndexAndTaxo be in facet?
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
