Jonathan Ellis gmail.com> writes:
>
> IMO if you only get CL.ALL it's not superior enough to pessimistic
> locking to justify the complexity of adding it.
>
Yes, may be youre right, but CL.ALL is neccessary only to solve this problem in
a generic way.
In some (most?) cases, conflicts detectio
On Wed, Feb 23, 2011 at 9:57 AM, Oleg Anastasyev wrote:
> From the other hand, the same article says:
> "For conditional writes to work, the condition must be evaluated at all update
> sites before the write can be allowed to succeed."
>
> This means, that when doing such an update CL=ALL must be
> From the article I linked:
>
> "But wait, some might say, you can avoid all this by using vectors in
> a different way – to prevent update conflicts by issuing conditional
> writes which specify a version (vector) and only succeed if that
> version is still current. Sorry, but no, or at least no
On Wed, Feb 23, 2011 at 3:32 AM, Oleg Anastasyev wrote:
>> Basically: vector clocks tell you there was a conflict, but not how to
>> resolve it (that is, you simply don't have enough information to
>> resolve it even if you push that back to the client a la Dynamo).
>> What dynamo-like systems mos
> Basically: vector clocks tell you there was a conflict, but not how to
> resolve it (that is, you simply don't have enough information to
> resolve it even if you push that back to the client a la Dynamo).
> What dynamo-like systems mostly VC for is the trivial case of "client
> X updated field 1
On Tue, Feb 22, 2011 at 7:37 PM, wrote:
> Vector clocks was more of a Dynamo thing, I read a write up somewhere on some
> of reasons why Cassandra puts this issue on the user but I can't locate it
> currently unfortunately. Hope this helps.
Basically: vector clocks tell you there was a conflic
Thanks Jeremy for the details. That helps.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Does-Cassandra-use-vector-clocks-tp6054778p6055129.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
itesh [mailto:tijoriwala.rit...@gmail.com]
Sent: Tuesday, February 22, 2011 8:13 PM
To: cassandra-u...@incubator.apache.org
Subject: Re: Does Cassandra use vector clocks
Thanks for the quick reply. I found this ticket
https://issues.apache.org/jira/browse/CASSANDRA-580 which talks about vector
clock suppo
Thanks for the quick reply. I found this ticket
https://issues.apache.org/jira/browse/CASSANDRA-580 which talks about vector
clock support in Cassandra but it was marked as "won't fix". It would be
insightful to know why it was rejected.
If Cassandra relies on timestamps, does it mean that client
It doesn't, where a time component is needed you must submit your own timestamp
or clock, ie on an insert.
- Original Message -
From: tijoriwala.ritesh
To: cassandra-u...@incubator.apache.org
Sent: Tue Feb 22 19:59:56 2011
Subject: Does Cassandra use vector clocks
Hi,
I searched onli
NO it doesn't. Instead of using vector clock, it checks the column timestamps.
On Wed, Feb 23, 2011 at 11:59 AM, tijoriwala.ritesh
wrote:
>
> Hi,
> I searched online but couldn't get a detailed document on whether Cassandra
> uses vector clocks or not? If yes, how does it work. Any pointers to de
11 matches
Mail list logo
