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 7774E17D03 for ; Thu, 18 Jun 2015 20:33:01 +0000 (UTC) Received: (qmail 95456 invoked by uid 500); 18 Jun 2015 20:33:01 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 95430 invoked by uid 500); 18 Jun 2015 20:33:01 -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 95418 invoked by uid 99); 18 Jun 2015 20:33:01 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jun 2015 20:33:01 +0000 Date: Thu, 18 Jun 2015 20:33:01 +0000 (UTC) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-9618) Consider deprecating sstable2json/json2sstable in 2.2 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-9618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14592465#comment-14592465 ] Jonathan Ellis commented on CASSANDRA-9618: ------------------------------------------- How is 7464 not just sstable2json with a different output format? (We've changed output format dramatically before, it's totally valid to do that in a major version.) > 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 > Fix For: 2.2.0 rc2 > > > 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)