cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lohfink (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11483) Enhance sstablemetadata
Date Wed, 26 Oct 2016 21:01:58 GMT

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

Chris Lohfink commented on CASSANDRA-11483:
-------------------------------------------

It does
{{SimpleDateFormat("MM/dd/yyyy HH:mm:ss").format(new java.util.Date(unit.toMillis(time)));}}

which will use the machines local time zone. Adding a X to the format to include offset would
probably be good idea incase distributing the results.

> 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