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

Aleksei Zotov commented on CASSANDRA-16844:
-------------------------------------------

[~brandon.williams]

I put a small comment to 
[https://github.com/driftx/cassandra/commit/6299df9653e31ec8f6842b03b4be157ff0f06e4e].

[~adelapena]

+1 to rename _count_ to _sstables_, it seems to be clearer.

WRT columns order, there might be a backward-compatibility issue if someone 
parses the command's output. So I'm not sure whether it is permitted.

> Add number of sstables in a compaction to compactionstats output
> ----------------------------------------------------------------
>
>                 Key: CASSANDRA-16844
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16844
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tool/nodetool
>            Reporter: Brendan Cicchi
>            Assignee: Brandon Williams
>            Priority: Normal
>             Fix For: 4.x
>
>
> It would be helpful to know at a glance how many sstables are involved in any 
> running compactions. While this information can certainly be collected now, a 
> user has to grab it from the debug logs. I think it would be helpful for some 
> use cases to have this information straight from {{nodetool compactionstats}} 
> and then if the actual sstables involved in the compactions are desired, dive 
> into the debug.log for that. I think it would also be good to have this 
> information in the output of {{nodetool compactionhistory}}.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to