Partition Key Implementation
Thanks graham for the hints.
I've digged into the source code and found out those 2 classes:
https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/DeletionInfo.java
https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassand
Thanks graham for the hints.
I've digged into the source code and found out those 2 classes:
https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/DeletionInfo.java
https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/RangeTombstoneList.java
A deletion of an entire row is a single row tombstone, and yes there are range
tombstones for marking deletion of a range of columns also
On Aug 8, 2014, at 2:17 PM, Kevin Burton wrote:
> This is a good question.. I'd love to find out the answer. Seems like a
> tombstone with prefixes for the
This is a good question.. I'd love to find out the answer. Seems like a
tombstone with prefixes for the keys would work well.
Also, can't any key prefixes work in theory?
On Thu, Aug 7, 2014 at 8:33 AM, DuyHai Doan wrote:
> Hello all
>
> Usually, when using DELETE in CQL3 on some fields, C*
Hello all
Usually, when using DELETE in CQL3 on some fields, C* creates tombstone
columns for those fields.
Now if I delete a whole PARTITION (delete from MyTable where
partitionKey=...), what will C* do ? Will it create as many tombstones as
there are physical columns on this partition or will
