cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Viktor Jevdokimov <Viktor.Jevdoki...@adform.com>
Subject RE: tombstones problem with 1.0.8
Date Fri, 23 Mar 2012 09:59:50 GMT
> You are explaining that if i have expired row tombstone and there exists later timestamp
on this row that tombstone is not deleted? If this works that way, it will be never deleted.

Exactly. It is merged with new one.

Example 1: a row with 1 column in sstable. delete a row, not a column. after compaction or
cleanup in sstable will exist an empty row key with tombstone.
Example 2: a row with 1 column in sstable. delete a column. after compaction or cleanup in
sstable will exist a row with 1 column with tombstone.

Question: why delete operation is requested from application for a row/column that is already
deleted (can't be returned by get)?



Best regards/ Pagarbiai



Viktor Jevdokimov

Senior Developer



Email:  Viktor.Jevdokimov@adform.com

Phone: +370 5 212 3063. Fax: +370 5 261 0453

J. Jasinskio 16C, LT-01112 Vilnius, Lithuania






[Adform news]<http://www.adform.com/>

[Visit us!]

Follow:


[twitter]<http://twitter.com/#!/adforminsider>

Visit our blog<http://www.adform.com/site/blog>



Disclaimer: The information contained in this message and attachments is intended solely for
the attention and use of the named addressee and may be confidential. If you are not the intended
recipient, you are reminded that the information remains the property of the sender. You must
not use, disclose, distribute, copy, print or rely on this e-mail. If you have received this
message in error, please contact the sender immediately and irrevocably delete this message
and any copies.


Mime
View raw message