cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Tolbert (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7464) Replace sstable2json and json2sstable
Date Mon, 21 Dec 2015 18:37:47 GMT


Andy Tolbert commented on CASSANDRA-7464:

[~JoshuaMcKenzie], we'd definitely both be interested and willing :).   I don't think it would
be too big of an effort to get it working with C*.  The only non-cli/logging dependency is
jackson, which C* already depends on (albeit an older version) so it shouldn't be too much

We took a best effort at coming up with an output format that we thought would be human readable
and familiar to those who previously used sstable2json, but definitely would be welcome to

> Replace sstable2json and json2sstable
> -------------------------------------
>                 Key: CASSANDRA-7464
>                 URL:
>             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
> 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

View raw message