cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11483) Enhance sstablemetadata
Date Sat, 30 Apr 2016 01:08:12 GMT

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

Yuki Morishita commented on CASSANDRA-11483:
--------------------------------------------

On windows, this runs without problems.
I fixed some styling and ran tests.

||branch||testall||dtest||
|[11483|https://github.com/yukim/cassandra/tree/11483]|[testall|http://cassci.datastax.com/view/Dev/view/yukim/job/yukim-11483-testall/lastCompletedBuild/testReport/]|[dtest|http://cassci.datastax.com/view/Dev/view/yukim/job/yukim-11483-dtest/lastCompletedBuild/testReport/]|

As you can see in dtest, some of them rely on the output of sstablemetadata, so we either
fix those dtests as well, or support old output format.
Between those two, I prefer supporting old output format, since it can be least suprise for
user who rely on output of the tool as well.
WDYT?

> Enhance sstablemetadata
> -----------------------
>
>                 Key: CASSANDRA-11483
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11483
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Observability
>            Reporter: Chris Lohfink
>            Assignee: Chris Lohfink
>            Priority: Minor
>             Fix For: 3.x
>
>         Attachments: CASSANDRA-11483.txt, CASSANDRA-11483v2.txt, CASSANDRA-11483v3.txt,
CASSANDRA-11483v4.txt, Screen Shot 2016-04-03 at 11.40.32 PM.png
>
>
> sstablemetadata provides quite a bit of useful information but theres a few hiccups I
would like to see addressed:
> * Does not use client mode
> * Units are not provided (or anything for that matter). There is data in micros, millis,
seconds as durations and timestamps from epoch. But there is no way to tell what one is without
a non-trival code dive
> * in general pretty frustrating to parse



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message