[
https://issues.apache.org/jira/browse/CASSANDRA-19104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793826#comment-17793826
]
Leo Toff commented on CASSANDRA-19104:
--------------------------------------
Got it, keeping KiB/MiB/GiB for now. We should probably get feedback from the
mailing list on this as well.
Regarding "compacted partitions", the spreadsheet is updated to use byte
quantifiers.
Regarding "zero bytes", looks like "0.00 KiB" is the preferred format according
to the discussion in the mailing list, so I'll go with that. However, I think
"0.00 KiB" is ambiguous since it might be interpreted as "something below 0.005
KiB", not necessarily "zero bytes". So my personal preference is "0 B" or "0
bytes". I'll be using "0.00 KiB" until corrected.
> Standardize tablestats formatting and data units
> ------------------------------------------------
>
> Key: CASSANDRA-19104
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19104
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/nodetool
> Reporter: Brad Schoening
> Assignee: Leo Toff
> Priority: Normal
>
> Tablestats reports output in plaintext, JSON or YAML. The human readable
> output currently has a mix of KiB, bytes with inconsistent spacing
> Considering simplifying and defaulting output to 'human readable'. Machine
> readable output is available as an option and the current mixed output
> formatting is neither friendly for human or machine reading.
> !image-2023-11-27-13-49-14-247.png!
> *Not a goal now (consider a follow up Jira):*
> Fix inconsistencies with KiB/MiB/GiB and KB/MB/GB formatting:
> * gcstats - uses MB
> * getcompactionthroughput - uses MB/s
> * getstreamthroughput - uses MB/s
> * info - uses MiB/GiB
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
