Re: Looking for Cassandra Forward topics and speakers

2025-01-30 Thread Patrick McFadin
Awesome! Thank you Maxim and Carlos. DM incoming. I have 2 hours of content between DMs and replies here if each talk is 15 minutes. This will be a great preview tour of Cassandra.next() I say that except TCM. We still need somebody to take that on and, at a minimum, explain what it is and how it

Re: Capabilities

2025-01-30 Thread Štefan Miklošovič
On Wed, Jan 29, 2025 at 8:15 PM David Capwell wrote: > One motivating case for TCM vs non-TCM… When accord processes the user > request, we can make sure to use the configs as they were at the execution > epoch… by splitting this out it makes all configs non-deterministic from > Accord’s point of

Re: Looking for Cassandra Forward topics and speakers

2025-01-30 Thread Maxim Muzafarov
Hello community, Patrick, I can also prepare some PP slides (status, design, and progress) and a short talk for: - CQL Management API If you can help, option 2 sounds good to me. On Thu, 30 Jan 2025 at 11:30, Rolo, Carlos via dev wrote: > > Hello Patrick, > > Count me in! > > I would like to p

Re: Looking for Cassandra Forward topics and speakers

2025-01-30 Thread Rolo, Carlos via dev
Hello Patrick, Count me in! I would like to pick either - CQL Management API: Can we just celebrate the end of JMX hell potentially? Who can talk about this? Or - SAI enhancements were recently highlighted by Caleb on the ML. This isn't just a one-and-done feature, and its future is really c

Re: [DISCUSS] 5.1 should be 6.0

2025-01-30 Thread Mick Semb Wever
. > If you mean only 4.1 and 5.0 would be online upgrade targets, I would > suggest we change that to T-3 so you encompass all “currently supported” > releases at the time the new branch is GAed. > > I think that's better actually, yeah. I was originally thinking T-2 from > the "what calendar