default_time_to_live is a convenience parameter that automatically applies
a TTL to incoming data. Every field that's inserted can have a separate
TTL.
The TL;DR of all this is that changing default_time_to_live doesn't change
any existing data retroactively. You'd have to truncate the table if you
want to drop the old data.
On Mon, Mar 20, 2017 at 12:06 PM Gábor Auth <auth.ga...@gmail.com> wrote:
> Hi,
>
> On Fri, Mar 17, 2017 at 2:22 PM Paulo Motta <pauloricard...@gmail.com>
> wrote:
>
> It's safe to truncate this table since it's just used to inspect repairs
> for troubleshooting. You may also set a default TTL to avoid it from
> growing unbounded (this is going to be done by default on CASSANDRA-12701).
>
>
> I've made an alter on the repair_history and the parent_repair_history
> tables:
> ALTER TABLE system_distributed.repair_history WITH compaction =
> {'class':'org.apache.cassandra.db.compaction.TimeWindowCompactionStrategy',
> 'compaction_window_unit':'DAYS', 'compaction_window_size':'1'
> } AND default_time_to_live = 2592000;
>
> Is it affect the previous contents in the table or I need to truncate
> manually? Is the 'TRUNCATE' safe? :)
>
> Bye,
> Gábor Auth
>
