ble: and
> default_time_to_live=86400 .
>
>
>
> *From:* Redmumba [mailto:redmu...@gmail.com]
> *Sent:* Monday, April 28, 2014 12:51 PM
> *To:* user@cassandra.apache.org
> *Subject:* Re: Cassandra data retention policy
>
>
>
> Have you looked into using a TTL? You can set this
ble: and
> default_time_to_live=86400 .
>
> From: Redmumba [mailto:redmu...@gmail.com]
> Sent: Monday, April 28, 2014 12:51 PM
> To: user@cassandra.apache.org
> Subject: Re: Cassandra data retention policy
>
> Have you looked into using a TTL? You can set this per i
Donald Smith :
> CQL lets you specify a default TTL per column family/table: and
> default_time_to_live=86400 .
>
>
>
> *From:* Redmumba [mailto:redmu...@gmail.com]
> *Sent:* Monday, April 28, 2014 12:51 PM
> *To:* user@cassandra.apache.org
> *Subject:* Re: Cassandra data re
Have you looked into using a TTL? You can set this per insert
(unfortunately, it can't be set per CF) and values will be tombstoned after
that amount of time. I.e.,
INSERT INTO VALUES ... TTL 15552000
Keep in mind, after the values have expired, they will essentially become
tombstones-
CQL lets you specify a default TTL per column family/table: and
default_time_to_live=86400 .
From: Redmumba [mailto:redmu...@gmail.com]
Sent: Monday, April 28, 2014 12:51 PM
To: user@cassandra.apache.org
Subject: Re: Cassandra data retention policy
Have you looked into using a TTL? You can
Hi guys,
We have a processing system that just uses the data for the past six months
in Cassandra. Any suggestions on the best way to manage the old data in
order to save disk space? We want to keep it as backup but it will not be
used unless we need to do recovery. Thanks in advance!
-John
