[
https://issues.apache.org/jira/browse/CASSANDRA-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106824#comment-14106824
]
Sylvain Lebresne commented on CASSANDRA-7159:
---------------------------------------------
bq. there is a ByteBufferUtil class and it look's like it can deserialize
correctly column names
You might want to make sure you understand what the "column names" are in that
context. What the min/maxColumnNames in the SSTableMetadata stores is the min
and max values for each component of the *internal column* (not CQL column)
names contained in the sstable (I would argue that min/maxColumnNames is bad
naming in that case and we should probably not use some better designation in
the output of sstablemetadata that this issue will add). Those value are not a
all guaranteed to be strings, so ByteBufferUtil.string() won't work in general.
The comparator however has the type for each of those components.
bq. Probably we can get an instance of the ColumnFamilyStore
(Keyspace.open(KEYSPACE1).getColumnFamilyStore("Counter1"))
Let's not get there. As I mentioned, those values are stored in the Summary
file, so let's just read them from there.
> 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
>
> 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)
