DurablePersistentMap
Related Docs:
object DurablePersistentMap
| package confluent
Finds the most recent value for an entity id with respect to version path.
Finds the most recent value for an entity id with respect to version path. If a value is found,
it is return along with a suffix suitable for identifier path actualisation.
the type of values stored with the entity
the identifier for the object
the path through which the object has been accessed (the version at which it is read)
the transaction within which the access is performed
the serializer used to store the entity's values
None if no value was found, otherwise a Some of the tuple consisting of the
suffix and the value. The suffix is the access path minus the prefix at which the
value was found. However, the suffix overlaps the prefix in that it begins with the
tree entering/exiting tuple at which the value was found.
Finds the most recent value for an entity id with respect to version path.
Finds the most recent value for an entity id with respect to version path.
The serializer given is _non_transactional. This is because this trait bridges confluent
and ephemeral world (it may use a durable backend, but the data structures used for
storing the confluent graph are themselves ephemeral). If the value A requires a
transactional serialization, the current approach is to pre-serialize the value into
an appropriate format (e.g. a byte array) before calling into put. In that case
the wrapping structure must be de-serialized after calling get.
the type of values stored with the entity
the identifier for the object
the path through which the object has been accessed (the version at which it is read)
the transaction within which the access is performed
the serializer used to store the entity's values
None if no value was found, otherwise a Some of that value.
Note: requires that path is non-empty.
Stores a new value for a given write path.
Stores a new value for a given write path.
The serializer given is _non_transactional. This is because this trait bridges confluent
and ephemeral world (it may use a durable backend, but the data structures used for
storing the confluent graph are themselves ephemeral). If the value A requires a
transactional serialization, the current approach is to pre-serialize the value into
an appropriate format (e.g. a byte array) before calling into put. In that case
the wrapping structure must be de-serialized after calling get.
the type of values stored with the entity
the identifier for the object
the path through which the object has been accessed (the version at which it is read)
the value to store
the transaction within which the access is performed
the serializer used to store the entity's values
Interface for a confluently or partially persistent storing key value map. Keys (type
K) might be single object identifiers (as the variable storage case), or combined keys (as in the live map case).the underlying system
the key type