On Sat, Mar 15, 2014 at 12:47 PM, Shai Erera wrote:
> If you use LocalReplicator on both sides, you have to use the same instance
> on both sides. Otherwise the replicas will never see the published
> revisions the which are done in a separate instance. Can you try that?
Ok, I missed it. I was us
If you use LocalReplicator on both sides, you have to use the same instance
on both sides. Otherwise the replicas will never see the published
revisions the which are done in a separate instance. Can you try that?
Shai
On Mar 15, 2014 1:10 PM, "Roberto Franchini" wrote:
> On Sat, Mar 15, 2014 at
On Sat, Mar 15, 2014 at 11:58 AM, Michael McCandless
wrote:
> I think maybe the problem is you are using LocalReplicator on the
> replicas? I think you should only use that on the master. I think
> e.g. you should use HttpReplicator on the clients? Or, your own
> implementation that moves the f
I think maybe the problem is you are using LocalReplicator on the
replicas? I think you should only use that on the master. I think
e.g. you should use HttpReplicator on the clients? Or, your own
implementation that moves the files its own way.
Have you seen Shai's blog post about this?
http://
Double fields can be implemented today over NumericDVField and therefore
already support updates.
String can be implemented on Sorted/SortedSetDVField, but not updates for
them yet. I hope that once I'm done w/ LUCENE-5513, adding update support
for Sorted/SortedSet will be even easier.
Shai
On
