Those properties but 21600 is probably more aggressive than I’d use myself - I’m not 100% sure but I suspect I’d try something over 12 hours
> On Oct 28, 2020, at 10:37 PM, Eunsu Kim <eunsu.bil...@gmail.com> wrote: > > > Thank you for your response. > > What subproperties do you mean specifically? > > Currently, there are the following settings to ageressive purge. > > AND COMPACTION = { 'class' : 'TimeWindowCompactionStrategy', > 'compaction_window_unit' : 'HOURS', 'compaction_window_size' : 12, > 'unchecked_tombstone_compaction': true, 'tombstone_threshold' : 0.05, > 'tombstone_compaction_interval' : 21600 } > AND gc_grace_seconds = 600 > > Apache Cassandra Version 3.11.4 > > >> 2020. 10. 29. 12:26, Jeff Jirsa <jji...@gmail.com> 작성: >> >> Works but requires you to enable tombstone compaction subproperties if you >> need to purge the 2w ttl data before the highest ttl time you chose >> >>> On Oct 28, 2020, at 5:58 PM, Eunsu Kim <eunsu.bil...@gmail.com> wrote: >>> >>> Hello, >>> >>> I have a table with a default TTL(2w). I'm using TWCS(window size : 12h) on >>> the recommendation of experts. This table is quite big, high WPS. >>> >>> I would like to insert data different TTL from the default in this table >>> according to the type of data. >>> About four different TTLs (4w, 6w, 8w, 10w) >>> >>> ex.) >>> INSERT INTO my_table (…..) VALUES (….) USING TTL 4w >>> >>> >>> Could this cause performance problems or unexpected problems in the >>> compaction? >>> >>> Please give me advice, >>> >>> Thank you. >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org >>> For additional commands, e-mail: user-h...@cassandra.apache.org >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org >> For additional commands, e-mail: user-h...@cassandra.apache.org >> >