Re: [VOTE] Release Apache Cassandra 3.11.19

The vote has passed with 4 binding +1s and no vetoes. On Thu, Feb 6, 2025 at 1:02 PM Brandon Williams wrote: > +1 > > Kind Regards, > Brandon > > On Thu, Feb 6, 2025 at 1:04 AM Štefan Miklošovič > wrote: > > > > Proposing the test build of Cassandra 3.11.19 for release. > > > > sha1: ecbafb5275

Re: [VOTE] Release Apache Cassandra 3.0.32

The vote has passed with 4 binding +1s and no vetoes. On Thu, Feb 6, 2025 at 1:02 PM Brandon Williams wrote: > +1 > > Kind Regards, > Brandon > > On Thu, Feb 6, 2025 at 1:00 AM Štefan Miklošovič > wrote: > > > > Proposing the test build of Cassandra 3.0.32 for release. > > > > sha1: c559cf89624

Re: [DISCUSS] Default Selection of 2i

+1 to going the YAML route w/ thisAlong with CASSANDRA-18112, and when defaulted to legacy 2i, the following process should be possible:1.) legacy 2i exists and serves queries2.) SAI index is added and begins building3.) SAI index build completes4.) use 18112 to exclude legacy 2i in test queries (a

[VOTE] Release Apache Cassandra Java Driver 4.19.0

Greetings all! I’m proposing the test build of Cassandra Java Driver 4.19.0 for release. sha1: 46444eaabdbd23e9231123198536d070e99aca27 Git: https://github.com/apache/cassandra-java-driver/tree/4.19.0 Maven Artifacts: https://rep

Re: [DISCUSS] Default Selection of 2i

Tossing out an idea without any knowledge of implementation details - could we use the SAI index when a partition key is provided, and legacy when none is? On Thu, Feb 6, 2025 at 1:59 PM Benedict wrote: > Oof, if nothing else it sounds like a bug that we prefer an unbuilt index > over a built on

Re: [DISCUSS] Default Selection of 2i

Oof, if nothing else it sounds like a bug that we prefer an unbuilt index over a built one when there’s a choice.It also sounds like a bug for SAI to self report as the best index without any consideration, but perhaps that is harder to address.On 6 Feb 2025, at 21:15, C. Scott Andreas wrote:Pref

Re: [DISCUSS] Default Selection of 2i

Preference for a yaml property and MBean. Briefly:– All other secondary index config is defined in yaml.– System properties are more cumbersome to manage in that they’re less structured and commingle JVM configuration with database configuration.– We need an MBean hot property so users can flip to

Re: [DISCUSS] Default Selection of 2i

System property works for me, even if I have to leave the default alone in 5.0.x On Thu, Feb 6, 2025 at 1:34 PM Jeremiah Jordan wrote: > Rather than changing the default, I would be +1 to making a system > property so that an operator who knows what they are doing could change > it. A little he

Re: [DISCUSS] Default Selection of 2i

Rather than changing the default, I would be +1 to making a system property so that an operator who knows what they are doing could change it. A little hesitant of just changing it outright in a patch release. On Feb 6, 2025 at 1:10:28 PM, Caleb Rackliffe wrote: > Hey everyone! > > I'll keep

[DISCUSS] Default Selection of 2i

Hey everyone! I'll keep this short. SASI and later SAI, in lieu of anything resembling a query planner, have always just greedily returned a min long from Index#getEstimatedResultRows(), thereby stealing the right to be used to execute the query even when a legacy 2i is present on the relevant col

Re: [VOTE] CEP-45: Mutation Tracking

After double checking my math, the vote passes for real. This time with 15 +1’s (6 nb) and no -1s. Thanks again! Blake On Thu, Feb 6, 2025, at 10:21 AM, Jake Luciani wrote: > +1 > > On Thu, Feb 6, 2025 at 8:37 AM J. D. Jordan wrote: > > > > +1 (nb) > > > > > On Feb 6, 2025, at 6:31 AM, Maxim

Re: [VOTE] CEP-45: Mutation Tracking

+1 On Thu, Feb 6, 2025 at 8:37 AM J. D. Jordan wrote: > > +1 (nb) > > > On Feb 6, 2025, at 6:31 AM, Maxim Muzafarov wrote: > > > > +1 (nb) > > > >> On Thu, 6 Feb 2025 at 05:34, Patrick McFadin wrote: > >> > >> +1 > >> > >>> On Wed, Feb 5, 2025 at 8:15 PM C. Scott Andreas > >>> wrote: > >>> >

Re: [VOTE] CEP-45: Mutation Tracking

+1 (nb) > On Feb 6, 2025, at 6:31 AM, Maxim Muzafarov wrote: > > +1 (nb) > >> On Thu, 6 Feb 2025 at 05:34, Patrick McFadin wrote: >> >> +1 >> >>> On Wed, Feb 5, 2025 at 8:15 PM C. Scott Andreas >>> wrote: >>> >>> +1 >>> On Feb 5, 2025, at 2:50 PM, Alex Petrov wrote: >>> >>> >>>

Re: [VOTE] CEP-45: Mutation Tracking

+1 (nb) On Thu, 6 Feb 2025 at 05:34, Patrick McFadin wrote: > > +1 > > On Wed, Feb 5, 2025 at 8:15 PM C. Scott Andreas wrote: > > > > +1 > > > > On Feb 5, 2025, at 2:50 PM, Alex Petrov wrote: > > > > > > +1 > > > > On Wed, Feb 5, 2025, at 11:03 PM, Blake Eggleston wrote: > > > > Ok ok, I've jum

Re: [VOTE] Release Apache Cassandra 3.11.19

+1 Kind Regards, Brandon On Thu, Feb 6, 2025 at 1:04 AM Štefan Miklošovič wrote: > > Proposing the test build of Cassandra 3.11.19 for release. > > sha1: ecbafb52750f1a2ab8523cbd7cc88c760dd3632b > Git: https://github.com/apache/cassandra/tree/3.11.19-tentative > Maven Artifacts: > https://repos

Re: [VOTE] Release Apache Cassandra 4.0.17

+1 Kind Regards, Brandon On Thu, Feb 6, 2025 at 4:31 AM Mick Semb Wever wrote: > > Proposing the test build of Cassandra 4.0.17 for release. > > sha1: 0354c915a9f8be6ab671af5ff93b8178e6f2e76f > Git: https://github.com/apache/cassandra/tree/4.0.17-tentative > Maven Artifacts: > https://repository

Re: [VOTE] Release Apache Cassandra 3.0.32

+1 Kind Regards, Brandon On Thu, Feb 6, 2025 at 1:00 AM Štefan Miklošovič wrote: > > Proposing the test build of Cassandra 3.0.32 for release. > > sha1: c559cf89624802fdb770e6ea962b45f102e48224 > Git: https://github.com/apache/cassandra/tree/3.0.32-tentative > Maven Artifacts: > https://reposit

Re: [VOTE] Release Apache Cassandra 4.0.17

+1 > On 6 Feb 2025, at 10:31, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 4.0.17 for release. > > sha1: 0354c915a9f8be6ab671af5ff93b8178e6f2e76f > Git: https://github.com/apache/cassandra/tree/4.0.17-tentative > Maven Artifacts: > https://repository.apache.org/content/repos

Re: [VOTE] Release Apache Cassandra 3.0.32

+1 > On 6 Feb 2025, at 07:00, Štefan Miklošovič wrote: > > Proposing the test build of Cassandra 3.0.32 for release. > > sha1: c559cf89624802fdb770e6ea962b45f102e48224 > Git: https://github.com/apache/cassandra/tree/3.0.32-tentative > Maven Artifacts: > https://repository.apache.org/content/re

Re: [VOTE] Release Apache Cassandra 3.11.19

+1 > On 6 Feb 2025, at 07:02, Štefan Miklošovič wrote: > > Proposing the test build of Cassandra 3.11.19 for release. > > sha1: ecbafb52750f1a2ab8523cbd7cc88c760dd3632b > Git: https://github.com/apache/cassandra/tree/3.11.19-tentative > Maven Artifacts: > https://repository.apache.org/content/

Re: [VOTE] Release Apache Cassandra 4.0.17

. > The vote will be open for 24 hours (longer if needed). Everyone who > has tested the build is invited to vote. Votes by PMC members are > considered binding. A vote passes if there are at least three binding > +1s and no -1's. +1 Checked - signing correct - checksums are correct - so

[VOTE] Release Apache Cassandra 4.0.17

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

Re: [VOTE] Release Apache Cassandra 3.11.19

. > The vote will be open for 24 hours (longer if needed). Everyone who has > tested the build is invited to vote. Votes by PMC members are considered > binding. A vote passes if there are at least three binding +1s and no -1's. > +1 Checked - signing correct - checksums are correct - so

Re: [VOTE] Release Apache Cassandra 3.0.32

. > The vote will be open for 24 hours (longer if needed). Everyone who has > tested the build is invited to vote. Votes by PMC members are considered > binding. A vote passes if there are at least three binding +1s and no -1's. > +1 Checked - signing correct - checksums are correct -