[CASSANDRA-18049] Update Chronicle Queue

• Type: Task
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 5.0-alpha1, 5.0
• Epic Link: Support Java 17
• Complexity: Normal
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/eee211fdbb517c1b0e0a8635e0813bda7cf655e5 https://github.com/apache/cassandra-dtest/commit/24a677ac420ec64b98164c37a346dc5384582a7c

Test and Documentation Plan

CI

• Assignee: Michael Semb Wever
• Reporter: Ekaterina Dimitrova

Authors

Michael Semb Wever

Reviewers

Ekaterina Dimitrova

• Created: 15/Nov/22 15:40
• Updated: 12/Sep/23 13:03
• Resolved: 22/Mar/23 08:05

Description

According to this article:

Starting from chronicle-bom-2.22ea26, all new releases can be run under Java 17 when run on the class path (but not yet under the module path).

This BOM is newer than what we currently have in both 4.1 and trunk. 4.1 points in comments to https://mvnrepository.com/artifact/net.openhft/chronicle-bom/1.16.23 which I believe was just forgotten to be updated/removed. The versions we see correspond to this BOM https://mvnrepository.com/artifact/net.openhft/chronicle-bom/2.20.226

It is still older than chronicle-bom-2.22ea26 so we need to upgrade. I suggest we also add a comment again which BOM is considered, this makes things easier.

Further to running CI, review of the CHANGE logs needs to happen to ensure we do not miss anything that can impact us and it is not caught by our tests.

For testing with JDK17, please, contact e.dimitrova for latest branch and CI config (at this point feature branch in the cassandra repo does not exist)

 

Issue Links

• is blocked by: CASSANDRA-18247 Add CircleCI config files for J11+J17