[
https://issues.apache.org/jira/browse/CASSANDRA-7464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15038529#comment-15038529
]
Sylvain Lebresne commented on CASSANDRA-7464:
---------------------------------------------
bq. It is absolutely insane that a perfectly working, albeit not the greatest,
troubleshooting tool was removed and not replaced with anything.
I think there is a bit of confusion on what happened here and that's possibly
due to the phrasing of the description so I apologize for that. Those tools
were more or less exposing the sstable layout. 3.0 has completely and
profoundly changed that layout so those haven't been removed, their code has
been almost entirely invalidated by the changes made in 3.0 and we have to
re-implement them pretty much from scratch (we can salvage a couple lines of
code to deal with json but that's not really the problem). Which imply figuring
a decent way to expose the new layout (in json or otherwise) and I'm suggesting
we might as well try to do a better job than what we did for the previous
layout.
The only choice we did made is to not delay the 3.0 release until we had time
to deal with that rewrite because we figured some users may be fine starting to
use 3.0 without this (at least in development/for testing since let's be frank
here, few people will go in production with 3.x before probably 3.3/3.4 if not
later). I'm personally comfortable this wasn't an unreasonable choice.
But please be assured we haven't forgotten about this. It's just that we are
pretty early after the 3.0 release and we're somewhat prioritizing fixing our
known bugs (and fixing our damn dtests) before re-adding this. Which, here
again, I don't think is completely unreasonable. Hopefully, we'll soon have
fixed our most pressing bugs and will be able to devote resources to this. But
if you can't wait, this is open source ... :)
> 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)
