[
https://issues.apache.org/jira/browse/CASSANDRA-9618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596132#comment-14596132
]
Aleksey Yeschenko commented on CASSANDRA-9618:
----------------------------------------------
Should we write the warning to {{err}} instead? Printing to {{out}} might break
things for those who (wrongly or rightly) use sst2j and j2sst in an automated
fashion.
Otherwise +1.
> Consider deprecating sstable2json/json2sstable in 2.2
> -----------------------------------------------------
>
> Key: CASSANDRA-9618
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9618
> 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
(v6.3.4#6332)
