You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Paulo Motta (JIRA)" <ji...@apache.org> on 2016/03/10 16:00:50 UTC
[jira] [Created] (CASSANDRA-11337) Add --hex-key option to nodetool
getsstables
Paulo Motta created CASSANDRA-11337:
---------------------------------------
Summary: Add --hex-key option to nodetool getsstables
Key: CASSANDRA-11337
URL: https://issues.apache.org/jira/browse/CASSANDRA-11337
Project: Cassandra
Issue Type: Improvement
Components: Tools
Reporter: Paulo Motta
Priority: Minor
Sometimes it's useful to retrieve an sstable from the hex string representation of its key, for instance, when you get an exception like this and you want to find out which sstable owns the faulty key:
{noformat}
java.lang.AssertionError: row DecoratedKey(2769066505137675224, 00040000002e00000800000153441a3ef000) received out of order wrt DecoratedKey(2774747040849866654, 00040000019b0000080000015348847eb200)
{noformat}
In this case, {noformat}nodetool getsstables ks cf 00040000002e00000800000153441a3ef000{noformat} will only work if {{ks.cf}} has a blob primary key.
It's straightforward to retrieve a {{DecoratedKey}} from the hexstr representation of the key, so we should add a {{--hex-key}} option to allow for that.
{noformat}nodetool getsstables ks cf --hex-key 00040000002e00000800000153441a3ef000{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)