OK, that's an option indeed. However due to the amount of records it would also involve bucketing which makes it not the simplest option. Further more, there are lots of manual indexes referring to the keys of the actual events: all those indexes should also be updated.
Best regards, Robin Verlangen *Software engineer* * * W http://www.robinverlangen.nl E ro...@us2.nl 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. 2012/9/10 Oleg Dulin <oleg.du...@gmail.com> > ** > > You should create an index where you store references to your records. You > can use composite column names where column name=composite(timestamp,key) > > > then you would get a slice of all columns where timestamp part of the > composite is >= TTL in the past, and then iterate through them and delete > the items. > > > Regards, > > Oleg > > > > On 2012-09-10 09:47:31 +0000, Robin Verlangen said: > > > Hi there, > > > I'm working on a project that might want to set TTL to roughly 7 years. > However it might occur that the TTL should be reduced or extended. Is there > any way of updating the TTL without being in need of rewriting the data > back again? This would cause way to much overhead for this. > > > If not, is running a Map/Reduce task on the whole data set the "best" > option or should I think in a difference approach for this challenge? > > > My last question is regarding to a long term TTL, does this have any > negative impact on the cluster? Maybe during compaction, repair, > reading/writing? > > > Best regards, > > > Robin Verlangen > > Software engineer > > > W http://www.robinverlangen.nl > > E ro...@us2.nl > > > 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. > > > > >
