Return-Path: 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 33A3419CAF for ; Tue, 19 Apr 2016 08:55:26 +0000 (UTC) Received: (qmail 95748 invoked by uid 500); 19 Apr 2016 08:55:25 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 95707 invoked by uid 500); 19 Apr 2016 08:55:25 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 95690 invoked by uid 99); 19 Apr 2016 08:55:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Apr 2016 08:55:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 951EA2C1F54 for ; Tue, 19 Apr 2016 08:55:25 +0000 (UTC) Date: Tue, 19 Apr 2016 08:55:25 +0000 (UTC) From: "Sylvain Lebresne (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (CASSANDRA-11601) Add ability to remove TTL on table 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-11601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne resolved CASSANDRA-11601. ------------------------------------------ Resolution: Duplicate We can't efficiently remove all the TTL on a table, and besides, it seems what you want is to basically do this on your backup and the simplest way to do this is probably CASSANDRA-7471 so marking this as a duplicate. > Add ability to remove TTL on table > ---------------------------------- > > Key: CASSANDRA-11601 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11601 > Project: Cassandra > Issue Type: Improvement > Reporter: Danyang Li > Priority: Minor > Fix For: 2.2.x > > > If tables are TTLed in your Cassandra and you try to backup the corresponding SSTable to a new cluster, your backup will be lost automatically after a certain period of time, because TTL are still expiring data in the backup SStable. Once the TTL elapsed, data become inaccessible and finally will be deleted physically by compaction after GCGraceSecondes. So we cannot really keep the backup data in a new cluster without removing these existing TTL. > So it might be good to add ability to do batch TTL removing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)