Yeah, I can use HBase too.
but why you are not using hbase if its feature set fits your needs
better and want to have same functionality in cassandra? Its good that
both projects are different in this area. From rest of your post it
looks like you want to have cassandra ACID compliant, which is against
its design ideas. If you want ACID compliant nosql engine then there are
few others not only hbase.
Cassandra is more like read uncommitted.
yes.
Even if row mutations in one CF for one key are atomic on one server , stuff
is not rolled back when the CL can't be satisfied at the coordinator level.
Data won't be visible at QUORUM level, but when using weaker CL, invalid
data can appear imho.
Thats right. Its responsibility of application designer to code
application in that way - use correct CL. In SQL databases its server
responsibility to deal with inconsistent data, but in nosql its client
responsibility. In reality its not problem because you have your
applications under control. This problem might be worked around by
cassandra core if additional settings are added to CF - minimum CL
levels for read/write. Submit feature request to jira if you are
interested in that.
