Re: [DISCUSS] Gossip Protocol Change

Hi Cameron, Just want to make sure I understood correctly. So your observation was at the end of the shadow round, some nodes have empty endpointStateMap? But I read the code at GossipDigestSynVerbHandler::createShadowReply it seems that the receiving node will reply with a full stateMap? return

Re: [DISCUSS] Adding support for BETWEEN operator

I second Patrick about the parties and all that… Thanks, Simon for all your work! I am excited to see what’s next from you as I am sure it will be awesome! Cheers! On Thu, 16 May 2024 at 14:50, Jon Haddad wrote: > Benjamin, I’m +1 on adding BETWEEN, thanks for bringing this up. > > To all, my i

Re: [DISCUSS] Adding support for BETWEEN operator

Benjamin, I’m +1 on adding BETWEEN, thanks for bringing this up. To all, my intention wasn’t to suggest we add support for update between via range writes at the same time, if it came across that way i apologize for the confusion. Josh, thanks for the suggestion. If I feel inspired to discuss wit

Re: [DISCUSS] Gossip Protocol Change

> Sounds like the request was to hit the pause button until TCM merged rather > than skipping the work entirely so that's promising. Correct, I was only asked to wait a few days and to rebase after TCM merged. The issue was that I had to time box this work and the fact it hit issues kinda beca

Re: [DISCUSS] Gossip Protocol Change

I'm +1 to continuing work on CASSANDRA-18917 for all the reasons Jordan listed. Sounds like the request was to hit the pause button until TCM merged rather than skipping the work entirely so that's promising. On Thu, May 16, 2024, at 1:43 PM, Jon Haddad wrote: > I have also recently worked with

Re: [DISCUSS] Gossip Protocol Change

I have also recently worked with a teams who lost critical data as a result of gossip issues combined with collision in our token allocation. I haven’t filed a jira yet as it slipped my mind but I’ve seen it in my own testing as well. I’ll get a JIRA in describing it in detail. It’s severe enough

Re: [DISCUSS] Gossip Protocol Change

I’m a big +1 on 18917 or more testing of gossip. While I appreciate that it makes TCM more complicated, gossip and schema propagation bugs have been the source of our two worst data loss events in the last 3 years. Data loss should immediately cause us to evaluate what we can do better. We will li

Re: [DISCUSS] Adding support for BETWEEN operator

> More of a "how could we technically reach mars?" discussion than a "how we > get congress to authorize a budget to reach mars?" Wow - that is genuinely a great simile. Really good point. To Jeff's point - want to kick off a [DISCUSS] thread referencing this thread Jon so we can take the conver

Re: [DISCUSS] ccm as a subproject

> We do still have the issues of DSE-supporting code in it, as we do with the > drivers. I doubt any of us strongly object to it: there's no trickery > happening here on the user; but we should be aware of it and have a rough > direction sketched out for when someone else comes along wanting to

Re: [DISCUSS] NULL handling and the unfrozen collection issue

I found some other confusing behavior in LWT around null value and empty multicell collection. I opened CASSANDRA-19637 for those interested. Le jeu. 4 avr. 2024 à 18:34, Caleb Rackliffe a écrit : > The easiest way to check out how Accord us

Re: [DISCUSS] ccm as a subproject

+1 (my personal opinion) How to deal with the DSE-supporting code is a separate discussion IMO - - -- --- - - Jacek Lewandowski czw., 16 maj 2024 o 10:21 Berenguer Blasi napisał(a): > +1 ccm is super useful > On 16/5/24 10:09, Mick Semb Wever wrote: > > > > On Wed, 15

Re: [DISCUSS] ccm as a subproject

+1 ccm is super useful On 16/5/24 10:09, Mick Semb Wever wrote: On Wed, 15 May 2024 at 16:24, Josh McKenzie wrote: Right now ccm isn't formally a subproject of Cassandra or under governance of the ASF. Given it's an integral components of our CI as well as for local testing for m

Re: [DISCUSS] ccm as a subproject

On Wed, 15 May 2024 at 16:24, Josh McKenzie wrote: > Right now ccm isn't formally a subproject of Cassandra or under governance > of the ASF. Given it's an integral components of our CI as well as for > local testing for many devs, and we now have more experience w/our muscle > on IP clearance an