cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Viktor Jevdokimov <>
Subject RE: Partition maintenance
Date Tue, 18 Dec 2012 16:57:46 GMT
No way to read the taped data with TTL later - will disappear from tapes :)

Best regards / Pagarbiai
Viktor Jevdokimov
Senior Developer

Phone: +370 5 212 3063, Fax +370 5 261 0453
J. Jasinskio 16C, LT-01112 Vilnius, Lithuania
Follow us on Twitter: @adforminsider<!/adforminsider>
Take a ride with Adform's Rich Media Suite<>

[Adform News] <>
[Adform awarded the Best Employer 2012] <>

Disclaimer: The information contained in this message and attachments is intended solely for
the attention and use of the named addressee and may be confidential. If you are not the intended
recipient, you are reminded that the information remains the property of the sender. You must
not use, disclose, distribute, copy, print or rely on this e-mail. If you have received this
message in error, please contact the sender immediately and irrevocably delete this message
and any copies.

From: Keith Wright []
Sent: Tuesday, December 18, 2012 18:33
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 data space used in such a case would be the TTL * the number of columns?  I was hoping
there was a way to set a row TTL.  See older post:

From: Christopher Keller <<>>
Reply-To: "<>" <<>>
Date: Tuesday, December 18, 2012 11:16 AM
To: "<>" <<>>
Subject: Re: Partition maintenance

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. Space is reclaimed as with any tombstone.


On Dec 18, 2012, at 11:08 AM,<>

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-months old are archived to tape/cold storage and then the partition
for that month is dropped.  Is there a way to do something similar with Cassandra without
destroying our overall performance?

Thanks in advance,

"The downside of being better than everyone else is that people tend to assume you're pretentious."

View raw message