[
https://issues.apache.org/jira/browse/CASSANDRA-7464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14614614#comment-14614614
]
Robert Stupp commented on CASSANDRA-7464:
-----------------------------------------
Regarding some "tool for debugging purposes": I think it would be very useful
for people to be able to scan for very wide and very narrow rows - i.e. to
actually being able to inspect the rows that "really hurt" not just by
inspecting _cfstats_ (which only tells you, that there is a problem). Not
really sure if that demand really fits into a node-local tool (I suspect not).
> Retire/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
>
> 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)
