[
https://issues.apache.org/jira/browse/LUCENE-4975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649727#comment-13649727
]
Adrien Grand commented on LUCENE-4975:
--------------------------------------
bq. Then maybe we could have sub-modules for specific replication strategies?
To make my point a little clearer, I was suggesting something pretty much like
the analysis module: analyzers that require additional dependencies (such as
icu or morfologik) are in their own sub-module so that you don't need to pull
the ICU or Morfologik JARs if you just want to use LetterTokenizer (which is in
lucene/analysis/common).
Likewise, we could have the interface and the logic to replicate simple (no
sidecar data) indexes in lucene/replicator/common and have sub-modules for
facet (lucene/replicator/facet) or suggesters (lucene/replicator/suggesters).
This may look overkill but at least this would help us keep dependencies clean
between modules.
> 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
