[
https://issues.apache.org/jira/browse/CASSANDRA-7382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14029745#comment-14029745
]
Sylvain Lebresne commented on CASSANDRA-7382:
---------------------------------------------
The only simple way to do this would be to read the full row server side and
re-insert it with the new TTL. So far, we've preferred leaving that to the
client so it's clear that there is a read-before-write. I still think it's a
good idea, though if we were to change our mind on that, doing it wouldn't be
too complicated and could go in 2.1.
Another option if we wanted to support this more efficiently would be to add
range TTLs. Conceptually, it would be very similar to range tombstones and a
lot of code could be shared between the two, but it's still not trivial work if
only because we need to change the serialization format (network and on-disk)
to support it, so that wouldn't be 2.1 material. I'm not entirely convinced
it's worth the complexity but if someone came up with a clean patch to do it, I
wouldn't have a strong opposition either.
> A single command for setting a row ttl
> --------------------------------------
>
> Key: CASSANDRA-7382
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7382
> Project: Cassandra
> Issue Type: Improvement
> Components: API
> Reporter: Or Sher
>
> Currently, in order to just change a row ttl you'll have read it's values and
> re-insert them using ttl.
> I'm not sure if current design will allow it, but it will be great
> improvement to be able to do something like this:
> update <table> using ttl <sec> where pk=<value>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
