Re: [ANNOUNCEMENT] Expect failures today. Dropping JDK 8 and adding JDK 11

2023-07-27 Thread Mick Semb Wever
> FYI, devbranch (pre-commit) on ci-cassandra.a.o is hardcoded to build on > jdk8 and jdk11 > so it's not going to work with trunk based patches… > > I'll review any patches to fix this, but otherwise focus is > on CASSANDRA-18594 where a standalone jenkinsfile avoids this problem > altogether. >

Re: Status Update on CEP-7 Storage Attached Indexes (SAI)

2023-07-27 Thread Jon Haddad
Very nice! I'll kick the tires a bit, and add a sai test to tlp-stress On 2023/07/26 18:56:29 Caleb Rackliffe wrote: > Alright, the cep-7-sai branch is now merged to trunk! > > Now we move to addressing the most urgent items from "Phase 2" ( > CASSANDRA-18473

Re: Status Update on CEP-7 Storage Attached Indexes (SAI)

2023-07-27 Thread Lorina Poland
I have to say how excited I am that I get to emphasize SAI as an indexing method for Apache C*, rather than the much less capable 2i! I have been waiting for this day for years! Thanks Caleb and all who worked to make this day a reality! Lorina On Wed, Jul 26, 2023 at 10:08 PM Berenguer Blasi

Re: [ANNOUNCEMENT] Expect failures today. Dropping JDK 8 and adding JDK 11

2023-07-27 Thread Ekaterina Dimitrova
CASSANDRA-18701 On Thu, 27 Jul 2023 at 13:10, Ekaterina Dimitrova wrote: > It seems there was some misunderstanding as dev-branch was on the list of > tasks to be fixed here. > > Anyway, I will work on a patch as I do not want to block people who are > using it, thanks. My understanding from a

Re: [ANNOUNCEMENT] Expect failures today. Dropping JDK 8 and adding JDK 11

2023-07-27 Thread Ekaterina Dimitrova
It seems there was some misunderstanding as dev-branch was on the list of tasks to be fixed here. Anyway, I will work on a patch as I do not want to block people who are using it, thanks. My understanding from a private conversation is that CASSANDRA-18594 might land in August-September so I

Re: [ANNOUNCEMENT] Expect failures today. Dropping JDK 8 and adding JDK 11

2023-07-27 Thread Mick Semb Wever
> I am working on dropping JDK 8 and adding JDK17 on trunk in both CI systems today. > This requires numerous patches in a few repos so you will be seeing more failures in CI throughout the day today, but it shouldn’t be anything more 爛 than what we have listed in the table of failures in

Re: August 5.0 Freeze (with waivers…) and a 5.0-alpha1

2023-07-27 Thread Josh McKenzie
+1 to what you've stated here Mick with a question: where did we land on flagging new features as experimental? Seems like it's an "at author's discretion" - search of the list turned up not too much structure there. Had a statement to that effect from Benjamin here

Re: [DISCUSS] Maintain backwards compatibility after dependency upgrade in the 5.0

2023-07-27 Thread Josh McKenzie
+1 to the change pre 5.0. Any committers have bandwidth to review https://issues.apache.org/jira/projects/CASSANDRA/issues/CASSANDRA-14667? PR can be found here: https://github.com/apache/cassandra/pull/2238/files On Thu, Jul 27, 2023, at 7:59 AM, Maxim Muzafarov wrote: > Bump this topic up

Re: [Discuss] Repair inside C*

2023-07-27 Thread Josh McKenzie
> The idea that your data integrity needs to be opt-in has never made sense to > me from the perspective of either the product or the end user. I could not agree with this more. 100%. > The current (and past) state of things where running the DB correctly > **requires* *running a separate

Re: August 5.0 Freeze (with waivers…) and a 5.0-alpha1

2023-07-27 Thread Ekaterina Dimitrova
+1 on freeze 1st August with the suggested waiver. Also, +1 on the idea for alpha 1, as long as we give straight upfront the right expectations to users. Now, when we added also JDK17 in CI, I want to encourage people to start testing it in their test environments and give us some feedback.

Re: [DISCUSS] Maintain backwards compatibility after dependency upgrade in the 5.0

2023-07-27 Thread Maxim Muzafarov
Bump this topic up for visibility as the code freeze is coming soon. This seems like a good change to include in 5.0 as this kind of library upgrade is more natural when the major version changes. It is still possible to postpone it to 6.0, but the main concern here is that the current version of

Re: August 5.0 Freeze (with waivers…) and a 5.0-alpha1

2023-07-27 Thread Miklosovic, Stefan
I plan to run few builds with Corretto etc and do few manual tests, I will try to push that as soon as possible but it might happen it will leak to the next week. From: Mick Semb Wever Sent: Thursday, July 27, 2023 0:27 To: dev Subject: August 5.0