cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremiah Jordan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7159) sstablemetadata command should print some more stuff
Date Fri, 29 Aug 2014 17:41:53 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14115544#comment-14115544
] 

Jeremiah Jordan commented on CASSANDRA-7159:
--------------------------------------------

2) or 3) WFM.  Maybe 2) here and a new ticket to do 3) in 3.0? Since 3 requires a new sstable
version?  Would be nice to have some schema stuff stored in the sstables, as the requirement
to read schema exists for all of the sstable reading tools.  (And reading schema actually
causes a commit log replay, so you have to do it with the node offline.)

> 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)

Mime
View raw message