Class ORSet$

  • All Implemented Interfaces:, scala.Serializable

    public class ORSet$
    extends java.lang.Object
    implements scala.Serializable
    Java API
    See Also:
    Serialized Form
    • Field Detail

      • MODULE$

        public static final ORSet$ MODULE$
        Static reference to the singleton instance of this Scala object.
    • Constructor Detail

      • ORSet$

        public ORSet$()
    • Method Detail

      • $lessinit$greater$default$3

        public <A> scala.Option<ORSet.DeltaOp> $lessinit$greater$default$3()
        Implements a 'Observed Remove Set' CRDT, also called a 'OR-Set'. Elements can be added and removed any number of times. Concurrent add wins over remove.

        It is not implemented as in the paper A comprehensive study of Convergent and Commutative Replicated Data Types. This is more space efficient and doesn't accumulate garbage for removed elements. It is described in the paper An optimized conflict-free replicated set The implementation is inspired by the Riak DT riak_dt_orswot.

        The ORSet has a version vector that is incremented when an element is added to the set. The node -&gt; count pair for that increment is stored against the element as its "birth dot". Every time the element is re-added to the set, its "birth dot" is updated to that of the node -&gt; count version vector entry resulting from the add. When an element is removed, we simply drop it, no tombstones.

        When an element exists in replica A and not replica B, is it because A added it and B has not yet seen that, or that B removed it and A has not yet seen that? In this implementation we compare the dot of the present element to the version vector in the Set it is absent from. If the element dot is not "seen" by the Set version vector, that means the other set has yet to see this add, and the item is in the merged Set. If the Set version vector dominates the dot, that means the other Set has removed this element already, and the item is not in the merged Set.

        This class is immutable, i.e. "modifying" methods return a new instance.

      • empty

        public <A> ORSet<A> empty()
      • apply

        public ORSet<java.lang.Object> apply()
      • create

        public <A> ORSet<A> create()
        Java API
      • unapply

        public <A> scala.Option<scala.collection.immutable.Set<A>> unapply​(ORSet<A> s)
        Extract the ORSet.elements().
        s - (undocumented)
      • unapply

        public scala.Option<scala.collection.immutable.Set<java.lang.Object>> unapply​(ReplicatedData a)
        Extract the ORSet.elements() of an ORSet.
        a - (undocumented)
      • mergeCommonKeys

        public <A> scala.collection.immutable.Map<A,​VersionVector> mergeCommonKeys​(scala.collection.immutable.Set<A> commonKeys,
                                                                                         ORSet<A> lhs,
                                                                                         ORSet<A> rhs)
      • mergeDisjointKeys

        public <A> scala.collection.immutable.Map<A,​VersionVector> mergeDisjointKeys​(scala.collection.immutable.Set<A> keys,
                                                                                           scala.collection.immutable.Map<A,​VersionVector> elementsMap,
                                                                                           VersionVector vvector,
                                                                                           scala.collection.immutable.Map<A,​VersionVector> accumulator)