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 EE5129F9F for ; Mon, 19 Mar 2012 22:10:44 +0000 (UTC) Received: (qmail 59308 invoked by uid 500); 19 Mar 2012 22:10:42 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 59239 invoked by uid 500); 19 Mar 2012 22:10:42 -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 59219 invoked by uid 99); 19 Mar 2012 22:10:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Mar 2012 22:10:42 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of hsn@filez.com designates 64.6.108.239 as permitted sender) Received: from [64.6.108.239] (HELO ponto.amerinoc.com) (64.6.108.239) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Mar 2012 22:10:32 +0000 Received: from fbsd8.localdomain (205.83.broadband7.iol.cz [88.102.83.205]) (authenticated bits=128) by ponto.amerinoc.com (8.14.5/8.14.5) with ESMTP id q2JM9vHH011214 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 19 Mar 2012 23:10:00 +0100 (CET) (envelope-from hsn@filez.com) Received: from [127.0.0.1] ([10.0.0.1]) by fbsd8.localdomain (8.14.4/8.14.4) with ESMTP id q2JLpuNt096631 for ; Mon, 19 Mar 2012 22:51:56 +0100 (CET) (envelope-from hsn@filez.com) Message-ID: <4F67AA77.7000409@filez.com> Date: Mon, 19 Mar 2012 22:51:51 +0100 From: Radim Kolar User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120312 Thunderbird/11.0 MIME-Version: 1.0 To: user@cassandra.apache.org Subject: Re: repair broke TTL based expiration References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------040309040002020704000204" X-Antivirus: avast! (VPS 120319-0, 19.03.2012), Outbound message X-Antivirus-Status: Clean X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. --------------040309040002020704000204 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Dne 19.3.2012 21:46, Caleb Rackliffe napsal(a): > I've been wondering about this too, but every column has both a > timestamp /and/ a TTL. Unless the timestamp is not preserved, there > should be no need to adjust the TTL, assuming the expiration time is > determined from these two variables. timestamp is application defined, it can be anything. expire time is recorded into sstable in node local time. another question is why to store original TTL? i dont think that it is that usefull to read it back. it would be enough to read expire time. --------------040309040002020704000204 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Dne 19.3.2012 21:46, Caleb Rackliffe napsal(a):
I've been wondering about this too, but every column has both a timestamp and a TTL.  Unless the timestamp is not preserved, there should be no need to adjust the TTL, assuming the expiration time is determined from these two variables.
timestamp is application defined, it can be anything. expire time is recorded into sstable in node local time.
another question is why to store original TTL? i dont think that it is that usefull to read it back. it would be enough to read expire time.
--------------040309040002020704000204--