Re: [DISCUSS] LWT conditions behavior on collections is inconsistent (CASSANDRA-19637)

Hey Benjamin, Thanks for the fix and raising the point here. The patch seems reasonable to me. The only thing to confirm on my mind is whether people consider it behavior breaking change or only a bug fix. Based on that we can move forward with patch for 4.0+ or only trunk. It will be also good

Re: [DISCUSS] Stream Pipelines on hot paths

+1 to ban them, considering we also do not have any regular performance testing as part of the project test suites. Jacek has a good point about the checkstyle - there is separate one for tests. Though I would not object if people want them banned from tests too. I guess if we ban them this would

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

Re: discuss: add to_human_size function

to GIBIBYTES and respective methods on them which convert from >> that unit to whatever else. Is this OK to be used for the purposes of this >> feature? I would expect that once we have units like these and methods on >> them to convert from-to, it can be reused in where

Re: discuss: add to_human_size function

like. > > On Thu, Apr 25, 2024 at 3:36 PM Ekaterina Dimitrova > wrote: > >> Quick comment: >> >> DataRateSpec, DataStorageSpec, or DurationSpec >> - we intentionally do not support going smaller to bigger size in those >> classes which are specific

Re: discuss: add to_human_size function

Edit: I meant to say smaller to bigger unit, not size, sorry On Thu, 25 Apr 2024 at 6:35, Ekaterina Dimitrova wrote: > Quick comment: > > DataRateSpec, DataStorageSpec, or DurationSpec > - we intentionally do not support going smaller to bigger size in those > classes whi

Re: discuss: add to_human_size function

Quick comment: DataRateSpec, DataStorageSpec, or DurationSpec - we intentionally do not support going smaller to bigger size in those classes which are specific for cassandra.yaml - precision issues. Please keep it that way. That is why the notion of min unit was added in cassandra.yaml for

Re: Welcome Alexandre Dutra, Andrew Tolbert, Bret McGuire, Olivier Michallat as Cassandra Committers

Congrats and thank you for all your work on the drivers! On Wed, 17 Apr 2024 at 13:17, Francisco Guerrero wrote: > Congratulations everyone! > > On 2024/04/17 17:14:34 Abe Ratnofsky wrote: > > Congrats everyone! > > > > > On Apr 17, 2024, at 1:10 PM, Benjamin Lerer wrote: > > > > > > The

Re: Default table compression defined in yaml.

Any new settings are expected to be added in the new format On Tue, 19 Mar 2024 at 5:52, Bowen Song via dev wrote: > I believe the `foobar_in_kb: 123` format in the cassandra.yaml file is > deprecated, and the new format is `foobar: 123KiB`. Is there a need to > introduce new settings entries

Re: Welcome Brad Schoening as Cassandra Committer

Congrats and thank you for everything, Brad! 拾 On Wed, 21 Feb 2024 at 15:46, Josh McKenzie wrote: > The Apache Cassandra PMC is pleased to announce that Brad Schoening has > accepted > the invitation to become a committer. > > Your work on the integrated python driver, launch script

Re: [Discuss] "Latest" configuration for testing and evaluation (CASSANDRA-18753)

Thanks for opening an epic @Jacek. It seems the dtest_offheap job is replaced by dtest_latest which means we will have the same amount of jobs after the current ticket and I am not worried about Jenkins. Though in CircleCI we did not have the dtest_offheap job mandatory run pre-commit but as far

Re: [Discuss] "Latest" configuration for testing and evaluation (CASSANDRA-18753)

> > Perhaps this was needed during j17 stabilization but is no longer required? No, I only switched from tests running J8+J11 to tests running J11+J17. What we tested was something decided in the 4.0 era when JDK11 was added, and I was not even part of the community yet :-) > Any known

Re: [Discuss] "Latest" configuration for testing and evaluation (CASSANDRA-18753)

> > I'm ok with breaking trunk CI temporarily as long as failures are tracked > and triaged/addressed before the next release. >From the ticket, I understand it is meant for 5.0-rc I share this sentiment for the release we decide to ship with: > The failures should block release or we should

Re: Welcome Maxim Muzafarov as Cassandra Committer

Congrats, Maxim! Well deserved! Thank you for everything! On Mon, 8 Jan 2024 at 13:26, Jeremiah Jordan wrote: > Congrats Maxim! Thanks for all of your contributions! > > On Jan 8, 2024 at 12:19:04 PM, Josh McKenzie wrote: > >> The Apache Cassandra PMC is pleased to announce that Maxim

Re: Welcome Mike Adamson as Cassandra committer

Great news! Congrats, Mike!! Thank you for all your hard work!!! On Fri, 8 Dec 2023 at 9:55, Jeremiah Jordan wrote: > Congrats Mike! Thanks for all your work on SAI and Vector index. Well > deserved! > > On Dec 8, 2023 at 8:52:07 AM, Brandon Williams wrote: > >> Congratulations Mike! >> >>

Re: Pre-commit (devbranch) ci-cassandra.a.o on 5.0 and trunk unavailable

Jenkins Trunk is also not running post commit at the moment - pending https://issues.apache.org/jira/browse/CASSANDRA-19083 On Wed, 29 Nov 2023 at 3:38, Mick Semb Wever wrote: > > For broader awareness. > > The debranch job on ci-cassandra.a.o: that used for pre-commit testing; is > currently

Re: [DISCUSSION] CASSANDRA-19001 - JRE vs JDK runtime

Thanks, Mick It seems that no one had objections to your suggestion so I will move forward with that: “I suggest, for expediency, to - put a nice failure message in Sjk.java (e.g. "JDK required for this nodetool command"), - add a comment in cassandra.yaml in front of audit_logging_options

Re: CEP-21 - Transactional cluster metadata merged to trunk

I hate to say it, but I was disappointed that this email thread was started after the TCM work had already been committed. Especially knowing how we had even an epic with patches spread around the codebase, which are waiting on TCM to get committed first so that we do not disturb any rebase. The

Re: Welcome Francisco Guerrero Hernandez as Cassandra Committer

Congrats Francisco! Well deserved ! On Tue, 28 Nov 2023 at 14:08, J. D. Jordan wrote: > Congrats! > > > On Nov 28, 2023, at 12:57 PM, C. Scott Andreas > wrote: > > > > Congratulations, Francisco! > > > > - Scott > > > >> On Nov 28, 2023, at 10:53 AM, Dinesh Joshi wrote: > >> > >> The PMC

Re: [VOTE] Release Apache Cassandra 5.0-beta1

“The QA label is part of our version number and that's baked in.” How can we have beta 2, but there is no way for alpha 2? On Tue, 28 Nov 2023 at 13:55, Mick Semb Wever wrote: > > > On Tue, 28 Nov 2023 at 19:27, J. D. Jordan > wrote: > >> That said. This is clearly better than and with many

Re: [DISCUSS] Harry in-tree

+1, also, Alex, just an idea - maybe you want to make a virtual talk, as part of the contributors meetings? На понеделник, 27 ноември 2023 г. Yifan Cai написа: > +1 > -- > *发件人:* Sam Tunnicliffe > *发送时间:* Tuesday, November 28, 2023 2:43:51 AM > *收件人:* dev > *主题:*

[DISCUSSION] CASSANDRA-19001 - JRE vs JDK runtime

Hi everyone, Some of you remember that Paulo raised a concern around warnings about missing modules on startup during the 5.0 alpha2 voting.[1] We opened the ticket CASSANDRA-19001. The problem turned out to be not a 5.0 one. Those modules are missing when we run Cassandra on JRE. Those warnings

Re: [VOTE] Release Apache Cassandra 5.0-alpha2

1. “No objections from me since these issues are mostly cosmetic, but it would be nice to clear these before the next alpha/beta. I will create a ticket for the unknown module warning later if nobody beats me to it.” 1. 1. CASSANDRA-19001

Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2)

Totally agree with the others. Such an issue on its own should be a priority in any release. Looking forward to the reproduction test mentioned on the ticket. Thanks to Alex for his work on harry! On Sat, 4 Nov 2023 at 12:47, Benedict wrote: > Alex can confirm but I think it actually turns out

Re: [VOTE] Release Apache Cassandra 5.0-alpha2

this topic. On Fri, 3 Nov 2023 at 21:07, Ekaterina Dimitrova wrote: > Hi Paulo, > > Thank you for testing and for raising the issue! > I can confirm I do not use the same JDK as you, and I did not see any > warnings on my machine on startup or when calling nodetool commands

Re: [VOTE] Release Apache Cassandra 5.0-alpha2

Hi Paulo, Thank you for testing and for raising the issue! I can confirm I do not use the same JDK as you, and I did not see any warnings on my machine on startup or when calling nodetool commands. I believe on a quick check that jdk.attach was needed for nodetool sjk. (It was mentioned on

Re: Push TCM (CEP-21) and Accord (CEP-15) to 5.1 (and cut an immediate 5.1-alpha1)

Benedict, what is your expectation for stabilization time? And what is the suggestion for the patches Benjamin mentioned, which are on their way to land in trunk? (Or any other patch on its way to be merged) On Thu, 26 Oct 2023 at 8:20, Benedict wrote: > The time to stabilise is orthogonal to

Re: Push TCM (CEP-21) and Accord (CEP-15) to 5.1 (and cut an immediate 5.1-alpha1)

Hi everyone, Thanks, Mick, for raising the topic. I support having released 5.0 without waiting on Accord and TCM as previously discussed here. (we are almost November, and the features are not ready. The currently committed set is glamorous in its own way :-)

Re: Development Dependencies documentation.

Hi Claude, You are not wrong. Unfortunately, it is outdated. Abe Ratnofsky has a work in progress patch. You might want to get in touch with him to finish it. Best regards, Ekaterina On Wed, 25 Oct 2023 at 8:04, Claude Warren, Jr via dev < dev@cassandra.apache.org> wrote: > I just had to change

Re: CASSANDRA-18775 (Cassandra supported OSs)

+1 on removal the whole lib if we are sure we don’t need it. Nothing better than some healthy house cleaning -1 on partial removals On Fri, 20 Oct 2023 at 17:34, David Capwell wrote: > +1 to drop the whole lib… > > > On Oct 20, 2023, at 7:55 AM, Jeremiah Jordan > wrote: > > Agreed. -1 on

Re: [DISCUSS] putting versions into Deprecated annotations

I’ve been told in the past not to remove public methods in a patch release though. On Fri, 13 Oct 2023 at 8:03, Benjamin Lerer wrote: > Could you point me some document / ML thread this was explicitly decided >> in if you know of anything like that? It would be great if there was some >> solid

Re: [VOTE] Accept java-driver

+1(nb), thank you for making it happen! На вторник, 3 октомври 2023 г. Dinesh Joshi написа: > +1 > > This is great for the project. Thank you for all the hard work everyone > put into this! It has been a long journey to get to this point. > > Dinesh > > On Oct 2, 2023, at 9:53 PM, Mick Semb

Re: [DISCUSS] Add JVector as a dependency for CEP-30

For my understanding, isn’t it gonna be an issue to be copyrighted also to a single person? For the same reasons? On Fri, 22 Sep 2023 at 7:59, Mick Semb Wever wrote: > > > Just for my understanding on this. Is the issue that the code has a >> copyright header on it or that it is copyright to a

Re: [DISCUSS] Backport CASSANDRA-18816 to 5.0? Add support for repair coordinator to retry messages that timeout

+1 from me too. Moreover, this work has started as part of the test efforts and identifying weak points during the 4.0 testing, if I recall correctly. 5.0 sounds like a good place to land. Thank you David and everyone else involved for your efforts! On Thu, 21 Sep 2023 at 1:01, Berenguer Blasi

Re: [DISCUSS] Addition of smile-nlp test dependency for CEP-30

Jeff, isn’t this ok as long as it is used only in tests? If we are not sure we can open a Jira to legal? On Wed, 13 Sep 2023 at 12:23, Jeff Jirsa wrote: > Just to be clear - this repo? > https://github.com/haifengl/smile/blob/master/LICENSE > > That shows GPL + Commercial? > > > > On Wed, Sep

Re: [DISCUSS] Update default disk_access_mode to mmap_index_only on 5.0

Thanks for starting this discussion, Paulo! Shall we also share this thread with @user? On Wed, 6 Sep 2023 at 16:35, C. Scott Andreas wrote: > Supportive of switching the default to mmap_index_only as well. > > I don’t have numbers handy to share, but my experience has been > significantly

Re: [DISCUSSION] Dependency management in our first alpha release

ache.org/jira/browse/CASSANDRA-18799 > > On Fri, 25 Aug 2023 at 18:39, Ekaterina Dimitrova > wrote: > > > > Thank you all. We are going to continue with those tickets and related > problems then. > > > > On Maxim's question: > > "Do we need a separate issu

Re: [DISCUSSION] Dependency management in our first alpha release

l have a path forward if they need similar functionality. > > On Aug 23, 2023, at 07:28, Ekaterina Dimitrova > wrote: > > I also want to hear if Abe still has concerns about not following > deprecation process here. > >

Re: [DISCUSSION] Shall we remove ant javadoc task?

avadocs as errorneous. > > There are other checkboxes as well. I am not saying it solves it all but > there is some room for tweaking this if one wishes. > > ____ > From: Ekaterina Dimitrova > Sent: Monday, August 21, 2023 20:05 > To: dev@ca

Re: [VOTE] Release Apache Cassandra 5.0-alpha1

+1 On Fri, 25 Aug 2023 at 11:14, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 5.0-alpha1 for release. > > DISCLAIMER, this alpha release does not contain the expected 5.0 > features: Vector Search (CEP-30), Transactional Cluster Metadata > (CEP-21) and Accord Transactions

[DISCUSSION] Dependency management in our first alpha release

Hi everyone, I wanted to clarify something. I understood dependency updates/cleaning can also be done in an alpha release if they lead to minimal user-facing changes, if any at all. I agree with that in our first 5.0 alpha release because we are not yet feature-complete. It is a good time for

[DISCUSSION] News and announcements, help needed

Hey friends, The 5.0 alpha test build is out for testing! Great! Did you also have the chance to attend any of the latest town halls? Ok, it is time to say where I am going with this short intro... Our friends from Constantia are working hard to help us spread the news and promote all the great

Re: [DISCUSSION] Shall we remove ant javadoc task?

push it through On Thu, 17 Aug 2023 at 12:46, Mick Semb Wever wrote: > +1 to `ant check` (and to failing on it). > > On Thu, 17 Aug 2023 at 18:43, Ekaterina Dimitrova > wrote: > >> Agreed with Maxim. If we fail CI on the javadoc task, in my opinion it >> should be

[DISCUSSION] CASSANDRA-18772 - removal of commons-codec on trunk

Hi everyone, I propose we remove commons-codec on trunk. The only usage I found was from CASSANDRA-12790 * - *Support InfluxDb metrics reporter configuration, which relied on commons-codec and metrics-reporter-config, which will be removed as

Re: [DISCUSSION] Shall we remove ant javadoc task?

should fail if it regresses so > > we can keep it this way. > > > > Kind Regards, > > Brandon > > > > On Thu, Aug 17, 2023 at 10:49 AM Ekaterina Dimitrova > > wrote: > > > > > > In CASSANDRA-18717 Maxim posted the javadoc fix. Stefan alrea

Re: [DISCUSSION] Shall we remove ant javadoc task?

sense. Could even add them to > our site with something like an "API" section (gasp) here: > https://cassandra.apache.org/doc/latest/. > > Would certainly help motivate us to clarify the whole "what is an external > API we're committing to or not" d

Re: [DISCUSS] CASSANDRA-18743 Deprecation of metrics-reporter-config

“ The rationale for this proposed deprecation is that the upcoming 5.0 release is a good time to evaluate dependencies that are no longer receiving updates and will become risks in the future.” Thank you for raising it, I support your proposal for deprecation On Fri, 11 Aug 2023 at 8:55, Abe

Re: Timing of the last releases of Cassandra 3.0.x / 3.11.x

I agree, we have enough for a release of 3.0 and 3.11 and if there are users expecting it, I don’t see a reason why not to cut releases. Shall we do it together with 5.0 alpha? There was a mention that one might be cut soon, as far as I recall. Just thinking it might be easier to do the releases

Re: [DISCUSS] Creating a 5.0 landing page

p in case someone missed it. > > On Thu, Aug 3, 2023, at 4:21 PM, Ekaterina Dimitrova wrote: > > > Hi Hugh, > > Thank you for reaching out. I think this is a great idea. Also, great > timing, considering the community is discussing a potential 5.0 alpha > release soon. > > It

Re: [DISCUSSION] Shall we remove ant javadoc task?

apache/cassandra/compare/trunk...Mmuzaf:cassandra:javadoc_build > > On Thu, 3 Aug 2023 at 21:20, Ekaterina Dimitrova > wrote: > > > > Thank you Maxim, > > > > “ > > > > From my point of > > view, the problem is that the javadoc task is not given

Re: [DISCUSS] Creating a 5.0 landing page

Hi Hugh, Thank you for reaching out. I think this is a great idea. Also, great timing, considering the community is discussing a potential 5.0 alpha release soon. It seems to me you actually suggest more than one page? 1) 5.0 and new features - could this be an update of the What’s new page? -

Re: [DISCUSSION] Shall we remove ant javadoc task?

codebase. > >>> I definitely use it extensively inside the IDE. But never as a > compiled set of external docs. > >>> > >>> Which is to say, I'm +1 on removing the target and I'd ask everyone to > keep javadoccing your classes and methods where things are non-obvious

Re: [DISCUSSION] Adding BountyCastle as a test dependency

As it seems there are no objections, we will continue with the addition of this dependency, thank you On Mon, 31 Jul 2023 at 11:41, Ekaterina Dimitrova wrote: > Hi team, > Probably most of you noticed that SSLFactoryTest unit tests fail now with > JDK 17. Java 15 removed sun.secu

Re: [DISCUSSION] Shall we remove ant javadoc task?

gt; Cheers, > > Derek > > On Wed, Aug 2, 2023 at 11:11 AM Brandon Williams wrote: > > I don't think even if it works anyone is going to use the output, so > I'm good with removal. > > Kind Regards, > Brandon > > On Wed, Aug 2, 2023 at 11:50 AM Ekaterina Dimitrova

[DISCUSSION] Shall we remove ant javadoc task?

Hi everyone, We were looking into a user report around our ant javadoc task recently. That made us realize it is not run in CI; it finishes successfully even if there are hundreds of errors, some potentially breaking doc pages. There was a ticket discussion where a few community members mentioned

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

As there were no objections from the community I closed CASSANDRA-18701 On Thu, 27 Jul 2023 at 16:22, Mick Semb Wever wrote: > > > >> 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

[DISCUSSION] Adding BountyCastle as a test dependency

Hi team, Probably most of you noticed that SSLFactoryTest unit tests fail now with JDK 17. Java 15 removed sun.security.x509 package. You can still generate a Self-Signed certificate using BouncyCastle by adding it to the classpath, described in this issue

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

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 und

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

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: August 5.0 Freeze (with waivers…) and a 5.0-alpha1

+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: Status Update on CEP-7 Storage Attached Indexes (SAI)

Thanks Caleb! Great job everyone!  On Wed, 26 Jul 2023 at 15:07, J. D. Jordan wrote: > Thanks for all the work here! > > On Jul 26, 2023, at 1:57 PM, Caleb Rackliffe > wrote: > >  > > Alright, the cep-7-sai branch is now merged to trunk! > > Now we move to addressing the most urgent items

Re: Java distributed upgrade tests fail and issue with CircleCI generate.sh script

Upgrade tests fixed, please rebase your branches on latest trunk On Tue, 25 Jul 2023 at 13:03, Ekaterina Dimitrova wrote: > 1 of 2 is resolved. > The CircleCI script is fixed, you might want to rebase trunk. > > On Tue, 25 Jul 2023 at 12:05, Ekaterina Dimitrova > wrote: >

Re: Java distributed upgrade tests fail and issue with CircleCI generate.sh script

1 of 2 is resolved. The CircleCI script is fixed, you might want to rebase trunk. On Tue, 25 Jul 2023 at 12:05, Ekaterina Dimitrova wrote: > Hi all, > All java distributed upgrade tests fail at the moment. > Testing a potential fix in CASSANDRA-18690. > Apologize for the is

Java distributed upgrade tests fail and issue with CircleCI generate.sh script

Hi all, All java distributed upgrade tests fail at the moment. Testing a potential fix in CASSANDRA-18690. Apologize for the issue. After this issue is fixed you should not be seeing any other failures than the SSLFactoryTest as pointed last night. Also, I added a small fix for generate.sh script

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

trunk - CASSANDRA-18239 As usual - if you have any questions or concerns, please do let me know. Last but not least - thank you to everyone who helped in one way or another with this effort!! On Mon, 24 Jul 2023 at 16:37, Ekaterina Dimitrova wrote: > Ninja fix was required for Jenkins, new buil

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

Ninja fix was required for Jenkins, new build started #1636 On Mon, 24 Jul 2023 at 15:42, Ekaterina Dimitrova wrote: > Done! > > All commits from 18255 are in. > The first run to monitor will be in Jenkins #1635 > > There will be still fixes to be applied for some uni

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

-16895, there is a table in its description) I will keep you posted on any new developments. On Mon, 24 Jul 2023 at 14:52, Ekaterina Dimitrova wrote: > Starting commits for 18255. Please put on hold any trunk commits. I will > let you know when it is done. Thank you > > On Mon,

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

Starting commits for 18255. Please put on hold any trunk commits. I will let you know when it is done. Thank you On Mon, 24 Jul 2023 at 11:29, Ekaterina Dimitrova wrote: > Hi everyone, > > Happy Monday! > > I am working on dropping JDK 8 and adding JDK17 on trunk in both CI

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

Hi everyone, Happy Monday! 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

Re: [Discuss] CQLSH confusion

“ keep the C* version somewhere in cqlsh and warn when it doesn't match the server.” +1 on this suggestion. I had horrible experience recently with things changing their versioning in another project. It brings mostly confusion. Warning and adding C* version makes it simple and obvious. No need

Re: Changing the output of tooling between majors

On German’s point, to be honest in pre-4.1 any new changes we tried to add with a flag after concerns for breaking changes were raised. So in that sense I think it will be confusing to flip that to - new output by default and moving to legacy the old one On Thu, 13 Jul 2023 at 12:09, German

Re: Fwd: [DISCUSS] Formalizing requirements for pre-commit patches on new CI

> > > > śr., 12 lip 2023 o 14:51 Ekaterina Dimitrova > napisał(a): > >> jenkins_jira_integration >> <https://github.com/apache/cassandra-builds/blob/trunk/jenkins-jira-integration/jenkins_jira_integration.py> >> script >> updating the JIRA ticket with

Re: Fwd: [DISCUSS] Formalizing requirements for pre-commit patches on new CI

jenkins_jira_integration script updating the JIRA ticket with test results if you cause a regression + us building a muscle around reverting your commit if they break tests.“ I am not sure

Re: Fwd: [DISCUSS] Formalizing requirements for pre-commit patches on new CI

“ On our 4.0 release I remember a number of such failures but not recently. ” Based on all the 5.0 work I’d say we need as a minimum to build and start a node with all JDK versions pre-commit. On Wed, 12 Jul 2023 at 7:29, Jacek Lewandowski wrote: > Isn't novnodes a special case of vnodes with

Re: Proposed update to cassandra-stress to use Apache Commons CLI

Hey Brad, Thanks for raising the topic. I wanted to mention we are now on a very old version of commons-cli (1.1 from 2007). So I would suggest we first update it. While there is activity in the commons-cli github repo (a lot of dependency updates as far as I can tell from a quick look), the last

Re: Removal of CloudstackSnitch

Hi Stefan, I think we should follow our deprecation rules and deprecate it in 5.0, potentially remove in 6.0. (Deprecate in one major, remove in the next major) Maybe the deprecation can come with a note on your findings for the users, just in case someone somewhere uses it and did not follow the

Re: [DISCUSS] Allow UPDATE on settings virtual table to change running configuration

Hi, First of all, thank you for all the work! I personally think that it should be ok to add a new column. I will be very happy to see this landing in 5.0. I am personally against porting this patch to 4.1. To be clear, I am sure you did a great job and my response would be the same to every

Fwd: [DISCUSS] Formalizing requirements for pre-commit patches on new CI

“I'm curious what it triggers for you Brandon, Berenguer, Andres, Ekaterina, and Mick (when you're back from the mountains ;)). ” We already have pre-commit a minimum set being mandatory in CircleCI. People can manually trigger other tests if they feel they might have broken something. The only

Re: JDK 17 Support Proposal for ant generate-idea-files in CASSANDRA-18467

Dear all, Thanks to everyone who shared feedback and tested the changes. The patch was committed. ‘ant generate-idea-files’ now support JDK8, JDK11, and JDK17 To add support for another JDK the java-jvmargs property must be set for the JDK in question (see how it’s done in build.xml for Java 11

Re: [DISCUSS] Formalizing requirements for pre-commit patches on new CI

Thank you, Josh and Mick Immediate questions on my mind: - Currently we run at most two parallel CI runs in Jenkins-dev, I guess you will try to improve that limitation? - There are hw constraints, is there any approximation on how long it will take to run all tests? Or is there a stated goal

Re: [DISCUSS] When to run CheckStyle and other verificiations

etter to have these be completely invisible to people with their workflows >> and Just Work (except for when your IDE scolds you for bad behavior w/build >> errors immediately). >> >> I still think Flags Are Bad. :) >> >> On Thu, Jun 29, 2023, at 1:38 PM, Eka

Re: [DISCUSS] When to run CheckStyle and other verificiations

Should we just keep a consolidated for all kind of checks no-check flag and get rid of the no-checkstyle one? Trading one for one with Josh :-) Best regards, Ekaterina On Thu, 29 Jun 2023 at 10:52, Josh McKenzie wrote: > I really prefer separate tasks than flags. Flags are not listed in the >

Re: [DISCUSS] When to run CheckStyle and other verificiations

Thank you, Jacek, for starting the thread; those things are essential for developer productivity. I support the idea of opting out vs opting into checks. In my experience, it also makes things easier and faster during review time. If people have to opt-in - it is one more thing for new people to

Re: [DISCUSS] Being specific about JDK versions and python lib versions in CI

ecially for > things like Java or Python version, I would hope we just install the latest > Java 8, Java 11, or Java 17 JDK for the platform the image is built from > and run under them. Otherwise we don’t find out until it’s too late when > some JDK update breaks things. I know I always t

Re: [DISCUSS] Being specific about JDK versions and python lib versions in CI

Wouldn’t we recommend people to use the test images the project CI use? Thus using in testing the versions we use? I would assume the repeatable CI will still expect test images the way we have now? (I hope I did not misunderstand the question) I also share similar worries with Brandon On Thu,

Re: [DISCUSSIONS] Replace ant eclipse-warnings with CheckerFramework

Thank you all! It seems there is a consensus here so I updated accordingly CASSANDRA-18239 On Fri, 16 Jun 2023 at 8:56, Jeremiah Jordan wrote: > +1 from me. > > On Jun 15, 2023 at 1:01:01 PM, Ekaterina Dimitrova > wrote: > >> Hi everyone, >> Happy Thursday! >

Re: [DISCUSS] Remove deprecated keyspace_count_warn_threshold and table_count_warn_threshold

Hi all, I was following the discussion. What Andres just summarized sounds reasonable to me. Let’s just not forget to document also all this. Thank you Ekaterina On Fri, 16 Jun 2023 at 10:16, Andrés de la Peña wrote: > It seems we agree on removing the default value for the old thresholds, >

Re: [DISCUSSIONS] Replace ant eclipse-warnings with CheckerFramework

Got so excited that I forgot to say which of the two options exactly I meant - running the analysis only on changed files after the initial full pass is done sounds like a good improvement to me On Fri, 16 Jun 2023 at 7:43, Ekaterina Dimitrova wrote: > I think this is a great i

Re: [DISCUSSIONS] Replace ant eclipse-warnings with CheckerFramework

ssue I missed, if I’m remembering correctly. All other >> instances have just been annoyances, forcing to add a redundant suppressed >> annotation. >> >> On 15 Jun 2023, at 19:01, Ekaterina Dimitrova >> wrote: >> >> Hi everyone, >> Happy Thursday! >

[DISCUSSIONS] Replace ant eclipse-warnings with CheckerFramework

Hi everyone, Happy Thursday! Some time ago, Jacek raised the point that ant eclipse-warnings is generating too many false positives and not really working as expected. (CASSANDRA-18239) Reminder: ant eclipse-warnings is a task we run with the goal to check Cassandra code - static analysis to warn

Re: [DISCUSS] Moving system property names to the CassandraRelevantProperties

Thank you Maxim! I also agree with 1 and 2. Also, thank you for considering documentation. The datastax docs page mentioned here is not maintained by the project, the other one can get some love. I guess if we are adding description column, we can automate the way we populate that page. But I

Re: [VOTE] CEP-8 Datastax Drivers Donation

+1 On Tue, 13 Jun 2023 at 10:33, Jeff Jirsa wrote: > +1 > > > On Tue, Jun 13, 2023 at 7:15 AM Jeremy Hanna > wrote: > >> Calling for a vote on CEP-8 [1]. >> >> To clarify the intent, as Benjamin said in the discussion thread [2], the >> goal of this vote is simply to ensure that the community

Re: [VOTE] CEP-30 ANN Vector Search

+1 On Thu, 25 May 2023 at 16:46, Brandon Williams wrote: > +1 > > Kind Regards, > Brandon > > On Thu, May 25, 2023 at 10:45 AM Jonathan Ellis wrote: > > > > Let's make this official. > > > > CEP: >

Re: [DISCUSS] Feature branch version hygiene

I do not think we discussed it from feature branch perspective. (Happy to stand corrected but I did not find anything in @dev archive myself) But we do mark with 5.0 anything that lands in trunk. I think it might be a good idea anything that lands in a feature branch to have different fix version

Re: [VOTE] CEP-29 CQL NOT Operator

+1 On Wed, 10 May 2023 at 0:40, Dinesh Joshi wrote: > +1 > > > On May 8, 2023, at 1:52 AM, Piotr Kołaczkowski > wrote: > > > > Let's vote. > > > > > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-29%3A+CQL+NOT+operator > > > > Piotr Kołaczkowski > > e. pkola...@datastax.com > > w.

Re: [DISCUSS] Introduce DATABASE as an alternative to KEYSPACE

“ KEYSPACE is fine. If we want to introduce a standard nomenclature like DATABASE that’s also fine. Inventing brand new ones is not fine, there’s no benefit. I think it would be fine to introduce some arbitrary unrelated concept for assigning tables with similar behaviours some configuration that

Re: Google Season of Docs

Thank you for your efforts Lorina! On Tue, 4 Apr 2023 at 16:26, Deepak Vohra via dev wrote: > I noticed that fewer projects were selected this year and no Apache > project was selected. > > On Monday, April 3, 2023 at 06:07:53 p.m. EDT, Nate McCall < > zznat...@gmail.com> wrote: > > > Thank

Re: [VOTE] CEP-26: Unified Compaction Strategy

+1 On Tue, 4 Apr 2023 at 11:44, Benjamin Lerer wrote: > +1 > > Le mar. 4 avr. 2023 à 17:17, Andrés de la Peña a > écrit : > >> +1 >> >> On Tue, 4 Apr 2023 at 15:09, Jeremy Hanna >> wrote: >> >>> +1 nb, will be great to have this in the codebase - it will make nearly >>> every table's

Re: Welcome our next PMC Chair Josh McKenzie

Congrats Josh! Thanks Mick! На четвъртък, 23 март 2023 г. Brandon Williams написа: > Congrats Josh! Thanks Mick! > > Kind Regards, > Brandon > > On Thu, Mar 23, 2023 at 3:22 AM Mick Semb Wever wrote: > > > > It is time to pass the baton on, and on behalf of the Apache Cassandra > Project

CASSANDRA-18343

Hi everyone, Heads up, I will be adding new -add-exports to jvm17-clients.options in CASSANDRA-18343. It is needed in order to be able to run bin/nodetool sjk hh with JDK 17. More details on the ticket if someone is interested Best regards, Ekaterina

  1   2   3   4   >