[
https://issues.apache.org/jira/browse/CASSANDRA-7464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15013959#comment-15013959
]
Sebastian Estevez commented on CASSANDRA-7464:
----------------------------------------------
For general understanding of how SSTables and compaction work, sstable2json is
invaluable. 3.0 dropped last week this issue has not been prioritized.
Here's a couple of great posts that only exist because the community had the
tooling to introspect sstables:
http://www.planetcassandra.org/blog/qa-starters-guide-to-cassandra/
http://thelastpickle.com/blog/2011/05/15/Deletes-and-Tombstones.html
folks also used cassandra-cli for this which I think we also deprecated:
http://opensourceconnections.com/blog/2013/07/24/understanding-how-cql3-maps-to-cassandras-internal-data-structure/
There's lots more where these came from, just wanted to show some good examples
of why the tools are useful. +1 on this Jira.
> 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)
