.
*From:* AJ [mailto:a...@dude.podzone.net]
*Sent:* Friday, June 24, 2011 11:28 PM
*To:* user@cassandra.apache.org
*Subject:* Re: Cassandra ACID
Ok, here it is reworked; consider it a summary of the thread. If I
left out an imp
ode, but not the others.
From: AJ [mailto:a...@dude.podzone.net]
Sent: Friday, June 24, 2011 11:28 PM
To: user@cassandra.apache.org
Subject: Re: Cassandra ACID
Ok, here it is reworked; consider it a summary of the thread. If I left
out an important point that
>
> That being said, we do not provide isolation, which means in particular
> that
> reads *can* return a state where only parts of a batch update seems applied
> (and it would clearly be cool to have isolation and I'm not even
> saying this will
> never happen).
Out of curiosity, do you see any
> We do always provide atomicity of updates in the same batch_mutate call
> under a given key. Which means that for a given key, all update of the batch
> will be applied, or none of them. This is *always* true and this does not
> depend
> on the commit log (and granted, if the write timeout, you
Ok, here it is reworked; consider it a summary of the thread. If I left
out an important point that you think is 100% correct even if you
already mentioned it, then make some noise about it and provide some
evidence so it's captured sufficiently. And, if you're in a debate,
please try and get
On 6/23/2011 8:55 PM, AJ wrote:
Can any Cassandra contributors/guru's confirm my understanding of
Cassandra's degree of support for the ACID properties?
I provide official references when known. Please let me know if I
missed some good official documentation.
*Atomicity*
All individual writ
On Fri, Jun 24, 2011 at 9:11 AM, Peter Schuller
wrote:
>> Atomicity
>> All individual writes are atomic at the row level. So, a batch mutate for
>> one specific key will apply updates to all the columns for that one specific
>> row atomically. If part of the single-key batch update fails, then a
> Atomicity
> All individual writes are atomic at the row level. So, a batch mutate for
> one specific key will apply updates to all the columns for that one specific
> row atomically. If part of the single-key batch update fails, then all of
> the updates will be reverted since they all pertaine
Can any Cassandra contributors/guru's confirm my understanding of
Cassandra's degree of support for the ACID properties?
I provide official references when known. Please let me know if I
missed some good official documentation.
*Atomicity*
All individual writes are atomic at the row level.
Hi, all,
(Jonathan Ellis, Jonathan Shook, Aaron Morton)
Thanks for the confirmation.
JonE, the "update" wording has been added to wiki page w.r.t. to insert and
mutation API.
Regards,
Alex Yiu
On Tue, Jul 20, 2010 at 2:02 PM, Jonathan Ellis wrote:
> On Tue, Jul 20, 2010 at 2:58 PM, Alex Yi
Yes, both inserts (colD and colE) will succeed if you send insert() or batch_mutation()s from the client. It's also correct to think of them as insert-or-update calls. AaronOn 21 Jul, 2010,at 07:58 AM, Alex Yiu wrote:Hi,I have more questions on Cassandra ACID properties. Say, I have a row
a
logical instance of each row, from what I know. Maybe a dev can
confirm this.
On Tue, Jul 20, 2010 at 2:58 PM, Alex Yiu wrote:
>
>
> Hi,
> I have more questions on Cassandra ACID properties.
> Say, I have a row that has 3 columns already: colA, colB and colC
> And, if two *c
On Tue, Jul 20, 2010 at 2:58 PM, Alex Yiu wrote:
> Say, I have a row that has 3 columns already: colA, colB and colC
> And, if two *concurrent* clients perform a different insert(...) into the
> same row,
> one insert is for colD and the other insert is for colE.
> Then, Cassandra would guarantee
Hi,
I have more questions on Cassandra ACID properties.
Say, I have a row that has 3 columns already: colA, colB and colC
And, if two *concurrent* clients perform a different insert(...) into the
same row,
one insert is for colD and the other insert is for colE.
Then, Cassandra would guarantee
14 matches
Mail list logo
