Re: [VOTE] CEP-37: Repair scheduling inside C*

As per the CEP process documentation, this vote will be open for 72 hours > (longer if needed). > +1

Re: Backporting CASSANDRA-17812 to 4.x

Can you please put the ticket description in the email. Saves us having to follow the link to know what you're talking about. Yes to backporting this. On Tue, 5 Nov 2024 at 10:27, Štefan Miklošovič wrote: > Hello, > > I want to ask if there are objections for backporting CASSANDRA-17812 (1) >

Re: [Discuss] Repair inside C*

Thanks Jaydeep. I've exhausted my lines on enquiry and am happy that thought has gone into them. > On top of the above list, here is my recommendation (this is just a pure > thought only and subject to change depending on how all the community > members see it): > >- Nov-Dec: We can definit

Re: [Discuss] Repair inside C*

Jaydeep, your replies address my main concerns, there's a few questions of curiosity as replies inline below… > >Without any per-table scheduling and history (IIUC) a node would have > to restart the repairs for all keyspaces and tables. > > The above-mentioned quote should work fine and wi

Re: [Discuss] Repair inside C*

any name works for me, Jaydeep :-) I've taken a run through of the CEP, design doc, and current PR. Below are my four (rough categories of) questions. I am keen to see a MVP land, so I'm more looking at what the CEP's design might not be able to do, rather than what may or may not land in an init

Re: [DISCUSS] Donating easy-cass-stress to the project

On Wed, 23 Oct 2024 at 05:48, Jordan West wrote: > Josh/Mick, where does that leave us? I’d like to start with the smaller > scope Josh described in his last email. We can tackle in-tree/stress > separately. > > I was going to start working on getting signed ICLAs. Does that still > sound like th

[RELEASE] Apache Cassandra 5.0.2 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 5.0.2. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source an

Re: [DISCUSS] Modeling JIRA fix version for subprojects

> > Isn't it weird that you said that we should not save characters at the > cost of readability while we just use CASS everywhere except the main > project? Why do you think that having "CASS-" will make people > automatically think that this is Cassandra related. No other project in > Apache (afa

[RESULT][VOTE] Release Apache Cassandra 5.0.2

Vote passes with six +1s (four binding) and no vetoes. ref: https://lists.apache.org/thread/wb8k7t0vfpj5hs4k7h2gydbkl8qmlsqz On Wed, 16 Oct 2024 at 14:18, Mick Semb Wever wrote: > Proposing the test build of Cassandra 5.0.2 for release. > > sha1: f278f6774fc76465c182041e081982105c3e7

Re: [Discuss] Repair inside C*

This is looking strong, thanks Jaydeep. I would suggest folk take a look at the design doc and the PR in the CEP. A lot is there (that I have completely missed). I would especially ask all authors of prior art (Reaper, DSE nodesync, ecchronos) to take a final review of the proposal Jaydeep, can

Re: [DISCUSS] Modeling JIRA fix version for subprojects

;> >>> Kind Regards, >>>>> > >> >>> Brandon >>>>> > >> >>> >>>>> > >> >>> On Wed, Oct 2, 2024 at 5:07 PM Brandon Williams < >>>>> dri...@gmail.com> >>&g

Re: [VOTE] Release Apache Cassandra 5.0.2

reply below. > The vote will be open for 72 hours (longer if needed). Everyone who has > tested the build is invited to vote. Votes by PMC members are considered > binding. A vote passes if there are at least three binding +1s and no -1's. > +1 Checked - signing correct - checksums correct - s

[VOTE] Release Apache Cassandra 5.0.2

Proposing the test build of Cassandra 5.0.2 for release. sha1: f278f6774fc76465c182041e081982105c3e7dbb Git: https://github.com/apache/cassandra/tree/5.0.2-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1349/org/apache/cassandra/cassandra-all/5.0.2

Re: [DISCUSS] Donating easy-cass-stress to the project

arg parsing alone is a > 5K line mess. It's certainly not being well-maintained and could use a > replacement. > > On Sun, Oct 13, 2024 at 10:25 PM Josh McKenzie > wrote: > > > Unsolicited .02: > > - If this will eventually replace the in-tree cassandra-stress, does i

[ANNOUNCE] Apache Cassandra 5.0.2 test artifact available

The test build of Cassandra 5.0.2 is available. sha1: f278f6774fc76465c182041e081982105c3e7dbb Git: https://github.com/apache/cassandra/tree/5.0.2-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1349/org/apache/cassandra/cassandra-all/5.0.2/ The So

Re: [DISCUSS] 5.0 Upgrades and CASSANDRA-19989

I'll start a 5.0.2 release then… unless there's anything else in-flight I should be waiting for …? On Fri, 11 Oct 2024 at 23:06, Caleb Rackliffe wrote: > Just to close the loop, this is committed to 5.0 and trunk. > > On Wed, Oct 9, 2024 at 3:07 PM Caleb Rackliffe > wrote: > >> Hey folks, >>

Re: [DISCUSS] Donating easy-cass-stress to the project

reply below. > I’m terms of next steps: Mick what do we need to do next? Figure out the > answers to your questions re: getting contributor sign off? > The process of donation is as follows… (feel free to correct me, or add anything) 1. General pre-agreement from the PMC that we'll take this

Re: [DISCUSS] Modeling JIRA fix version for subprojects

To play devil's advocate here, it's important that the subprojects don't lose visibility and silo from the rest of the project. There are different ways to solve this, and lumping everything into one jira project is a messy and poor way of doing it. But as the sidecar has shown us, subproject act

[RELEASE] Apache Cassandra 5.0.1 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 5.0.1. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source an

Re: [DISCUSS] CEP-44: Kafka integration for Cassandra CDC using Sidecar

Agree with Jon, Josh and Patrick here. This is the type of hidden subproject that will get us into trouble with the board/foundation. I'm sure it's getting enough committer eyeballs, and some PMC oversight, but maybe not enough. Addressing the more material points that Jon mentions is the best

[RESULT][VOTE] Release Apache Cassandra 5.0.1

. Proposing the test build of Cassandra 5.0.1 for release. > > sha1: c206e4509003ac4cd99147d821bd4b5d23bdf5e8 > Git: https://github.com/apache/cassandra/tree/5.0.1-tentative > Maven Artifacts: > https://repository.apache.org/content/repositories/orgapachecassandra-1348/org/apache/cassandra/cassand

[RELEASE] Apache Cassandra 4.1.7 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 4.1.7. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source an

[RELEASE] Apache Cassandra 4.0.14 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 4.0.14. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source a

[RESULT][VOTE] Release Apache Cassandra 4.1.7

Vote passes with five +1s, four binding. ref: https://lists.apache.org/thread/clq6959ntgltbpzx21xl1jkphcowwgg7 On Fri, 20 Sept 2024 at 16:35, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 4.1.7 for release. > > sha1: ca494526025a480bc8530ed3ae472ce8c9cbaf7a

[RESULT][VOTE] Release Apache Cassandra 4.0.14

Vote passes with three binding +1s ref: https://lists.apache.org/thread/lps6bskc1lr8f5bfhglystcmjdnqzn24 On Fri, 20 Sept 2024 at 16:35, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 4.0.14 for release. > > sha1: 7bf67349579411521bcdee4febd209cff63179a6

Re: [VOTE] Release Apache Cassandra 5.0.1

. > > The vote will be open for 96 hours (longer if needed). Everyone who has > tested the build is invited to vote. Votes by PMC members are considered > binding. A vote passes if there are at least three binding +1s and no -1's. > +1 Checked - signing correct - checksums correct - source ar

Re: [VOTE] Release Apache Cassandra 4.1.7

. > > The vote will be open for 96 hours (longer if needed). Everyone who has > tested the build is invited to vote. Votes by PMC members are considered > binding. A vote passes if there are at least three binding +1s and no -1's. > +1 Checked - signing correct - checksums are correct - sour

Re: [VOTE] Release Apache Cassandra 4.0.14

. > > The vote will be open for 96 hours (longer if needed). Everyone who has > tested the build is invited to vote. Votes by PMC members are considered > binding. A vote passes if there are at least three binding +1s and no -1's. > +1 Checked - signing correct - checksums are correct - source

[VOTE] Release Apache Cassandra 5.0.1

Proposing the test build of Cassandra 5.0.1 for release. sha1: c206e4509003ac4cd99147d821bd4b5d23bdf5e8 Git: https://github.com/apache/cassandra/tree/5.0.1-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1348/org/apache/cassandra/cassandra-all/5.0.1

[VOTE] Release Apache Cassandra 4.1.7

Proposing the test build of Cassandra 4.1.7 for release. sha1: ca494526025a480bc8530ed3ae472ce8c9cbaf7a Git: https://github.com/apache/cassandra/tree/4.1.7-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1347/org/apache/cassandra/cassandra-all/4.1.7

[VOTE] Release Apache Cassandra 4.0.14

Proposing the test build of Cassandra 4.0.14 for release. sha1: 7bf67349579411521bcdee4febd209cff63179a6 Git: https://github.com/apache/cassandra/tree/4.0.14-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1345/org/apache/cassandra/cassandra-all/4.0

[ANNOUNCE] Apache Cassandra 4.0.14, 4.1.7, 5.0.1 test artefacts available

The test builds of Cassandra 4.0.14, 4.1.7 and 5.0.1, are available. A vote of this test build will be initiated within the next couple of days. == 4.0.14 == sha1: 7bf67349579411521bcdee4febd209cff63179a6 Git: https://github.com/apache/cassandra/tree/4.0.14-tentative Maven Artifacts: https://repo

Re: [DISCUSS] CASSANDRA-13704 Safer handling of out of range tokens

reply below. > Mick - this patch doesn't fix things 100%. It can't. BUT - it does take us > from "In all cases where this occurs you will silently lose data" to "in > some cases where this occurs you will have a rejected write, in others > you'll have coordinator level logging, and in the worst

Re: [DISCUSS] CASSANDRA-13704 Safer handling of out of range tokens

replies below (to Scott, Josh and Jeremiah). tl;dr all my four points remain undisputed, when the patch is applied. This is a messy situation, but no denying the value of rejection writes to various known popular scenarios. Point (1) remains important to highlight IMHO. On Fri, 13 Sept 2024 at

Re: [DISCUSS] CASSANDRA-13704 Safer handling of out of range tokens

es then the nodes may as well be down. > Unless the end user is writing at CL ANY they have requested to be ACKed > when CL nodes which own the data have acked getting it. > > -Jeremiah > > On Sep 12, 2024 at 2:35:01 PM, Mick Semb Wever wrote: > >> Great that the discus

Re: [DISCUSS] CASSANDRA-13704 Safer handling of out of range tokens

reply below On Thu, 12 Sept 2024 at 21:56, Josh McKenzie wrote: > I'd like to propose we treat all data loss bugs as "fix by default on all > supported branches even if that might introduce user-facing changes". > > Even if only N of M people on a thread have experienced it. > Even if we only un

Re: [DISCUSS] CASSANDRA-13704 Safer handling of out of range tokens

Yes, and my usage of CL.*ONE wasn't so correct (as writes are backgrounded), but… The point is we should be accurate and precise in talking about this (folk will come back and read this thread), both in how it can manifest, the limitations of both logging and rejection, what possible remedies are,

Re: [DISCUSS] CASSANDRA-13704 Safer handling of out of range tokens

will be lost than silently lose it. > > Of course, a change like this requires very good communication in NEWS.txt > and elsewhere but I think its well worth it. While it may surprise some > users I think they would be more surprised that they were silently losing > data. > > Jord

Re: [DISCUSS] CASSANDRA-13704 Safer handling of out of range tokens

Thanks for starting the thread Caleb, it is a big and impacting patch. Appreciate the criticality, in a new major release rejection by default is obvious. Otherwise the logging and metrics is an important addition to help users validate the existence and degree of any problem. Also worth mentio

Welcome Chris Bannister, James Hartig, Jackson Flemming and João Reis, as cassandra-gocql-driver committers

The PMC's members are pleased to announce that Chris Bannister, James Hartig, Jackson Flemming and João Reis have accepted invitations to become committers on the Drivers subproject. Thanks a lot for everything you have done with the gocql driver all these years. We are very excited to see the dr

Re: [VOTE] Release test-api 0.0.17

> > The vote will be open for 24 hours. Everyone who has tested the build > is invited to vote. Votes by PMC members are considered binding. A > vote passes if there are at least three binding +1s. > +1

[RELEASE] Apache Cassandra 5.0.0 GA released

The Cassandra team is pleased to announce the GA release of Apache Cassandra version 5.0.0. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source

[RESULT][VOTE] Release Apache Cassandra 5.0.0

Vote passes with three binding +1 votes. ref: https://lists.apache.org/thread/b568cx8l1y2tx93rrc9fnhsohg3jqzk6 On Mon, 2 Sept 2024 at 12:11, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 5.0.0 for release. > > sha1: 186272edca920c757b91bf95c2392bafa1a38d72

Re: [VOTE] Release Apache Cassandra 5.0.0

. The vote will be open for 72 hours (longer if needed). Everyone who has > tested the build is invited to vote. Votes by PMC members are considered > binding. A vote passes if there are at least three binding +1s and no -1's. > +1 Checked - signing correct - checksums correct - source artefa

[VOTE] Release Apache Cassandra 5.0.0

Proposing the test build of Cassandra 5.0.0 for release. sha1: 186272edca920c757b91bf95c2392bafa1a38d72 Git: https://github.com/apache/cassandra/tree/5.0.0-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1342/org/apache/cassandra/cassandra-all/5.0.0

[ANNOUNCE] Apache Cassandra 5.0.0 GA test artifact available

The test build of Cassandra 5.0.0 GA is available. sha1: 186272edca920c757b91bf95c2392bafa1a38d72 Git: https://github.com/apache/cassandra/tree/5.0.0-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1342/org/apache/cassandra/cassandra-all/5.0.0/ The

[RELEASE] Apache Cassandra 5.0-rc2 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 5.0-rc2. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source

[RESULT][VOTE] Release Apache Cassandra 5.0-rc2

. > Proposing the test build of Cassandra 5.0-rc2 for release. > … > The vote will be open for 72 hours (longer if needed). Everyone who has > tested the build is invited to vote. Votes by PMC members are considered > binding. A vote passes if there are at least three binding +1s and no -1's. >

Re: [VOTE] Release Apache Cassandra 5.0-rc2

. The vote will be open for 72 hours (longer if needed). Everyone who has > tested the build is invited to vote. Votes by PMC members are considered > binding. A vote passes if there are at least three binding +1s and no -1's. > +1 Checked - signing correct - checksums correct - source artef

[VOTE] Release Apache Cassandra 5.0-rc2

Proposing the test build of Cassandra 5.0-rc2 for release. sha1: 06691fce25a215361332aa1767e188bb6694687a Git: https://github.com/apache/cassandra/tree/5.0-rc2-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1341/org/apache/cassandra/cassandra-all/5

[ANNOUNCE] Apache Cassandra 5.0-rc2 test artifact available

The test build of Cassandra 5.0-rc2 is available. sha1: 06691fce25a215361332aa1767e188bb6694687a Git: https://github.com/apache/cassandra/tree/5.0-rc2-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1341/org/apache/cassandra/cassandra-all/5.0-rc2/

Re: [VOTE] Release Apache Cassandra 4.1.6 - take 2

. > The vote will be open for 72 hours (longer if needed). Everyone who > has tested the build is invited to vote. Votes by PMC members are > considered binding. A vote passes if there are at least three binding > +1s and no -1's. > +1 Checked - signing correct - checksums are correct - so

Re: [DISCUSS] state of lz4-java

reply below. - since the project is Apache licensed we could fork / adopt for our needs? > I’m not familiar enough with the hurdles we’d have to surmount around the > licensing but at least it’s a compatible license. Maybe Mick knows more > about what would be required for this route? > It's "C

Re: [DISCUSS] Backport CASSANDRA-19800 to Cassandra-4.0, 4.1 and 5.0

reply below. We're moving into a world where we will likely more frequently modify the > mainline branch with new functionality to integrate with ecosystem changes > (sidecar, analytics, drivers?). It's probably at least worth a conversation > as to whether our current policy (improvements and ne

Re: [DISCUSS] The way we log

On Tue, 23 Jul 2024 at 15:27, J. D. Jordan wrote: > I don’t know that I agree we should remove use if isDebugEnabled, but we > should be assuming debug is enabled and not doing anything too crazy there. > The problem is that the use of isDebugEnabled, as trivial as it is, leads to the typical a

Re: [DISCUSS] The way we log

> I disagree with all of this. Debug logging *can* be enabled for > production clusters, but it should not be on by default. > > DEBUG should *not* be taken to mean “background activities” and we should > stamp this out wherever this has been occurring. DEBUG means verbose > logging for use debuggi

Re: [DISCUSS] The way we log

reply below… On Thu, 30 May 2024 at 14:34, Štefan Miklošovič wrote: > I see the feedback is overall positive. I will merge that and I will > improve the documentation on the website along with what Benedict suggested. > I think the codestyle needs to be more explicit that this applies _only_

[RELEASE] Apache Cassandra 5.0-rc1 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 5.0-rc1. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source

[RESULT][VOTE] Release Apache Cassandra 5.0-rc1 (take3)

> The vote will be open for 72 hours (longer if needed). Everyone who has > tested the build is invited to vote. Votes by PMC members are considered > binding. A vote passes if there are at least three binding +1s and no -1's. > The vote passes with three binding +1s

Re: [VOTE] Release Apache Cassandra 5.0-rc1 (take3)

The vote will be open for 72 hours (longer if needed). Everyone who has > tested the build is invited to vote. Votes by PMC members are considered > binding. A vote passes if there are at least three binding +1s and no -1's. > +1 Checked - signing correct - checksums correct - source artefact

Re: [VOTE] Release Apache Cassandra 5.0-rc1 (take3)

On Wed, 17 Jul 2024 at 21:40, Brandon Williams wrote: > On Wed, Jul 17, 2024 at 2:36 PM Mick Semb Wever wrote: > > > > Should we remove the noboolean rpm from the release, given we have no > way to verify or test it ? > > Effectively, dropping centos:7 support from 5.0

Re: [VOTE] Release Apache Cassandra 5.0-rc1 (take3)

On Mon, 15 Jul 2024 at 13:10, Brandon Williams wrote: > +1 > > Note that centos7 went EOL on June 30th; I didn't test the noboolean > packages as a result. > Should we remove the noboolean rpm from the release, given we have no way to verify or test it ? Effectively, dropping centos:7 support

[VOTE] Release Apache Cassandra 5.0-rc1 (take3)

Proposing the third test build of Cassandra 5.0-rc1 for release. sha1: d85d6750f90eaf799709a05d2f1c31189fce04fd Git: https://github.com/apache/cassandra/tree/5.0-rc1-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1338/org/apache/cassandra/cassandra

[RESULT][VOTE] Release Apache Cassandra 5.0-rc1 (take2)

. The vote will be open for 72 hours (longer if needed). Everyone who has > tested the build is invited to vote. Votes by PMC members are considered > binding. A vote passes if there are at least three binding +1s and no -1's. > > With a veto in place the vote fails.

[VOTE] Release Apache Cassandra 5.0-rc1 (take2)

Proposing the test build of Cassandra 5.0-rc1 for release. sha1: 01eea8a0d74deaede236edb25335fa470502106e Git: https://github.com/apache/cassandra/tree/5.0-rc1-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1337/org/apache/cassandra/cassandra-all/5

Re: [RESULT][VOTE][IP CLEARANCE] GoCQL driver

> The vote will be open for 72 hours (or longer). Votes by PMC members are >> considered binding. A vote passes if there are at least three binding >> +1s and no -1's. >> > > Vote passes with 12 +1s (9 from PMC). > vote thread was https://lists.apache.org/thread/j1tz0t90q72l3hp8frv9xzr0ozqstgg9

[RESULT][VOTE][IP CLEARANCE] GoCQL driver

. > The vote will be open for 72 hours (or longer). Votes by PMC members are > considered binding. A vote passes if there are at least three binding +1s > and no -1's. > Vote passes with 12 +1s (9 from PMC).

[RESULT}[VOTE] Release Apache Cassandra 5.0-rc1

The votes fails with a veto in place having made CASSANDRA-19668 an 5.0-rc blocker. Once 19668 lands we will need an immediate release of 4.1.6 too. On Fri, 28 Jun 2024 at 06:49, Jon Haddad wrote: > Thanks for confirming this, Blake. I agree that we should not knowingly > ship new versions wi

Re: [VOTE][IP CLEARANCE] GoCQL driver

. > The vote will be open for 72 hours (or longer). Votes by PMC members are > considered binding. A vote passes if there are at least three binding +1s > and no -1's. > +1

[VOTE][IP CLEARANCE] GoCQL driver

Please vote on the acceptance of the GoCQL driver and its IP Clearance: https://incubator.apache.org/ip-clearance/cassandra-gocql-driver.html All consent from original authors of the donation, and tracking of collected CLAs, is found in: - https://github.com/gocql/gocql/issues/1751 - https://cwi

Re: [VOTE] Release Apache Cassandra 5.0-rc1

. Proposing the test build of Cassandra 5.0-rc1 for release. > > sha1: b43f0b2e9f4cb5105764ef9cf4ece404a740539a > Git: https://github.com/apache/cassandra/tree/5.0-rc1-tentative > Maven Artifacts: > https://repository.apache.org/content/repositories/orgapachecassandra-1336/org/apache/cassandra/cas

[VOTE] Release Apache Cassandra 5.0-rc1

Proposing the test build of Cassandra 5.0-rc1 for release. sha1: b43f0b2e9f4cb5105764ef9cf4ece404a740539a Git: https://github.com/apache/cassandra/tree/5.0-rc1-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1336/org/apache/cassandra/cassandra-all/5

[DISCUSS] spark-cassandra-connector donation to Analytics subproject

What are folks thoughts on accepting a donation of the spark-cassandra-connector project into the Analytics subproject ? A number of folks have requested this, stating that they cannot contribute to the project while it is under DataStax. The project has largely been in maintenance mode the past

[ANNOUNCE] Apache Cassandra 5.0-rc1 test artifact available

The test build of Cassandra 5.0-rc1 is available. sha1: b43f0b2e9f4cb5105764ef9cf4ece404a740539a Git: https://github.com/apache/cassandra/tree/5.0-rc1-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1336/org/apache/cassandra/cassandra-all/5.0-rc1/

Re: Suggestions for CASSANDRA-18078

re that’s immediately deprecated >>> reflects poorly on the project and our ability to manage it. >>> > >>> > I don’t know how much work need to be done to merge that patch, so its >>> hard to say if we should wait for it or if we should ship 5.0 and make an >&

Re: Suggestions for CASSANDRA-18078

> > To remove MAXWRITETIME (CASSANDRA-18078) we must now (as Yifan notes) > first add CASSANDRA-18085. > This statement is inaccurate. Before 5.0-alpha1 there was no equivalent function for either MAXWRITETIME or 18085.

Re: Suggestions for CASSANDRA-18078

On Fri, 21 Jun 2024 at 09:43, Sam Tunnicliffe wrote: > 100% Option 1. Once it's out in GA release we're stuck with it so any > short term disruption to adopters of pre-release versions is a trivial > price to pay. Sam, Jeremiah, Jeff, Jon, we need some clarity on this. To remove MAXWRITETIM

Re: Cassandra PMC Chair Rotation, 2024 Edition

Thank you Josh for being an amazing VP. The past year has been very transformative for the project and you've done a ton of critical work behind the scenes that few know about. Welcome Dinesh! On Thu, 20 Jun 2024 at 17:53, Josh McKenzie wrote: > Another PMC Chair baton pass incoming! On beha

Re: Suggestions for CASSANDRA-18078

On Thu, 20 Jun 2024 at 18:46, Štefan Miklošovič wrote: > List, > > we need your opinions about CASSANDRA-18078. > > That ticket is about the removal of MAXWRITETIME function which was added > in CASSANDRA-17425 and firstly introduced in 5.0-alpha1. > > This function was identified to be redundant

Re: [DISCUSS] Stream Pipelines on hot paths

> > I think this is a good general principle for *raising standards* in the > codebase like this: if somebody says something is important, and cannot be > convinced otherwise, then it should generally be treated as important. This > is different from cases where there are simply competing approache

Re: CCM and CASSANDRA_USE_JDK11

I'd like us to invest in unit tests and make them the contract guards. > Thank you Jacek. In the end, I feel we strayed off the topic a bit - my question was quite > concrete - I'd like to remove the CASSANDRA_USE_JDK11 knob for CCM - it > should set it appropriately for Cassandra 4 so that the

Re: [DISCUSS] The way we log

> Based on these findings, I went through the code and I have incorporated > these rules and I rewrote it like this: > > 1) no wrapping in "if" if we are not logging more than 2 parameters. > 2) rewritten log messages to not contain any string concatenation but > moving it all to placeholders ({}).

Re: Updating Instaclustr donated Jenkins Agents

> This is exactly the feedback I was looking for, the last thing we want to > do is reduce the throughput of the already strained CI pipelines. > > Sounds like it's a bigger task than just cutting over to ARM, just want to > reassure you Brandon we certainly won't change anything without discussion

Re: Updating Instaclustr donated Jenkins Agents

Jackson, we are very thankful for all the donations from Instaclustr. Getting people (and resources) involved in ARM maintenance and testing is desperately needed. More detailed feedback below. On Fri, 24 May 2024 at 16:08, Brandon Williams wrote: > On Thu, May 23, 2024 at 5:51 PM Fleming,

Re: [VOTE] Release Apache Cassandra Java Driver 4.18.1 (2nd attempt)

With all of that said let's get to it. I’m proposing the test build of > Cassandra Java Driver 4.18.1 for release. > > sha1: cbdde2878786fa6c4077a21352cbe738875f2106 > > Git: > https://github.com/apache/cassandra-java-driver/tree/4.

Re: CCM and CASSANDRA_USE_JDK11

> > When starting Cassandra nodes, CCM uses the current env Java distribution > (defined by the JAVA_HOME env variable). This behavior is overridden in > three cases: > > - Java version is not supported by the selected Cassandra distribution - > in which case, CCM looks for supported Java distribut

Re: [VOTE] Release Apache Cassandra 4.1.5

> > > The vote will be open for 72 hours (longer if needed). Everyone who >> > has tested the build is invited to vote. Votes by PMC members are >> > considered binding. A vote passes if there are at least three binding >> > +1s and no -1's. > > +1 Checked - signing correct - checksums are corre

Re: [VOTE] Release Apache Cassandra 4.0.13

> > > The vote will be open for 72 hours (longer if needed). Everyone who > > has tested the build is invited to vote. Votes by PMC members are > > considered binding. A vote passes if there are at least three binding > > +1s and no -1's. > +1 Checked - signing correct - checksums are correct -

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

Re: Is there appetite to maintain the gocql driver (in the drivers subproject) ?

> > Ok, so we're got confidence now on how to approach this, confirmation from >> the project's maintainers supporting it, and interest from a handful of >> people interested in maintaining and contributing to the project. >> > > Did you talk to the current maintainers off list or did I miss some t

Re: Is there appetite to maintain the gocql driver (in the drivers subproject) ?

ven if it is not DataStax donating this particular codebase, the process is largely the same and it is the Drivers subproject receiving it. On Mon, 15 Apr 2024 at 12:31, Mick Semb Wever wrote: > > > > We can open an issue with LEGAL to see what they say at least? >>>

Re: Missing link to KEYS files on download page

done. asc changed again, but it can also be verified against the staged artifact we voted on. On Thu, 9 May 2024 at 07:45, Justin Mclean wrote: > Hi, > > I would update the asc file (and KEYS file if needed) so that if any user > tries to verify the release, it can be verified. > > Kind Regards

Re: Missing link to KEYS files on download page

On Wed, 8 May 2024 at 02:33, Justin Mclean wrote: > Hi, > > The Cassandra download page [1] includes signature files, but you also > need to include a link to the KEYS files to verify these. Relevant ASF > policy is here [2]. > > Trying the verify the latest source release, it fails with this err

Re: CI's working, and repeatable !!

On Mon, 29 Apr 2024 at 04:08, Josh McKenzie wrote: > I want to offer a heartfelt thanks to all involved for the focus and > energy that went into this! > … I also think there'd be significant value in more of us moving towards > using the JenkinsFile where at all possible. > Appreciated Josh.

CI's working, and repeatable !!

Good news. CI on 5.0 and trunk is working again, after an unexpected 6 weeks hiatus (and a string of general problems since last year). This includes pre-commit for 5.0 and trunk working again. More info… >From 5.0 we now have in-tree a Jenkinsfile that only relies on the in-tree scripts – it d

Re: [DISCUSS] Donating easy-cass-stress to the project

> > A separate subproject like dtest and the Java driver would maybe help > address concerns with introducing a gradle build system and Kotlin. > Nit, dtest is a separate repository, not a subproject. The Java driver is one repository to be in the Drivers subproject. Esoteric maybe, but ASF ter

Re: [DISCUSS] Donating easy-cass-stress to the project

On Fri, 26 Apr 2024 at 00:11, Jon Haddad wrote: > I should probably have noted - since TLP is no more, I renamed tlp-stress > to easy-cass-stress around half a year ago when I took it over again. > Do we have the IP cleared for donation ? At what SHA did you take and rename tlp-stress, and who

Re: [VOTE] Release Apache Cassandra 3.11.17

> Proposing the test build of Cassandra 3.11.17 for release. +1 Checked - signing correct - checksums are correct - source artefact builds - binary artefact runs - debian package runs - debian repo installs and runs

Re: [VOTE] Release Apache Cassandra 3.0.30

> Proposing the test build of Cassandra 3.0.30 for release. > +1 Checked - signing correct - checksums are correct - source artefact builds - binary artefact runs - debian package runs - debian repo installs and runs

Re: Is there appetite to maintain the gocql driver (in the drivers subproject) ?

We can open an issue with LEGAL to see what they say at least? >> > > > I will raise a LEGAL ticket. > > My question here is whether we have to go through the process of > best-efforts to get approval to donate (transfer copyright), or whether we > can honour the copyright on the prior work and mov

  1   2   3   4   5   6   7   8   9   10   >