Re: Request for Wiki access to create CEP

2025-06-03 Thread Brandon Williams
Your account should have access now. Kind Regards, Brandon On Tue, Jun 3, 2025 at 4:20 PM Kokoori, Shylaja wrote: > > Hi, > > I would like to submit a CEP and I don't have access to the wiki. > > If someone with access could provide permission to wiki ID 'shylaja', would > be much appreciated.

Request for Wiki access to create CEP

2025-06-03 Thread Kokoori, Shylaja
Hi, I would like to submit a CEP and I don't have access to the wiki. If someone with access could provide permission to wiki ID 'shylaja', would be much appreciated. Thank you, Shylaja Kokoori

Re: [DISCUSS] How we handle JDK support

2025-06-03 Thread Josh McKenzie
> 1) As you said, in trunk, we would go with the latest language level features > and if we backported and these language features are not present there > because of older JDK, the patch would need to be rewritten to comply. We already have plenty of cases where we have to write a patch for one b

Re: [DISCUSS] CEP-48: First-Class Materialized View Support

2025-06-03 Thread Blake Eggleston
> Adds overhead in the hot path due to maintaining indexes. Extra memory needed > during write path and compaction. I’d make the same argument about the overhead of maintaining the index that Jon just made about the disk space required. The relatively predictable overhead of maintaining the ind

Re: [DISCUSS] How we handle JDK support

2025-06-03 Thread Štefan Miklošovič
Hi Josh, One observation, you wrote: "Backports from trunk to older branches that utilize the latest language level would need to be refactored to work on older branches." This is interesting. There are two possibilities 1) As you said, in trunk, we would go with the latest language level featu

Re: [DISCUSS] How we handle JDK support

2025-06-03 Thread Josh McKenzie
I was attempting to convey the language level support for a given branch at any snapshot in time; my reading of Doug's email was for something that shouldn't be a problem with this new paradigm (since we would be doing bugfixes targeting oldest then merge up, and new improvements and features sh

Re: [DISCUSS] How we handle JDK support

2025-06-03 Thread Mick Semb Wever
What's difficult for me to grok here is you're treating each branch as static, while the discussion has already evolved to branches evolving over time (with jdks being back-ported, etc). Might be more helpful to explain states and events at different points of branch lifecycles… On Tue, 3 Jun 202

Re: Accepting AI generated contributions

2025-06-03 Thread scott
So the general concern we're talking about is identifying/avoiding cases in which a community member has contributed code generated with the support of a model that has reproduced training data verbatim, posing copyright risk to the Apache Cassandra project. Work in this area seems early, but t