Would it help here to not actually issue a delete statement but instead use date based compaction and a dynamically calculated ttl that is some safe distance in the future from your key?
Just a thought. -Thunder On Mar 25, 2015 11:07 AM, "Robert Coli" <rc...@eventbrite.com> wrote: > On Wed, Mar 25, 2015 at 12:45 AM, Robin Verlangen <ro...@us2.nl> wrote: > >> @Robert: can you elaborate a bit more on the "not ideal" parts? In my >> case I will be throwing away the rows (thus the points in time that are >> "now in the past"), which will create tombstones which are compacted away. >> > > "Not ideal" is what I mean... Cassandra has immutable data files, use > cases which do DELETE pay an obvious penalty. Some percentage of tombstones > will exist continuously, and you have to store them and seek past them. > > =Rob > >
