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 DCE7F10D06 for ; Fri, 11 Mar 2016 19:15:39 +0000 (UTC) Received: (qmail 85055 invoked by uid 500); 11 Mar 2016 19:15:39 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 85021 invoked by uid 500); 11 Mar 2016 19:15:39 -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 85002 invoked by uid 99); 11 Mar 2016 19:15:39 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Mar 2016 19:15:39 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 493D32C1F69 for ; Fri, 11 Mar 2016 19:15:39 +0000 (UTC) Date: Fri, 11 Mar 2016 19:15:39 +0000 (UTC) From: "Kaide Mu (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-8928) Add downgradesstables 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-8928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15191399#comment-15191399 ] Kaide Mu commented on CASSANDRA-8928: ------------------------------------- Hi, dear Paulo. I'd read such blog, I think now I'm clear with changes of Data.db in 3.x, I tried to find something similar of changes on version 2.2 but I didn't find anything, do you have any similar references or similar things, I'll try to see if I can breakdown it, but it seems quite difficult in the sense that I'm not familiar with Cassandra code base. Also before jumping to draw up the framework, I'd like to know is our purpose downgrade an existing SSTable to certain older version or add the possibility to write older version of SSTable? Regards. > Add downgradesstables > --------------------- > > Key: CASSANDRA-8928 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8928 > Project: Cassandra > Issue Type: New Feature > Components: Tools > Reporter: Jeremy Hanna > Priority: Minor > Labels: gsoc2016, mentor > > As mentioned in other places such as CASSANDRA-8047 and in the wild, sometimes you need to go back. A downgrade sstables utility would be nice for a lot of reasons and I don't know that supporting going back to the previous major version format would be too much code since we already support reading the previous version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)