[
https://issues.apache.org/jira/browse/CASSANDRA-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14115344#comment-14115344
]
Sylvain Lebresne commented on CASSANDRA-7159:
---------------------------------------------
I don't think we save the comparator in any sstable component so I don't think
there is a good way to get the comparator without reading the schema. And
reading the schema means that you'd only be able to run sstablemetadata on a
configured node of the cluster, which I'm not sure is a limitation we want to
add.
I guess the options are:
# we do require a configured node for sstablemetadata to run, and we read the
schema.
# we writes the column names bytes as hex. Not sure how useful that is but why
not.
# we start storing the comparator in the "validation" metadata, use that and
don't print anything on the column names if we don't have it.
I don't have a super strong opinion on which to do tbh, but 3) sounds
reasonable to me.
> sstablemetadata command should print some more stuff
> ----------------------------------------------------
>
> Key: CASSANDRA-7159
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7159
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Jeremiah Jordan
> Assignee: Vladislav Sinjavin
> Priority: Trivial
> Labels: lhf
> Fix For: 2.0.11
>
> Attachments:
> CASSANDRA-7159_-_sstablemetadata_command_should_print_some_more_stuff.patch
>
>
> It would be nice if the sstablemetadata command printed out some more of the
> stuff we track. Like the Min/Max column names and the min/max token in the
> file.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
