The Key-Value service in current ResilientDB only supports raw get and set
interfaces.
We need to add a version tag to enable users to obtain a Key's history
based on the version and support optimistic concurrency control via CAS
based on the version.

The new implementation will just extend the current implementation to
support both non-version and version interaction.


Thanks,
Junchao

Reply via email to