cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9618) Consider deprecating sstable2json/json2sstable in 2.2
Date Fri, 02 Oct 2015 20:56:32 GMT


Aleksey Yeschenko commented on CASSANDRA-9618:

[~java8964] You don't need to worry. There will absolutely be a new tool to replace it, in
3.x, something that makes more sense in post CASSANDRA-8099 world.

Now, as to whether or not using s2j and j2s to read the sstables programmatically (vs. using
them for debugging/educational purposes), is a different matter. It would be more efficient
to use something closer to {{SSTableReader}} without an intermediate transformation to JSON.

> Consider deprecating sstable2json/json2sstable in 2.2
> -----------------------------------------------------
>                 Key: CASSANDRA-9618
>                 URL:
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>             Fix For: 2.2.0 rc2
>         Attachments: 0001-Deprecate-sstable2json-and-json2sstable.patch
> The rational is explained in CASSANDRA-7464 but to rephrase a bit:
> * json2sstable is pretty much useless, {{CQLSSTableWriter}} is way more flexible if you
need to write sstable directly.
> * sstable2json is really only potentially useful for debugging, but it's pretty bad at
that (it's output is not really all that helpul in modern Cassandra in particular).
> Now, it happens that updating those tool for CASSANDRA-8099, while possible, is a bit
involved. So I don't think it make sense to invest effort in maintain these tools. So I propose
to deprecate these in 2.2 with removal in 3.0.
> I'll note that having a tool to help debugging sstable can be useful, but I propose to
add a tool for that purpose with CASSANDRA-7464.

This message was sent by Atlassian JIRA

View raw message