cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lohfink (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7464) Replace sstable2json and json2sstable
Date Fri, 18 Dec 2015 02:25:47 GMT

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

Chris Lohfink commented on CASSANDRA-7464:
------------------------------------------

In meantime for people wanting a sstable2json tool, [~andrew.tolbert] and I have a version
here: https://github.com/tolbertam/sstable-tools that supports the 3.x versions currently.


bq. A key differentiator between the storage format between older verisons of Cassandra and
Cassandra 3.0 is that an SSTable was previously a representation of partitions and their cells
(identified by their clustering and column name) whereas with Cassandra 3.0 an SSTable now
represents partitions and their rows. You can read about these changes in more detail by visiting
this blog post. Additional improvements over the sstable2json tool includes no longer requiring
the cassandra.yaml in classpath with the schema of the sstables loaded. Also by running in
client mode this tool will not write to system tables or your commit log. It can safely be
run as any user anywhere with no side effects.

Its a little easier to run then older version as well. We are using this place as a playground
but it may be a good starter if updating tool in C* as well.

> 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)

Mime
View raw message