The type of the delta.
The type of the delta. To be specified by subclass.
It may be the same type as T
or a different type if needed.
For example GSet
uses the same type and ORSet
uses different types.
The type of the concrete implementation, e.g.
The type of the concrete implementation, e.g. GSet[A]
.
To be specified by subclass.
Adds an entry to the map
Removes an entry from the map.
Removes an entry from the map. Note that if there is a conflicting update on another node the entry will not be removed after merge.
The accumulated delta of mutator operations since previous #resetDelta.
The accumulated delta of mutator operations since previous
#resetDelta. When the Replicator
invokes the modify
function
of the Update
message and the user code is invoking one or more mutator
operations the data is collecting the delta of the operations and makes
it available for the Replicator
with the #delta accessor. The
modify
function shall still return the full state in the same way as
ReplicatedData
without support for deltas.
Scala API: All entries of the map.
Java API: All entries of the map.
Monotonic merge function.
Monotonic merge function.
When delta is merged into the full state this method is used.
When delta is merged into the full state this method is used.
When the type D
of the delta is of the same type as the full state T
this method can be implemented by delegating to merge
.
The nodes that have changed the state for this data and would need pruning when such node is no longer part of the cluster.
The nodes that have changed the state for this data and would need pruning when such node is no longer part of the cluster.
Does it have any state changes from a specific node, which has been removed from the cluster.
Does it have any state changes from a specific node, which has been removed from the cluster.
When the removed
node has been removed from the cluster the state
changes from that node will be pruned by collapsing the data entries
to another node.
When the removed
node has been removed from the cluster the state
changes from that node will be pruned by collapsing the data entries
to another node.
Remove data entries from a node that has been removed from the cluster and already been pruned.
Remove data entries from a node that has been removed from the cluster and already been pruned.
Adds an entry to the map.
Adds an entry to the map.
You can provide your clock
implementation instead of using timestamps based
on System.currentTimeMillis()
time. The timestamp can for example be an
increasing version number from a database record that is used for optimistic
concurrency control.
Adds an entry to the map.
Adds an entry to the map.
You can provide your clock
implementation instead of using timestamps based
on System.currentTimeMillis()
time. The timestamp can for example be an
increasing version number from a database record that is used for optimistic
concurrency control.
Adds an entry to the map
Removes an entry from the map.
Removes an entry from the map. Note that if there is a conflicting update on another node the entry will not be removed after merge.
Reset collection of deltas from mutator operations.
Reset collection of deltas from mutator operations. When the Replicator
invokes the modify
function of the Update
message the delta is always
"reset" and when the user code is invoking one or more mutator operations the
data is collecting the delta of the operations and makes it available for
the Replicator
with the #delta accessor. When the Replicator
has
grabbed the delta
it will invoke this method to get a clean data instance
without the delta.
(lWWMap: any2stringadd[LWWMap[A, B]]).+(other)
Specialized ORMap with LWWRegister values.
LWWRegister
relies on synchronized clocks and should only be used when the choice of value is not important for concurrent updates occurring within the clock skew.Instead of using timestamps based on
System.currentTimeMillis()
time it is possible to use a timestamp value based on something else, for example an increasing version number from a database record that is used for optimistic concurrency control.The
defaultClock
is using max value ofSystem.currentTimeMillis()
andcurrentTimestamp + 1
. This means that the timestamp is increased for changes on the same node that occurs within the same millisecond. It also means that it is safe to use theLWWMap
without synchronized clocks when there is only one active writer, e.g. a Cluster Singleton. Such a single writer should then first read current value withReadMajority
(or more) before changing and writing the value withWriteMajority
(or more).For first-write-wins semantics you can use the LWWRegister#reverseClock instead of the LWWRegister#defaultClock
This class is immutable, i.e. "modifying" methods return a new instance.