Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 3 Dec 2015 19:03:11 +0000 (UTC)
From: "Russell Bradberry (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12838833.1434640965000.262751.1449169391222@Atlassian.JIRA>
In-Reply-To: <JIRA.12838833.1434640965000@Atlassian.JIRA>
References: <JIRA.12838833.1434640965000@Atlassian.JIRA>
 <JIRA.12838833.1434640965515@arcas>
Subject: [jira] [Issue Comment Deleted] (CASSANDRA-9618) Consider
 deprecating sstable2json/json2sstable in 2.2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-9618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Russell Bradberry updated CASSANDRA-9618:
-----------------------------------------
    Comment: was deleted

(was: It is absolutely insane that a perfectly working, albeit not the greatest, troubleshooting tool was removed and not replaced with anything.  We now have no way at all to look into the SSTables.  This makes troubleshooting production problems incredibly difficult.  I am curious as to why enough consideration wasn't given to hold off the removal of the tool until the new one was ready to go. )

> Consider deprecating sstable2json/json2sstable in 2.2
> -----------------------------------------------------
>
>                 Key: CASSANDRA-9618
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9618
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>             Fix For: 2.2.0 rc2
>
>         Attachments: 0001-Deprecate-sstable2json-and-json2sstable.patch
>
>
> The rational is explained in CASSANDRA-7464 but to rephrase a bit:
> * json2sstable is pretty much useless, {{CQLSSTableWriter}} is way more flexible if you need to write sstable directly.
> * sstable2json is really only potentially useful for debugging, but it's pretty bad at that (it's output is not really all that helpul in modern Cassandra in particular).
> Now, it happens that updating those tool for CASSANDRA-8099, while possible, is a bit involved. So I don't think it make sense to invest effort in maintain these tools. So I propose to deprecate these in 2.2 with removal in 3.0.
> I'll note that having a tool to help debugging sstable can be useful, but I propose to add a tool for that purpose with CASSANDRA-7464.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)