Yes, though as your link points out, "The RAMP family is not designed to
provide ACID guarantees - it’s for situations where atomic reads are good
enough. Concurrent writes will typically be handled with last write wins or
CRDTs."
On Wed, Jan 16, 2019 at 1:04 PM Jonathan Haddad wrote:
> Sounds
Sounds a bit like RAMP: http://rustyrazorblade.com/post/2015/ramp-made-easy/
On Wed, Jan 16, 2019 at 12:51 PM Carl Mueller
wrote:
> "2) Overview: In essence, the protocol calls for each data item to
> maintain the last committed and perhaps also the currently active version,
> for the data and
"2) Overview: In essence, the protocol calls for each data item to maintain
the last committed and perhaps also the currently active version, for the
data and relevant metadata. Each version is tagged with meta-data
pertaining to the transaction that created it. This includes the
transaction
Hi Shalom,
Just a suggestion. Before upgrading to 3.11.3 make sure you are not impacted by
any open crtitical defects especially related to RT which may cause data loss
e.g.14861.
Please find my response below:
The upgrade process that I know of is from 2.0.14 to 2.1.x (higher than 2.1.9 I
Hi All,
I'm about to start a rolling upgrade process from version 2.0.14 to version
3.11.3.
I have a few small questions:
1. The upgrade process that I know of is from 2.0.14 to 2.1.x (higher
than 2.1.9 I think) and then from 2.1.x to 3.x. Do I need to upgrade first
to 3.0.x or can I
Hi,
JanusGraph currently supports Thrift and CQL to communicate with Cassandra,
but CQL not yet for OLAP jobs executed on Spark [1].
If you're not familiar with JanusGraph: JanusGraph[2] is a scalable graph
database that uses different storage and index backends to store the data
and support
