IndexRevision uses the IndexWriter for deleting unused files when the revision is released, as well as to obtain the SnapshotDeletionPolicy.
I think that you will need to implement two things on the "client" side: * Revision, which doesn't use IndexWriter. * Replicator which keeps track of how many refs a file has (basically what IndexFileDeleter does) Then you could setup any node in the middle to be both a client and a server. Would be interesting to explore that. Would you like to open an issue? And maybe even try to come up w/ a patch? Shai On Tue, Apr 8, 2014 at 1:05 PM, Michael McCandless < luc...@mikemccandless.com> wrote: > It's not safe also opening an IndexWriter on the client side. > > But I agree, supporting tree topology would make sense; it seems like > we just need a way for the ReplicationClient to also be a Replicator. > It seems like it should be possible, since it's clearly aware of the > SessionToken it's pulled from the original Replicator. > > Mike McCandless > > http://blog.mikemccandless.com > > > On Tue, Apr 8, 2014 at 3:42 AM, Christoph Kaser <lucene_l...@iconparc.de> > wrote: > > Hi all, > > > > I am trying out the (highly useful) index replicator module (with the > > HttpReplicator) and have stumbled upon a question: > > It seems, the IndexReplicationHandler is working directly on the index > > directory, without using an indexwriter. Could there be a problem if I > open > > an IndexWriter on the client side? > > Usually, this should not be needed, as only the master should be changed, > > however if I want to implement a "tree topology", I need an IndexWriter > on a > > non-leaf client, because the IndexRevision that I need to publish needs > one. > > > > Regards, > > Christoph > > > > -- > > Dipl.-Inf. Christoph Kaser > > > > IconParc GmbH > > Sophienstrasse 1 > > 80333 München > > > > www.iconparc.de > > > > Tel +49 -89- 15 90 06 - 21 > > Fax +49 -89- 15 90 06 - 49 > > > > Geschäftsleitung: Dipl.-Ing. Roland Brückner, Dipl.-Inf. Sven Angerer. > HRB > > 121830, Amtsgericht München > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > > For additional commands, e-mail: java-user-h...@lucene.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > >
