You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Arvind Kandpal (Jira)" <ji...@apache.org> on 2025/12/22 07:25:00 UTC
[jira] [Assigned] (CASSANDRA-20081) Enhance nodetool compactionhistory to report compaction type and strategy
[ https://issues.apache.org/jira/browse/CASSANDRA-20081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arvind Kandpal reassigned CASSANDRA-20081:
------------------------------------------
Assignee: Arvind Kandpal
> Enhance nodetool compactionhistory to report compaction type and strategy
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-20081
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20081
> Project: Apache Cassandra
> Issue Type: New Feature
> Components: Tool/nodetool
> Reporter: Brad Schoening
> Assignee: Arvind Kandpal
> Priority: Normal
>
> It would be useful for compactionhistory to have:
> a) updated documentation for nodetool [compactionhistory |https://cassandra.apache.org/doc/stable/cassandra/tools/nodetool/compactionhistory.html] describing the columns *rows_merged* and {*}compaction_properties{*}. This StackOverflow article provides a good descriptions of rows_merged: [What does rows_merged mean in compactionhistory|https://stackoverflow.com/questions/27566558/what-does-rows-merged-mean-in-compactionhistory]
> b) the compaction strategy used: STCS, LCS, TWCS, UCS and sub-properties. For example, with level, the from-level and to-level could be reported.
> c) also useful would be to make the bytes in and out human readable by default, since there is already an -f option for machine readable output.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org