cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Zotov (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7464) Retire/replace sstable2json and json2sstable
Date Wed, 09 Jul 2014 06:08:04 GMT


Alexey Zotov commented on CASSANDRA-7464:


as I understand you are trying to propose more "cql-compatible" output, am I rigth? I came
to such conclusion because I do not now what is _partition_key_ and _static_block_ abstractions.
I will read about them a bit later. 
Actually my question is where is the row key for above output? Is it just missed?

Also I would like to try create a patch, but I'm confused by requirements for the output,
for me they are quite unclear. Could you, please, give me more details.

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