cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9618) Consider deprecating sstable2json/json2sstable in 2.2
Date Thu, 18 Jun 2015 15:52:02 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14592012#comment-14592012
] 

Aleksey Yeschenko commented on CASSANDRA-9618:
----------------------------------------------

Agreed. +1 to that.

> 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)

Mime
View raw message