[
https://issues.apache.org/jira/browse/CASSANDRA-18043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-18043:
------------------------------------------
Fix Version/s: 5.0
(was: 5.x)
Source Control Link:
https://github.com/apache/cassandra/commit/58a3b12508f97e44d3812f6c97e5a969dc6b5a1b
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
aligned dtest committed here
https://github.com/apache/cassandra-dtest/commit/dc6918d5e68a0849e8e38b7a49d0a822b95a6781
> remove deprecated DateTieredCompactionStrategy
> ----------------------------------------------
>
> Key: CASSANDRA-18043
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18043
> Project: Cassandra
> Issue Type: Task
> Components: Local/Compaction/DTCS
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 5.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> DTCS was marked as deprecated in CASSANDRA-9666 which was released in 3.0.8
> and 3.8. If I get our deprecation policies right, we wait one major release
> (4.0) and we can remove it in the next one (5.0). Having 4.1 about to be
> released soon and 4.2 will be 5.0, I think nothing blocks us from removing
> this strategy in trunk.
> This also makes CASSANDRA-18042 easier as it would most probably have to
> cover this strategy as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
