For my use case it would be nice to have per CF TTL (to protect myself
from application bug and from storage leak due to missed TTL), but seems
you can't avoid tombstones even in this case and if you change CF TTL
during runtime.
On 04/18/2012 03:06 PM, Viktor Jevdokimov wrote:
Our use case requires Column TTL, not CF TTL, because it is variable, not
constant.
Best regards/ Pagarbiai
Viktor Jevdokimov
Senior Developer
Email: [email protected]
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:[email protected]]
Sent: Wednesday, April 18, 2012 12:57
To: [email protected]
Subject: Re: size tiered compaction - improvement
Any compaction pass over A will first convert the TTL data into tombstones.
Then, any subsequent pass that includes A *and all other sstables
containing rows with the same key* will drop the tombstones.
thats why i proposed to attach TTL to entire CF. Tombstones would not be needed
