On 12/1/10 4:56 AM, Daniel Lundin wrote:
Correct. Unlike BigTable and HBase, Cassandra columns don't have a
version dimension.
Timestamp is used for (crude) conflict resolution, and older versions
are always overwritten.
I would be careful with the word "overwritten" here as it obfuscated the immutability of SSTables, and conceptual understanding of same is important to understanding the actual versioning behavior and how it relates to what data has to be read to satisfy queries. :)

=Rob

Reply via email to