TWCS uses the max timestamp in an sstable to determine what to compact
together, it won't anti-compact your data. The goal is to minimize I/O.
You'll have to wait for all your mixed-timestamp sstable data to TTL out
before TWCS's windowing kicks in optimally.
http://thelastpickle.com/blog/2016/1
Yes the data is TTLed, but I don't think that's the criteria for the TWCS.
My understanding is the data is divided into buckets based on written
timestamp.
Thanks
Pranay
On Fri, Apr 27, 2018, 1:17 PM Nitan Kainth wrote:
> Is old data TTLed already? If not, then I don't think TWCS will know when
Is old data TTLed already? If not, then I don't think TWCS will know when
to delete data.
My understanding about TWCS is, data has to be written with TTL. (Please
correct me, if wrong)
Regards,
Nitan K.
Cassandra and Oracle Architect/SME
Datastax Certified Cassandra expert
Oracle 10g Certified
Hi,
Testing to switch from sizetiered to Timewindow, did changed compaction
strategy on a table with a buckets of 3 days
After switching when I checked min and max timestamps on sstables I did see
data older than 3 days range in my case 30-60 days
So when we switch from sizetired to Timewindow,
