[jira] [Commented] (CASSANDRA-7464) Replace sstable2json and json2sstable

["Russell Bradberry (JIRA)" <ji...@apache.org>]

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

Russell Bradberry commented on CASSANDRA-7464:
----------------------------------------------

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.

> Replace sstable2json and json2sstable
> -------------------------------------
>
>                 Key: CASSANDRA-7464
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7464
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 3.x
>
>
> Both tools are pretty awful. They are primarily meant for debugging (there is much more efficient and convenient ways to do import/export data), but their output manage to be hard to handle both for humans and for tools (especially as soon as you have modern stuff like composites).
> There is value to having tools to export sstable contents into a format that is easy to manipulate by human and tools for debugging, small hacks and general tinkering, but sstable2json and json2sstable are not that.  
> So I propose that we deprecate those tools and consider writing better replacements. It shouldn't be too hard to come up with an output format that is more aware of modern concepts like composites, UDTs, ....



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