which was just /MM, then during our maintenance we could spool off
>> records that match the month we are archiving, then do a bulk delete by that
>> key. We would need to have a secondary index for that, I would assume.
>>
>>
>> From: Michael Kjellman [mail
to have a secondary index for that, I would assume.
From: Michael Kjellman [mailto:mkjell...@barracuda.com]
Sent: Tuesday, December 18, 2012 11:15 AM
To: user@cassandra.apache.org<mailto:user@cassandra.apache.org>
Subject: Re: Partition maintenance
You could make a column family for each peri
Just make month time stamp a part of row key. Then once a month select old
data, move it and delete.
Andrey
On Tue, Dec 18, 2012 at 8:08 AM, wrote:
> Hi folks. Still working through the details of building out a Cassandra
> solution and I have an interesting requirement that I’m not sure how
index for that, I would assume.
From: Michael Kjellman [mailto:mkjell...@barracuda.com]
Sent: Tuesday, December 18, 2012 11:15 AM
To: user@cassandra.apache.org
Subject: Re: Partition maintenance
You could make a column family for each period of time and then drop the column
family when you want
m]
Sent: Tuesday, December 18, 2012 18:33
To: user@cassandra.apache.org
Subject: Re: Partition maintenance
My understanding was that TTLs only apply to columns and not on a per row
basis. This means that for each column insert you would need to set that TTL.
Does this mean that the amount of d
ecember 18, 2012 11:16 AM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: Partition maintenance
If I'm understanding you correctly, you can write TTL's on each insert.
18 months would be roughly 54
If I'm understanding you correctly, you can write TTL's on each insert.
18 months would be roughly 540 days which would be 46656000 seconds. I've not
tried that number, but I use smaller TTL's all the time and they work fine.
Once they are expired they get tombstones and are no longer searchable
You could make a column family for each period of time and then drop the column
family when you want to destroy it. Before you drop it you could use the
sstabletojson converter and write the json files out to tape.
Might make your life difficult however if you need an input split for map
reduce
Hi folks. Still working through the details of building out a Cassandra
solution and I have an interesting requirement that I'm not sure how to
implement in Cassandra:
In our current Oracle world, we have the data for this system partitioned by
month, and each month the data that are now 18-mo
