Return-Path: 
 <commits-return-102425-apmail-cassandra-commits-archive=cassandra.apache.org@cassandra.apache.org>
X-Original-To: apmail-cassandra-commits-archive@www.apache.org
Delivered-To: apmail-cassandra-commits-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 462841185A
	for <apmail-cassandra-commits-archive@www.apache.org>;
 Thu, 12 Jun 2014 20:21:07 +0000 (UTC)
Received: (qmail 42469 invoked by uid 500); 12 Jun 2014 20:21:06 -0000
Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org
Received: (qmail 42417 invoked by uid 500); 12 Jun 2014 20:21:06 -0000
Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@cassandra.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@cassandra.apache.org>
List-Post: <mailto:commits@cassandra.apache.org>
List-Id: <commits.cassandra.apache.org>
Reply-To: dev@cassandra.apache.org
Delivered-To: mailing list commits@cassandra.apache.org
Received: (qmail 42373 invoked by uid 99); 12 Jun 2014 20:21:05 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jun 2014 20:21:05 +0000
Date: Thu, 12 Jun 2014 20:21:05 +0000 (UTC)
From: "Sylvain Lebresne (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12720810.1402555562300.121284.1402604465900@arcas>
In-Reply-To: <JIRA.12720810.1402555562300@arcas>
References: <JIRA.12720810.1402555562300@arcas>
Subject: [jira] [Commented] (CASSANDRA-7382) A single command for setting a
 row ttl
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ 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)