Hi Sergey,
That's exactly what I mean. I really hope that this will get released soon!
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 a
Hi Robin,
We have the same headache and hope that
https://issues.apache.org/jira/browse/CASSANDRA-3974 will be a balsam.
On 10 September 2012 13:47, Robin Verlangen wrote:
> Hi there,
>
> I'm working on a project that might want to set TTL to roughly 7 years.
> However it might occur that the T
> Is there any way of updating the TTL without being in need of rewriting the
> data back again?
No, there isn't.
> If not, is running a Map/Reduce task on the whole data set the "best" option
If the TTL is made rather infrequently and on a large percentage of
the data, which seems to be your
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 Verlan
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
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,
