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

Brandon Williams commented on CASSANDRA-16844:
----------------------------------------------

bq. Found this patch and saw a tool using awk positional parsing, so would break

We should have really fleshed out CASSANDRA-5977 to the rest of nodetool so we 
wouldn't need to worry about this and neither would tool authors, but I guess 
virtual tables will eventually solve it.

> 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.1, 4.1-alpha1
>
>
> 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.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to