cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Russell Bradberry (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9618) Consider deprecating sstable2json/json2sstable in 2.2
Date Thu, 03 Dec 2015 18:55:11 GMT


Russell Bradberry commented on CASSANDRA-9618:

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

View raw message