Cassandra is not row level consistent
datanerds.io
Cassandra is not row level consistent
1–10 of 126 posts
Re: Cassandra is not row level consistent
#2[deleted]
Re: Cassandra is not row level consistent
#3Couldn't explain the problem in a less cringy way?
Sounds like a bug to me. So file a bug report?
Re: Cassandra is not row level consistent
#4If it's not obtained synchronously what does the lock achieve?
Re: Cassandra is not row level consistent
#5Couldn't explain the problem in a less cringy way? Sounds like a bug to me. So file a bug report?
I think not strictly a bug, just surprising behavior. They linked to the documentation that shows that it is "expected" to work like that, and to two requests for features to help mitigate this issue.
Re: Cassandra is not row level consistent
#6As a long time Cassandra user its easy to forget that some of Cassandra's semantics will be surprising to new users. That being said, if you are considering adopting an AP database it really is important for you to know the details about how write conflicts get resolved. This is perhaps the biggest difference between Cassandra other databases like Riak and ought to be part of your decision making process instead of a surprise you run into later.
That being said, using Cassandra for distributed locks is a terrible idea. I can't think of any way in which Cassandra would be better than using {Zookeeper,etcd,consul}. Trying to force a database to do something it really isn't designed for will almost always lead to disappointment (and often resentment) of said database.
Re: Cassandra is not row level consistent
#7Cassandra is a piece of shit. Negative that comment how you wants, this never change the initial info. I used that BS on a startup on data science on the crawling info level and was on the worst experiences with db I had. CASSANDRA IS JUST PAIN.
Re: Cassandra is not row level consistent
#8Shouldn't Cassandra be using Lamport timestamps or even vector clocks there? Relying on timer and its resolution sounds strange for a database, especially a distributed one.
Re: Cassandra is not row level consistent
#9Cassandra is a piece of shit. Negative that comment how you wants, this never change the initial info. I used that BS on a startup on data science on the crawling info level and was on the worst experiences with db I had. CASSANDRA IS JUST PAIN.
Some details besides ad-hominem might actually be helpful. When you make statements like this it just looks like trolling.
Re: Cassandra is not row level consistent
#10Couldn't explain the problem in a less cringy way? Sounds like a bug to me. So file a bug report?
I think not strictly a bug, just surprising behavior. They linked to the documentation that shows that it is "expected" to work like that, and to two requests for features to help mitigate this issue.
bug/feature whatever. CASSANDRA-6123 is exactly addressing row level consistency. but here maybe they found another case.