[
https://issues.apache.org/jira/browse/CASSANDRA-18314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783522#comment-17783522
]
Stefan Miklosovic commented on CASSANDRA-18314:
-----------------------------------------------
There is one bug so far I found, that is, we removed "too much" from
HintDescriptor and this need to go back (1).
I am in the process of fixing this and making sure hints from times of 3.0 and
4.0 are indeed possible to be read in 5.0. I think these fixes might to in via
CASSANDRA-19002.
Hence, at the end of this effort in 19002, we should have tests for sstables,
commit logs and hints and that all is readable from times of 3.0 and newer.
(1)
https://github.com/instaclustr/cassandra/commit/b1f0e2934da2776fe7835b5b87fdfda6e5ca29f5#diff-8223ad998e5ecde3546ee32f657e7e870ce62bf5d91674246fd36fa8a9b50226
> Lift MessagingService.minimum_version to 40
> -------------------------------------------
>
> Key: CASSANDRA-18314
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18314
> Project: Cassandra
> Issue Type: Task
> Components: Messaging/Internode
> Reporter: Michael Semb Wever
> Assignee: Michael Semb Wever
> Priority: Normal
> Fix For: 5.0, 5.0-alpha1
>
> Time Spent: 15h 20m
> Remaining Estimate: 0h
>
> MessagingService's VERSION_30 and VERSION_3014 don't have to be supported in
> Cassandra 5.0 anymore.
> (Cassandra 5.0 currently is still using VERSION_40)
> Patch:
> https://github.com/apache/cassandra/compare/trunk...thelastpickle:cassandra:mck/18314/trunk
> Raises the question whether backward compatibility to the previous major is
> defined by the Cassandra version or by the internal component version
> (MessagingService).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
