I agree with jonathan haddad. A traditional ACID transaction following the
classic definition, isolation is necessary. Having said that, there is
different levels of isolation.
http://en.wikipedia.org/wiki/Isolation_%28database_systems%29#Isolation_levels
Saying the distinction is pendantic is wr
This is often a confusing topic because someone came up with the term ACID,
which lists isolation as well as atomicity, and as a result most people
assume they are independent. This is incorrect. For something to be
atomic, it actually requires isolation.
"An operation is atomic if no intermedia
On Tue, Mar 3, 2015 at 2:39 PM, Jonathan Haddad wrote:
> Actually, that's not true either. It's technically possible for a batch
> to be partially applied in the current implementation, even with logged
> batches. "atomic" is used incorrectly here, imo, since more than 2 states
> can be visible
Actually, that's not true either. It's technically possible for a batch to
be partially applied in the current implementation, even with logged
batches. "atomic" is used incorrectly here, imo, since more than 2 states
can be visible, unapplied & applied.
On Tue, Mar 3, 2015 at 9:26 AM Michael Dy
I have a minor complaint about the documentation. On the page for Batch
Statements:
http://www.datastax.com/documentation/cql/3.0/cql/cql_reference/batch_r.html
It states: "In the context of a Cassandra batch operation, atomic means
that if any of the batch succeeds, all of it will."
While the
