Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4ABD29F75 for ; Thu, 5 Apr 2012 02:00:58 +0000 (UTC) Received: (qmail 95738 invoked by uid 500); 5 Apr 2012 02:00:56 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 95713 invoked by uid 500); 5 Apr 2012 02:00:56 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 95705 invoked by uid 99); 5 Apr 2012 02:00:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Apr 2012 02:00:56 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jinjian.1@gmail.com designates 209.85.215.172 as permitted sender) Received: from [209.85.215.172] (HELO mail-ey0-f172.google.com) (209.85.215.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Apr 2012 02:00:49 +0000 Received: by eaaq11 with SMTP id q11so300289eaa.31 for ; Wed, 04 Apr 2012 19:00:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=JgqiV1HhSfg/Uyc+cajxAfDgEfqXqDE0bqwEidtUQl8=; b=lIczNj9QzewrhVLCR+iUBj80nytng1eZxXBHFjUcz5BwcfdMVZzlJ4ElJa7WVVOU9e Z4jjpCYhanjLlcOIp44myySGYy4ggzdrQr3mXLmXgFzW1X96hY9lG/UhsL2M1HW2cgWZ YoceLylPyaQfYFcaLVdGaP4xmXFxVdrEB4JrBLgV+f71nKkorMHdumnkjBRkzf0a+fXW el5GruUlUpWu6YEXiltdiU00XuWLG/yA7llifUvWpIRTNLfqEq2MKYcqzzFlEyacHtcl UAntI5WfRHlf0WUybamyLYBODhHDmMWTSKLpTMNAsdyAguLA0WTmT9PQCH9Kc1z1dHlZ p2iQ== Received: by 10.14.100.8 with SMTP id y8mr358416eef.7.1333591227119; Wed, 04 Apr 2012 19:00:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.213.7.11 with HTTP; Wed, 4 Apr 2012 19:00:06 -0700 (PDT) From: =?UTF-8?B?6YeR5YmR?= Date: Thu, 5 Apr 2012 10:00:06 +0800 Message-ID: Subject: Is there a way to update column's TTL only? To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=bcaec52be78b5e36f204bce4e7f3 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec52be78b5e36f204bce4e7f3 Content-Type: text/plain; charset=UTF-8 Hi, We would like to leverage Cassandra's expiration to manage our data's lifecycle. We need to: Delete data after a period, like: 1 hour , when user clicked the "Delete" button. We need to read and insert the column in order to update the TTL, but this is unacceptable in our system that might need to readout gigabytes of data. Is there a way to do this? Best Regards! Jian Jin --bcaec52be78b5e36f204bce4e7f3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Hi,

We would like to leverage Cassandra's= expiration to manage our data's lifecycle. We need to: Delete data aft= er a period, like: 1 hour , when user clicked the "Delete" button= .=C2=A0

We need to read and insert the column in order to updat= e the TTL, but this is unacceptable in our system that might need to readou= t gigabytes of data.

Is there a way to do this?
Best Regards!

Jian Jin

--bcaec52be78b5e36f204bce4e7f3--