CASSANDRA-20081: Add compaction type and strategy properties to compaction history

[arvindKandpal-ksolves]

Currently, nodetool compactionhistory does not provide visibility into the specific type of compaction (e.g., Major, Minor, Validation) or the compaction strategy used (e.g., STCS, LCS). Additionally, the output displays raw bytes by default, which is difficult to read.

This patch enhances the compaction history by persisting the compaction type and strategy properties into the system.compaction_history table and exposing them via nodetool.

Changes included in this patch:

1. Schema Update: Added compaction_type column to system.compaction_history.
2. Logic Update: Updated CompactionTask to capture the compaction type (e.g., Major, Cleanup) and strategy class (e.g., SizeTieredCompactionStrategy) and persist them.
3. JMX/Tooling: Updated CompactionHistoryTabularData and nodetool compactionhistory printer to display these new fields.
4. UX Improvement: Changed nodetool compactionhistory to display human-readable sizes (KiB, MiB) by default. Added a -n / --no-human-readable flag to revert to raw bytes.
5. Tests: Updated SystemKeyspaceTest, CompactionTaskTest, and CompactionHistoryTest to cover schema changes and verify the persistence of new fields.

Tests Performed:

• ant test -Dtest.name=SystemKeyspaceTest (PASSED)
• ant test -Dtest.name=CompactionTaskTest (PASSED)
• ant test -Dtest.name=CompactionHistoryTest (PASSED)
• Manual verification using nodetool compactionhistory on a local node.

patch by arvindKandpal-ksolves ; for CASSANDRA-20081

[jyothsnakonisa]

Left few comments.

[jyothsnakonisa]

Can you please check SystemKeyspaceMigrator41.java? specifically migrateCompactionHistory() method. You might need to include compaction_type during migration.

[arvindKandpal-ksolves]

@jyothsnakonisa Thanks for the review. I have addressed all your comments:

1. Reverted nodetool flag changes to maintain backward compatibility.
2. Updated SystemKeyspaceMigrator41 and fixed upgrade tests.
3. Fixed code style, imports, and cleanup issues.
4. Ready for re-review.

[jyothsnakonisa]

@arvindKandpal-ksolves looks good to me mostly. Can you also run CI and update the report on the JIRA

[arvindKandpal-ksolves]

Hi @jyothsnakonisa , thanks for the approval!

Could you please tell me how I can trigger the CI and what need to update in JIRA , as I am contributing to the code segment in Cassandra first time ?

[jyothsnakonisa]

Hi @arvindKandpal-ksolves @smiklosovic might be able to help you with that. I generally run it on my organization's infrastructure. Also, can you please get it reviewed by one more committer. I saw @Guoma commenting on the JIRA, please check with him if he can do a second review.