changed the version of chronicle map back to 2.1 and added some fixes to replication

This commit is contained in:
rob
2015-06-24 13:11:34 +01:00
parent 1881c98778
commit e0433a0922
2 changed files with 10 additions and 7 deletions
@@ -437,7 +437,6 @@ final class ReplicatedChronicleMap<K, KI, MKI extends MetaBytesInterop<K, ? supe
key, segmentHash, timestamp, remoteIdentifier);
}
@Override
public byte identifier() {
@@ -506,12 +505,16 @@ final class ReplicatedChronicleMap<K, KI, MKI extends MetaBytesInterop<K, ? supe
@Override
public void setModificationNotifier(
@NotNull final EngineReplicationModificationNotifier modificationNotifier) {
modificationIterator.setModificationNotifier(toModificationNotifier());
modificationIterator.setModificationNotifier(new ModificationNotifier() {
@Override
public void onChange() {
modificationNotifier.onChange();
}
});
}
private ModificationNotifier toModificationNotifier() {
return null;
}
};
}
@@ -1177,7 +1180,7 @@ final class ReplicatedChronicleMap<K, KI, MKI extends MetaBytesInterop<K, ? supe
/**
* Used only with replication, its sometimes possible to receive an old ( or stale update )
* from a remote map. This method is used to determine if we should ignore such updates.
*
* <p/>
* <p>We can reject put() and removes() when comparing times stamps with remote systems
*
* @param entry the maps entry