cassandra-commits mailing list archives

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

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

Romain Hardouin commented on CASSANDRA-11483:
---------------------------------------------

Having human readable data is very nice. 

What about using ISO 8601 to format the date? {{MM/dd}} is misleading in many countries and
can be understood as {{dd/MM}} when the day is below 13 e.g. 02/03/2016 -> Is it {{March,
2nd}} or {{Feb, 3rd}}? 

> 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