TTL. They read the
data with the key, calculated TTL, and rewrote the data with TTL. Long, boring,
etc. but they did it.
Sean Durity
-Original Message-
From: Jeff Jirsa
Sent: Thursday, March 14, 2019 9:30 AM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Re: Default TTL on CF
Awesome! Thank you!
On 3/14/19, 9:29 AM, "Jeff Jirsa" wrote:
>SSTableReader and CQLSSTableWriter if you’re comfortable with Java
>
>
>--
>Jeff Jirsa
>
>
>> On Mar 14, 2019, at 1:28 PM, Nick Hatfield
>>wrote:
>>
>> Bummer but, reasonable. Any cool tricks I could use to make that process
>>
SSTableReader and CQLSSTableWriter if you’re comfortable with Java
--
Jeff Jirsa
> On Mar 14, 2019, at 1:28 PM, Nick Hatfield wrote:
>
> Bummer but, reasonable. Any cool tricks I could use to make that process
> easier? I have many TB of data on a live cluster and was hoping to
> starting
Bummer but, reasonable. Any cool tricks I could use to make that process
easier? I have many TB of data on a live cluster and was hoping to
starting cleaning out the earlier bad habits of data housekeeping
On 3/14/19, 9:24 AM, "Jeff Jirsa" wrote:
>It does not impact existing data
>
>The data
It does not impact existing data
The data gets an expiration time stamp when you write it. Changing the default
only impacts newly written data
If you need to change the expiration time on existing data, you must update it
--
Jeff Jirsa
> On Mar 14, 2019, at 1:16 PM, Nick Hatfield wrote:
Hello,
Can anyone tell me if setting a default TTL will affect existing data? I would
like to enable a default TTL and have cassandra add that TTL to any rows that
don’t currently have a TTL set.
Thanks,
