[VOTE] Release Apache Cassandra 5.0.3

Proposing the test build of Cassandra 5.0.3 for release. sha1: b0226c8ea122c3e5ea8680efb0744d33924fd732 Git: https://github.com/apache/cassandra/tree/5.0.3-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1360/org/apache/cassandra/cassandra-all/5.0.3

[VOTE] Release Apache Cassandra 4.1.8

Proposing the test build of Cassandra 4.1.8 for release. sha1: 044727aabafeab2f6fef74c52d349d55c8732ef5 Git: https://github.com/apache/cassandra/tree/4.1.8-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1359/org/apache/cassandra/cassandra-all/4.1.8

[VOTE] Release Apache Cassandra 4.0.16

Proposing the test build of Cassandra 4.0.16 for release. sha1: c989c02be66411991c8536ca00ee6481f43e642e Git: https://github.com/apache/cassandra/tree/4.0.16-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1358/org/apache/cassandra/cassandra-all/4.0

[VOTE] Release Apache Cassandra 3.11.18

Proposing the test build of Cassandra 3.11.18 for release. sha1: 429f3ad83e1c9eff5c288a7c8fb4781939d00090 Git: https://github.com/apache/cassandra/tree/3.11.18-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1357/org/apache/cassandra/cassandra-all/3

[VOTE] Release Apache Cassandra 3.0.31

Proposing the test build of Cassandra 3.0.31 for release. sha1: 09e7a4d6ae23b7ac5c9867235c9d900d0c99649a Git: https://github.com/apache/cassandra/tree/3.0.31-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1356/org/apache/cassandra/cassandra-all/3.0

Re: [DISCUSS] 5.1 should be 6.0

Mick, There is a lot to respond to here and I think we might need a few other threads to avoid a spidering conversation but I wanted to respond to what I saw is at least part of the crux of your concern: our recommended upgrade paths. To take a snippet from your email "A little empathy for our use

Re: [DISCUSS] synchronisation of properties between Config.java and cassandra.yaml

Good point re: the implications of parsing and durability in the face of seeing unknown or missing parameters. I don't think widening the scope on that would be ideal, especially considering the entire impetus for this conversation is "we've misbehaved with our config and have a bunch of undocum

Re: [DISCUSS] synchronisation of properties between Config.java and cassandra.yaml

"we take "unclaimed" items and move them to their own InternalConfig.java or something" This is interesting. If we are meant to be still able to put these properties into cassandra.yaml (even they are "internal ones") and they would be just in InternalConfig.java for some basic separation of inter

Re: [DISCUSS] synchronisation of properties between Config.java and cassandra.yaml

This may be an off-base comparison, but this reminds me of struggles we've had getting to 0 failing unit tests before and the debates on fencing off a snapshot of the current "failure set" so you can have a set point where no further degradation is allowed in a primary data set. All of which is

Re: [DISCUSS] synchronisation of properties between Config.java and cassandra.yaml

Indeed, we need to balance that and thoughtfully choose what is going to be added and what not. However, we should not hide something which is meant to be tweaked by a user. The config is intimidating mostly because everything is just in one file. I merely remember discussions a few years ago which

Re: [DISCUSS] synchronisation of properties between Config.java and cassandra.yaml

Might be a bit of a balance between exposing what people actually are likely to need to modify vs having a super intimidating config file. It's already nearly 2000 lines. Personally I'd rather see some auto-documentation or something that's in the docs

Re: [DISCUSS] 5.1 should be 6.0

There's still a few open loops in this thread that I'd like to keep pushing on. I admit I've been pretty adamant that there's real value for a) users, operators, and ourselves, having an intuitive understanding of our recommended upgrade paths by versions, and b) a method to reduce the CI testing

Re: [DISCUSS] synchronisation of properties between Config.java and cassandra.yaml

I have compiled this table (1). It is editable by everybody. The idea behind that is that if people recognize they would like to have some property in cassandra.yaml exposed, just mark it as green, add a comment and some notes. It would be cool if we did this together as people who have introduced

[ANNOUNCE] Apache Cassandra 5.0.3 test artifact available

The test build of Cassandra 5.0.3 is available. sha1: b0226c8ea122c3e5ea8680efb0744d33924fd732 Git: https://github.com/apache/cassandra/tree/5.0.3-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1360/org/apache/cassandra/cassandra-all/5.0.3/ The So

[ANNOUNCE] Apache Cassandra 4.1.8 test artifact available

The test build of Cassandra 4.1.8 is available. sha1: 044727aabafeab2f6fef74c52d349d55c8732ef5 Git: https://github.com/apache/cassandra/tree/4.1.8-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1359/org/apache/cassandra/cassandra-all/4.1.8/ The So

[ANNOUNCE] Apache Cassandra 4.0.16 test artifact available

The test build of Cassandra 4.0.16 is available. sha1: c989c02be66411991c8536ca00ee6481f43e642e Git: https://github.com/apache/cassandra/tree/4.0.16-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1358/org/apache/cassandra/cassandra-all/4.0.16/ The

[ANNOUNCE] Apache Cassandra 3.11.18 test artifact available

The test build of Cassandra 3.11.18 is available. sha1: 429f3ad83e1c9eff5c288a7c8fb4781939d00090 Git: https://github.com/apache/cassandra/tree/3.11.18-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1357/org/apache/cassandra/cassandra-all/3.11.18/

[ANNOUNCE] Apache Cassandra 3.0.31 test artifact available

The test build of Cassandra 3.0.31 is available. sha1: 09e7a4d6ae23b7ac5c9867235c9d900d0c99649a Git: https://github.com/apache/cassandra/tree/3.0.31-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1356/org/apache/cassandra/cassandra-all/3.0.31/ The

Patch Available vs Needs Committer

Hello, This is just a reminder of the difference between these states. "Needs committer" is for when there is already one reviewer, and a second is needed (this state used to be called "Needs 2nd reviewer".) "Patch Available" is the state used when you need an initial review. If in doubt, use "Pat