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

Michael Semb Wever commented on CASSANDRA-18061:
------------------------------------------------

bq. Am I correct we need to support 4.0 -> 5.0 upgrade so we need to migrate 
compaction_history to a new table?

Yes. All `(N-1).x.y` to `N.xx.yy` upgrade paths must be supported.

That also means that if the patch doesn't support upgrades from 3.x it cannot 
be committed while build.xml is at 4.2
(you would then change the fixVersion to 5.x and wait til build.xml is bumped, 
or enhance the patch to support 3.x upgrades)

> Add compaction type output result for nodetool compactionhistory
> ----------------------------------------------------------------
>
>                 Key: CASSANDRA-18061
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Local/Compaction, Tool/nodetool
>            Reporter: maxwellguo
>            Assignee: maxwellguo
>            Priority: Low
>             Fix For: 4.x
>
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to