Should not. Scenario 1, write & delete in one memtable T1 write column T2 delete row T3 flush memtable, sstable 1 contains empty row tombstone T4 row tombstone expires T5 compaction/cleanup, row disappears from sstable 2
Scenario 2, write & delete different sstables T1 write column T2 flush memtable, sstable 1 contains row with column T3 delete row T4 flush memtable, sstable 2 contains empty row tombstone T5 row tombstone expires T6 compaction, rows from sstable 1 & 2 merged, not saved to sstable 3 Scenario 3, alive tombstone T1 write column T2 flush memtable, sstable 1 contains row with column T3 delete row T4 flush memtable, sstable 2 contains empty row tombstone T5 delete row (present in memtable) T6 row tombstone for T3 expected to be expired T7 compaction, sstable 3 row tombstone appears because of T5 Best regards/ Pagarbiai Viktor Jevdokimov Senior Developer Email: viktor.jevdoki...@adform.com Phone: +370 5 212 3063 Fax: +370 5 261 0453 J. Jasinskio 16C, LT-01112 Vilnius, Lithuania 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.-----Original Message----- From: Radim Kolar [mailto:h...@filez.com] Sent: Friday, March 23, 2012 13:28 To: user@cassandra.apache.org Subject: Re: tombstones problem with 1.0.8 Example: T1 < T2 < T3 at T1 write column at T2 delete row at T3 > tombstone expiration do compact ( T1 + T2 ) and drop expired tombstone column from T1 will be alive again?
