Re: Hi-Rez of Apache Cassandra logo??

Hi Nate, Here are vectorized versions of the logo reading "Apache Cassandra": – http://paradoxica.net/img/cassandra/apache-cassandra.pdf – http://paradoxica.net/img/cassandra/apache-cassandra.eps This is not an official graphic, but for the sake of provenance: – The image is sourced from: https

Re: Rocksandra performance test result

Thanks for sharing, Jay. Could you say a bit more about how you’ve approached shadowing traffic against an alternate cluster? (Asking not so much with regard to the Rocksandra test, but toward shadowing methodology in general). – Scott > On Jun 1, 2018, at 9:46 PM, Jay Zhuang wrote: > > We'r

Re: Testing 4.0 Post-Freeze

Here’s why I really like this proposal: – It focuses our thought and effort on what it’ll take for each of us to become confident in running Apache Cassandra 4.0 for our most critical applications *prior* to cutting the dot-zero release. – It marks a commitment we can make to our user community:

Tracking Testing, Release Status, and Build Health

Hi everyone, As September approaches, I’ve been thinking about how we might be able to share notes on testing and build health. Some types of information I have in mind: – Known issues with builds (e.g., master / nightlies) that impact the ability to test the project. These could include known

Re: Apache Cassandra Blog is now live

Please feel free to file a ticket (label: Documentation and Website). It looks like Jekyll, the static site generator used to build the website, has a plugin that generates Atom feeds if someone would like to work on adding one: https://github.com/jekyll/jekyll-feed

Re: QA signup

Thanks for getting started with performance testing - this is exciting to hear! Periodic SNAPSHOT builds sounds great. I'd feel much better about builds published as date- or SHA-stamped snapshots / nightlies rather than calling them alphas at this point, as everyone's testing work is beginning.

Re: QA signup

@Mick, thanks for your reply re: publishing snapshots/nightlies. In terms of what’s needed to configure these, would it be automation around building release artifacts, publishing jars to the Maven snapshots repo, and to dist/dev/cassandra on dist.apache.org for binary a

Re: QA signup

Got it, thanks! On the target audience: This would primarily be C* developers who are working on development, testing, and validation of the release. The performance testing exercise Joey, Vinay, Sumanth, Jason, Jordan, and Dinesh completed yesterday is a good example [1]. For developers build

Measuring Release Quality

Hi everyone, Now that many teams have begun testing and validating Apache Cassandra 4.0, it’s useful to think about what “progress” looks like. While metrics alone may not tell us what “done” means, they do help us answer the question, “are we getting better or worse — and how quickly”? A frie

Re: QA signup

Mick – Got it, thanks and sorry to have misunderstood. No fault in your writing at all; that was my misreading. Agreed with you and Kurt; I can’t think of a pressing need or immediate use for the Maven artifacts. As you mentioned, all of the examples I’d listed require binary artifacts only. R

Re: Measuring Release Quality

ome back > to with some regularity so there's real pain and opportunity here for the > project imo. > > On Wed, Sep 19, 2018 at 9:32 PM Scott Andreas wrote: > >> Hi everyone, >> >> Now that many teams have begun testing and validating Apache Cassandra >> 4.

Re: 4.0 Testing Signup

Joey, thanks for starting this document! I’ve updated it to add several leads/contributors, and will probably have a few minor updates to add soon. On November 8, 2018 at 2:49:52 PM, Joseph Lynch (joe.e.ly...@gmail.com) wrote: On Thu, Nov 8, 2018 at 1:42 PM kurt

Re: 4.0 Testing Signup

Tommy, thank you! I’ve added your name as a contributor toward upgrade testing. Thanks also for all of the work you’ve done toward this already, filing CASSANDRA-{14820, 14836, 14841, 14842, 14848}. The testing you’ve done so far, patches contributed, and issues reported are all great finds. To

JIRA Reports in Confluence

Hi everyone, I’ve created several new JIRA reports in Confluence organized under this top-level page: https://cwiki.apache.org/confluence/display/CASSANDRA/Jira+reports These pages report open issues by Component and fix version. My aims in creating them are to: – Represent what’s currently sc

Re: JIRA Workflow Proposals

If I read Josh’s reply right, I think the suggestion is to periodically review active labels and promote those that are demonstrably useful to components (cf. folksonomy -> taxonomy). I hadn’t read the reply as indicating that la

Re: [VOTE] Change Jira Workflow

+1 non-binding > On Dec 17, 2018, at 7:28 AM, Marcus Eriksson wrote: > > +1 > > On Mon, Dec 17, 2018 at 03:19:07PM +, Benedict Elliott Smith wrote: >> I propose these changes >> * >> to the Jira Workflow for th

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

Echoing Jon’s point here – JH: “My thinking is I'd like to be able to recommend 4.0.0 as a production ready database for business critical cases” I feel that this is a standard that is both appropriate and achievable, and one I’m legitimately excited about. Re: the current state of the test pl

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

/edit# Thanks, Sumanth On Tue, May 28, 2019 at 10:43 PM Scott Andreas wrote: > Echoing Jon’s point here – > > JH: “My thinking is I'd like to be able to recommend 4.0.0 as a production > ready > database for business critical cases”

Re: Apache Cassandra Virtual meetings

On the "virtual" side -- I've spent some time this week reviewing how the Kubernetes community conducts their weekly meetings. References are at the end of this message. If we'd like to hold occasional virtual meetings among the dev and user community, here are some things that may help make th

Re: Apache Cassandra Virtual meetings

trial calls to see how bad things are? > > On Sat, 10 Aug 2019, 08:27 Scott Andreas, wrote: > >> On the "virtual" side -- >> >> I've spent some time this week reviewing how the Kubernetes community >> conducts their weekly meetings. Referen

Re: Stability of MaterializedView in 3.11.x | 4.0

Hi Pankaj, There aren't plans to include substantial changes to the materialized views implementation in C* 4.0, and I'm not aware of project contributors who plan major work on MV's post-4.0 at present. – Scott From: Pankaj Gajjar Sent: Tuesday, Septe

Re: time for a release?

+1nb for me for the 3.x releases. The user-facing issues resolved in 2.2 are slimmer and relatively minor (just 15225, 15050, 15045, 15041), but if it makes sense to release all three together, sounds good to me. – Scott On 10/4/19, 11:00 AM, "Jon Haddad" wrote: It's been a while since

Re: [VOTE] Apache Cassandra Release Lifecycle

There are two main benefits to agreeing on this: 1. Providing clarity for contributors on release phases – i.e., what types of changes are expected to land or be deferred during a particular point in that cycle. 2. Providing semantic clarity to users of Cassandra in terms of what they can expe

Re: [VOTE-2] Apache Cassandra Release Lifecycle

+1 nb From: sankalp kohli Sent: Tuesday, October 8, 2019 11:00 AM To: dev Subject: [VOTE-2] Apache Cassandra Release Lifecycle Hi, We have discussed in the email thread[1] about Apache Cassandra Release Lifecycle. We came up with a doc[2] for it. We h

Re: [VOTE-2] Apache Cassandra Release Lifecycle

Re: "How can we decide that *all* new features are suppose to go into trunk only, if we don’t even have an idea about the upcoming release schedule?" This is a great question. My understanding of the intent of the document is that new features are generally expected to land in trunk, with an exc

Re: moving the site from SVN to git

Thanks, Jon! From: Jon Haddad Sent: Thursday, October 17, 2019 7:07 AM To: dev@cassandra.apache.org Subject: Re: moving the site from SVN to git The migration is finished. I had to fix a few things along the way. The docker containers didn't build corre

Re: Can we kick off a release?

Yes, we should also make sure to include: CASSANDRA-15363: Read repair in mixed mode between 2.1 and 3.0 on COMPACT STORAGE tables causes unreadable sstables after upgrade This is currently r=2 and about ready to land. From: beggles...@apple.com on beha

Re: [VOTE] Release Apache Cassandra 3.0.19

+1 nb — Scott > On Oct 24, 2019, at 7:09 PM, Dinesh Joshi wrote: > > +1 > > Thanks, Michael! > > Dinesh > >> On Oct 24, 2019, at 10:25 AM, Michael Shuler wrote: >> >> I propose the following artifacts for release as 3.0.19. >> >> sha1: a81bfd6b7db3a373430b3c4e8f4e930b199796f0 >> Git: >>

Re: [VOTE] Cassandra Enhancement Proposal (CEP) documentation

+1 nb > On Nov 1, 2019, at 5:36 AM, Benedict Elliott Smith > wrote: > > +1 > > On 01/11/2019, 12:33, "Mick Semb Wever" wrote: > >Please vote on accepting the Cassandra Enhancement Proposal (CEP) document > as a starting point and guide towards improving collaboration on, and success

Re: [VOTE] Cassandra Enhancement Proposal (CEP) documentation

uploaded anywhere? I would love to watch, since I missed the event. Kind regards, Michael On 11/1/19 9:07 AM, Scott Andreas wrote: > +1 nb > >> On Nov 1, 2019, at 5:36 AM, Benedict Elliott Smith >> wrote: >> >> +1 >> >> On 01/11/2019, 12:33, "Mick Se

Re: Offering some project management services

Happy to add detail on the origin of this from my side – At NGCC 2019 alongside ApacheCon in Las Vegas this year, I proposed the idea of periodic public video calls and an approach toward executing on the roles of product and release management as a community of volunteers. The thesis of the pr

Re: Cassandra 4.0 Dev Work Status

I think the intent of the milestones is meant to indicate that contributors view completion of those items as exit criteria for alpha / beta / RC; not necessarily that all items will be completed in strict order. In principle I'd interpret work targeting earlier milestones as higher priority, b

Re: Cassandra 4.0 Dev Work Status

Just realized I'd misunderstood Mick's original email, apologies. I'd originally interpreted it as a question of prioritization, but the intent was to ensure that the Fix Version field reflects the release a given change is /included in/, not /originally targeted for/. Apologies for my misunders

Re: Apache Cassandra Contributor Meeting

ch up on what's happening here, here's the establishing > > thread: > > > https://lists.apache.org/thread.html/aa54420a43671c00392978f2b0920bc6926ca9ba1e61a486ad39fb21%40%3Cdev.cassandra.apache.org%3E > > > > Key points that Scott Andreas proposed in the initial email was

Re: Apache Cassandra Contributor Meeting

t; Laxmikant > > On Tue, Jan 21, 2020 at 9:39 PM Scott Andreas wrote: > >> Thanks Jordan! >> >> Added a couple more items as well: >> – Call for volunteers to lead 4.0 quality tracks that need an owner >> – 3.0 / 3.11 branch status >> >> ___

Re: Apache Cassandra Contributor Meeting

_____ From: Scott Andreas Sent: Tuesday, January 21, 2020 9:58 PM To: dev@cassandra.apache.org Cc: Jordan West Subject: Re: Apache Cassandra Contributor Meeting Hi Laxmikant, Thanks for reaching out. The meeting was recorded; I think the video is being prepared now. Patrick can probably sha

Re: Feedback from the last Apache Cassandra Contributor Meeting

Thank you, Patrick! > On Feb 11, 2020, at 3:05 PM, Patrick McFadin wrote: > > Survey is closed. Thank you everyone that took time to give your feedback. > Here are the results: https://www.surveymonkey.com/results/SM-7YTMZYLT7/ > > Based on the feedback, these meetings are useful and this seem

Re: Idea: Marking required scope for 4.0 GA vs. optional

Yep that makes sense to me. There's still much work to be done to exercise 4.0 builds to identify unknown issues that haven't yet been filed – but those items can be tagged as release blockers as they're identified. 👍 From: Joshua McKenzie Sent: Saturda

Re: Discussion: addition to CEP guide

Sounds good to me as well, thanks for suggesting. From: Jon Haddad Sent: Wednesday, April 22, 2020 9:54 AM To: dev@cassandra.apache.org Subject: Re: Discussion: addition to CEP guide Great idea Josh, +1 On Wed, Apr 22, 2020 at 9:47 AM Benedict Elliott Sm

Re: List of serious issues fixed in 3.0.x

Sankalp, thanks for sending the spreadsheet and Josh for preparing this analysis (pending image issues; look forward to reading)! I'd encourage everyone involved in the project to review the list of tickets captured here. These issues aren't theoretical and represent real scenarios that result

Re: [DISCUSS] CASSANDRA-13994

That makes sense to me, yep. My hope and expectation is that the time required for "verification work" will shrink dramatically in the not too distant future - ideally to a period of less than a month. In this world, the cost of missing one train is reduced to catching the next one. One of the

Re: [DISCUSS] Considering when to push tickets out of 4.0

I'll take attribution for the delay in comment on 15299; this was in part a case of a pressing need to investigate a potential 3.0 data resurrection issue drawing attention from 4.0. I agree with the statement that we shouldn't consider protocol V5 ready for finalization in its current form. If

Re: [VOTE] Project governance wiki doc

+1 nb, thanks for everyone's work on this! From: Jordan West Sent: Tuesday, June 16, 2020 8:09 PM To: dev@cassandra.apache.org Subject: Re: [VOTE] Project governance wiki doc +1 nb On Tue, Jun 16, 2020 at 5:45 PM Jake Luciani wrote: > +1 > > On Tue, Ju

Re: [VOTE] Project governance wiki doc (take 2)

+1 nb > On Jun 20, 2020, at 9:37 AM, Joshua McKenzie wrote: > > +1 (binding / present / active) > > On Sat, Jun 20, 2020 at 12:23 PM Ekaterina Dimitrova > wrote: > >> +1(non-binding) >> >> On Sat, 20 Jun 2020 at 11:38, Brandon Williams wrote: >> >>> +1 >>> >>> On Sat, Jun 20, 2020, 10:12

Re: Community marketing for C*

Melissa, welcome to the project and thank you for your email! One of Apache Cassandra’s longstanding challenges has been establishing a voice for itself as an open source project independent of the many corporate entities that support its development. Working together to build awareness and ent

Re: [DISCUSS] When to branch 4.0

Great point re: increasing the public visibility of testing and validation activity. I’ll partner with a few contributors I work with to prep a summary of our findings that aren’t already captured in JIRA tickets we’ve filed against 3.x and 4.0 so far (as David mentioned, many issues we’re iden

Re: [DISCUSS] A point of view on Testing Cassandra

Thanks for starting discussion! Replying to the thread with what I would have left as comments. –– > As yet, we lack empirical evidence to quantify the relative stability or > instability of our project compared to a peer cohort I think it's more important that we set a standard for the pr

Re: 4.0 GA scope: the opt-in approach (CALL TO ACTION)

Thank you, Josh! Just took a pass and opted in 22 of the 55 tickets with the triage keyword as of this evening, most of which are active this month or are for flaky/failing tests. – Scott From: Joshua McKenzie Sent: Monday, October 5, 2020 11:01 AM To:

Re: [VOTE] Release dtest-api 0.0.6

+1nb From: Jordan West Sent: Thursday, October 8, 2020 7:40 AM To: dev@cassandra.apache.org Subject: Re: [VOTE] Release dtest-api 0.0.6 +1 On Thu, Oct 8, 2020 at 7:25 AM Brandon Williams wrote: > +1 > > On Thu, Oct 8, 2020 at 3:20 AM Oleksandr Petrov >

Re: Supported upgrade path for 4.0

Great, thanks Ben! The primary configuration my colleagues and I will be vetting is the 3.0.x -> 4.0 path (implicitly, 2.1 -> 3.0 -> 4.0). From a quality + safety perspective we will be ensuring that it’s a smooth ride for folks who opt for this route; though no major concerns on my part with t

Re: [VOTE] Release Apache Cassandra 3.0.23

+1 nb > On Oct 31, 2020, at 11:37 AM, Brandon Williams wrote: > > +1 > > Signatures and checksums match, source build works, as does dis/enablebinary. > > On Thu, Oct 29, 2020 at 7:29 AM Mick Semb Wever wrote: >> >> Proposing the test build of Cassandra 3.0.23 for release. >> >> sha1: 31530

Re: [VOTE] Release Apache Cassandra 4.0-beta3

+1 nb > On Oct 31, 2020, at 11:38 AM, Brandon Williams wrote: > > +1 > > Signatures and checksums match, source build works, as does dis/enablebinary. > > On Thu, Oct 29, 2020 at 7:30 AM Mick Semb Wever wrote: >> >> Proposing the test build of Cassandra 4.0-beta3 for release. >> >> sha1: be

Re: Cassandra 4.0 dropping support for older distributions Centos 5, Debian 4, Ubuntu 7.10

Thanks for flagging this, Mick! No concern from me as all EOL dates for these distributions have long passed and agreed that a NEWS entry is a good way to surface to users. From: Mick Semb Wever Sent: Friday, November 13, 2020 12:09 PM To: dev@cassandra.

Re: [VOTE] Release dtest-api 0.0.7

+1nb From: Brandon Williams Sent: Thursday, December 3, 2020 10:05 AM To: dev@cassandra.apache.org Subject: Re: [VOTE] Release dtest-api 0.0.7 +1 On Thu, Dec 3, 2020, 7:02 AM Oleksandr Petrov wrote: > Proposing the test build of in-jvm dtest API 0.0.7

Re: [DISCUSS] Revisiting the quality testing epic scope

Thanks for raising the question, Benjamin! Notes on a few tickets inline below. Non-Blocking: – CASSANDRA-15537 Local Read/Write Path: Upgrade and Diff Test I think it’s reasonable to consider this ticket complete. Yifan and others have worked to execute several dozen diff tests and while I’m sur

Re: [DISCUSS] Revisiting the quality testing epic scope

e a timeframe in mind for releasing 4.0 GA? Assuming that there is no sudden burst in the number of issues. We do have several flaky test tickets that could use attention, though > I believe that Adam, Berenguer and Brandon have started focusing on them. On Sat, Jan 16, 2021 at 10:49 PM Sco

Re: [VOTE] Release Apache Cassandra 3.0.24

+1 nb From: Yifan Cai Sent: Friday, January 29, 2021 12:51 PM To: dev@cassandra.apache.org Subject: Re: [VOTE] Release Apache Cassandra 3.0.24 +1 nb On Fri, Jan 29, 2021 at 7:11 AM Aleksey Yeshchenko wrote: > +1 > > > On 29 Jan 2021, at 14:31, Ekaterin

Re: Welcome Paulo Motta as Cassandra PMC member

Congratulations, Paulo! From: Jordan West Sent: Wednesday, February 10, 2021 5:39 PM To: dev@cassandra.apache.org Subject: Re: Welcome Paulo Motta as Cassandra PMC member Congrats Paulo! Jordan On Tue, Feb 9, 2021 at 10:25 PM Berenguer Blasi wrote: >

Re: Project Roadmap

+1 as well. This would be great for the project and for our users. From: Benedict Elliott Smith Sent: Tuesday, March 2, 2021 3:26 AM To: dev@cassandra.apache.org Subject: Re: Project Roadmap Yep, I'm not proposing we start discussions right now. Just want

Re: Roadmap for 4.0

Re-raising a point made earlier in the thread by Jeff and affirmed by Josh: ––– Jeff: >> A hard date for a feature freeze makes sense, a hard date for a release >> does not. Josh: > Strongly agree. We should also collectively define what "Done" looks like > post freeze so we don't end up in bike-

Re: [VOTE] Release Apache Cassandra 4.0-rc1

+1 nb. This is a huge milestone for the project. From: Paulo Motta Sent: Tuesday, March 30, 2021 4:57 AM To: Cassandra DEV Subject: Re: [VOTE] Release Apache Cassandra 4.0-rc1 +1 Em ter., 30 de mar. de 2021 às 00:25, Dinesh Joshi escreveu: > +1 > > Di

Re: [DISCUSSION] Next release roadmap

Thanks for starting this discussion, Benjamin! I share others’ enthusiasm on this thread for improvements to secondary indexes, trie-based partition indexes, guardrails, and encryption at rest. Here are some other post-4.0 areas for investment that have been on my mind: �C Transactional Cluster

Re: [VOTE] Release Apache Cassandra 4.0-rc1 (take2)

+1nb, thank you! From: Ekaterina Dimitrova Sent: Wednesday, April 21, 2021 12:23 PM To: dev@cassandra.apache.org Subject: Re: [VOTE] Release Apache Cassandra 4.0-rc1 (take2) +1 and thanks everyone for all the hard work Checked: - gpg signatures - sha che

Re: [VOTE] Release Apache Cassandra 4.0-rc1 (take2)

Looks like we’ve crossed the 72-hour mark. Shall we tally? 😀 > On Apr 23, 2021, at 4:43 AM, Paulo Motta wrote: > +1 > >> On Fri, 23 Apr 2021 at 06:35 Aleksey Yeshchenko >> wrote: >> +1 On 23 Apr 2021, at 08:51, Sam Tunnicliffe wrote: >>> +1 On 23 Apr 2021, at 04:19, Jasonstack Zhao

Re: Welcome Stefan Miklosovic as Cassandra committer

Congratulations, Štefan! From: David Capwell Sent: Monday, May 3, 2021 10:53 AM To: dev@cassandra.apache.org Subject: Re: Welcome Stefan Miklosovic as Cassandra committer Congrats! > On May 3, 2021, at 9:47 AM, Ekaterina Dimitrova wrote: > > Congrat Ste

Re: Welcome Caleb Rackliffe as Cassandra committer

Congratulations, Caleb! — Scott > On May 14, 2021, at 10:29 AM, Andrés de la Peña > wrote: > > Congrats Caleb, well deserved! :) > >> On Fri, 14 May 2021 at 17:53, Paulo Motta wrote: >> >> Awesome, congratulations Caleb!! :) >> >> Em sex., 14 de mai. de 2021 às 13:16, Patrick McFadin >>

Re: Welcome Dinesh Joshi as Cassandra PMC member

Congratulations, Dinesh! From: Lorina Poland Sent: Wednesday, June 2, 2021 9:27 AM To: dev@cassandra.apache.org Subject: Re: Welcome Dinesh Joshi as Cassandra PMC member Congratulations, Dinesh! Lorina Poland e. lor...@datastax.com w. www.datastax.com

Re: Are we ready for 4.0.0 (GA) ?

A second RC is appropriate given the revert of CASSANDRA-15899 necessitated by the discovery of CASSANDRA-16735: Adding columns via ALTER TABLE can generate corrupt sstables. Ekaterina and Benedict's statement regarding the true positive rate of flaky tests also shows the value of resolving the

Re: [VOTE] Release Apache Cassandra 4.0-rc2

+1 nb From: Andrés de la Peña Sent: Monday, June 28, 2021 1:04 PM To: dev@cassandra.apache.org Subject: Re: [VOTE] Release Apache Cassandra 4.0-rc2 +1 (nb) On Mon, 28 Jun 2021 at 21:01, Jon Meredith wrote: > +1 (nb) > > On Mon, Jun 28, 2021 at 9:47 AM

Re: [VOTE] Release Apache Cassandra 4.0.0 (take2)

+1nb. Thank you for sharing a Circle run, Sumanth! From: Sumanth Pasupuleti Sent: Wednesday, July 14, 2021 12:52 PM To: dev@cassandra.apache.org Subject: Re: [VOTE] Release Apache Cassandra 4.0.0 (take2) +1 (nb) Confirmed passing j8 UTs and dtests https:

Re: [VOTE] Release Apache Cassandra 4.0.0 (third time is the charm)

+1 nb > On Jul 23, 2021, at 2:46 PM, Mick Semb Wever wrote: > >  >> >> >> 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 an

Re: [VOTE] Release Apache Cassandra 3.0.25

+1nb, primarily for CASSANDRA-16735. > On Jul 25, 2021, at 10:40 AM, Brandon Williams wrote: > > I am proposing the test build of Cassandra 3.0.25 for release. > > sha1: 06235e93e16d1f483a3b03ba02f8fb29e33305fa > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tag

Re: [VOTE] Release Apache Cassandra 3.11.11

+1nb > On Jul 25, 2021, at 12:06 PM, Brandon Williams wrote: > > I am proposing the test build of Cassandra 3.11.11 for release. > > sha1: 4cafe2288e56e1135d65e76adbcd6c2de9306d6b > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.11-tentative > Maven Art

Re: [VOTE] CEP-10: Cluster and Code Simulations

+1 nb From: Sam Tunnicliffe Sent: Tuesday, July 27, 2021 12:54 AM To: dev@cassandra.apache.org Subject: Re: [VOTE] CEP-10: Cluster and Code Simulations +1 > On 26 Jul 2021, at 11:51, bened...@apache.org wrote: > > Proposing the CEP-10 (Cluster and Code S

Re: Welcome Adam Holmberg as Cassandra committer

Congratulations, Adam! 🎉 From: Joseph Lynch Sent: Tuesday, August 17, 2021 7:44 AM To: dev@cassandra.apache.org Subject: Re: Welcome Adam Holmberg as Cassandra committer Congratulations Adam! On Tue, Aug 17, 2021 at 10:25 AM Jordan West wrote: > > Congr

Re: [DISCUSS] CEP 14: Paxos Improvements

Benedict, thank you for sharing this CEP! Adding some notes on why I support this proposal: - Reducing common-case round trips from 4x to 2x on writes and 2x to 1x on reads is a huge improvement. This latency reduction may be sufficient to allow many users of Cassandra who operate in a single d

Re: Potential issues during 4.0 upgrade

Thank you for raising this, Sam! Agreed this is a bug that warrants releasing 4.0.1 and notifying user@. To elaborate on impact, this issue can produce a state in rolling 3.x -> 4.0 upgrades in which 4.0 nodes fail to serialize gossip state during the shadow round once the size of this state ex

Re: [DISCUSS] Java support roadmap

+1 for moving Java 11 support out of experimental for 4.0 at minimum, and no concern with doing so for 3.0/3.11 if someone were to propose. I and contributors I work with have deployed 4.0 + JDK11 in production, have found no issues, and would treat any issues that arise as ones we’re able to j

Re: [VOTE] CEP-14: Paxos Improvements

+1 > On Aug 27, 2021, at 12:58 PM, Mick Semb Wever wrote: > >  >> >> >> Proposal: >> https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-14%3A+Paxos+Improvements >> Discussion: >> https://lists.apache.org/thread.html/r1af3da2d875ef93479e3874072ee651f406b96c915759c7968d3266e%40%3Cdev.cas

Re: [VOTE] CEP-25: Trie-indexed SSTable format

+1nbOn Dec 19, 2022, at 1:27 PM, Josh McKenzie wrote:+1On Mon, Dec 19, 2022, at 11:54 AM, SAURABH VERMA wrote:+1On Mon, Dec 19, 2022 at 9:36 PM Benjamin Lerer wrote:+1Le lun. 19 déc. 2022 à 16:31, Andrés de la Peña a écrit :+1On Mon, 19 Dec 2022 at 15:11, Aleksey Yeshchenko wrote:+1On 19 Dec

CircleCI Security Incident

FYI for visibility among our development community - CircleCI reports they have experienced a security incident and are asking all users to immediately rotate any secrets stored in CircleCI (environment variables, object storage credentials, etc). They’re also recommending monitoring any inter

Re: Cassandra Summit update for 2023-01-24

Hugely excited to this – thanks to the Program Committee and to the Linux Foundation for organizing!It's been a long few years away from conferences and I can't wait to see all of you.Beyond learning about what everyone is doing with Apache Cassandra, I'm looking forward to the hallway chats an

Re: [ANNOUNCE] Evolving governance in the Cassandra Ecosystem

Josh and all PMC members, thank you for your work on this!Supportive of the changes and grateful to have scaffolding in place to accommodate current/incoming subprojects.– ScottOn Jan 26, 2023, at 1:21 PM, Josh McKenzie wrote:The Cassandra PMC is pleased to announce that we're evolving our go

Re: Implicitly enabling ALLOW FILTERING on virtual tables

There are some ideas that development community members have kicked around that may falsify the assumption that "virtual tables are tiny and will fit in memory."One example is CASSANDRA-14629: Abstract Virtual Table for very large result setshttps://issues.apache.org/jira/browse/CASSANDRA-14629C

Re: Welcome Patrick McFadin as Cassandra Committer

Congratulations, Patrick!On Feb 2, 2023, at 9:46 PM, Berenguer Blasi wrote:Welcome!On 3/2/23 4:09, Vinay Chella wrote:Well deserved one, Congratulations, Patrick. On Fri, Feb 3, 2023 at 4:01 AM Josh McKenzie wrote:Congrats Patrick! Well deserved.On Thu, Feb 2, 2023, at 5:

Re: [DISCUSS] Merging incremental feature work

Supportive of this as well. I see testability of trunk against JDK17 as more important than continuous preservation of support for scripted UDFs *during* that development. Will be tempted to cherry-pick this and begin kicking the tires as soon as it’s ready. 👍 - Scott > On Feb 5, 2023, at 6:

Re: Google Season of Documentation proposal

Thanks and congratulations Lorina! — Scott > On Feb 16, 2023, at 4:29 PM, Lorina Poland wrote: > > Good news! The Open Collective application was accepted! Step one is done. > > Lorina > >> On 2023/02/13 22:23:35 Lorina Poland wrote: >> Hi all - >> >> I have submitted an application to the

Re: Downgradability

I realize my feedback on this has been spread across tickets and older mailing list / wiki discussions, so I'll offer a proposal here.Starting with goals -1. Cassandra users must be able to abort and revert an upgrade to a new version of the database that introduces a new major SSTable format.Thi

Re: [DISCUSS] Next release date

Regarding “We should focus on why it took 6 months to go from 4.1 first alpha to GA and what happened inside that time window.” —Speaking solely from my perspective, the single biggest time draw was tracking down and resolving https://issues.apache.org/jira/browse/CASSANDRA-18110.One of the strateg

Re: Degradation of availability when using NTS and RF > number of racks

Modifying NTS in place would not be possible if it changes rack placement in a way that breaks existing clusters on upgrade. A strategy introducing a change to placement like this would need a new name. A new strategy would be fine in trunk. Logging a warning seems appropriate if RF > rack coun

Re: [DISCUSS] Enhanced Disk Error Handling

For this to be safe, my understanding is that:– A repair of the affected range would need to be completed among the replicas without such corruption (including paxos repair).– And we'd need a mechanism to execute repair on the affected node without it being available to respond to queries, eith

Re: [DISCUSS] Enhanced Disk Error Handling

more of an optimization to avoid read repair for queries over the affected range grinding traffic to a halt, rather than necessary for safety. — Scott > On Mar 8, 2023, at 8:54 AM, C. Scott Andreas wrote: >  > For this to be safe, my understanding is that: > > – A repair of the

Re: [DISCUSS] Drop support for sstable formats m* (in trunk)

I agree with Aleksey's view here.To expand on the final point he makes re: requiring SSTables be fully rewritten prior to rev'ing from 4.x to 5.x (if the cluster previously ran 3.x) –This would also invalidate incremental backups. Operators would either be required to perform a full snapshot ba

Re: Please grant Wiki access for CEP

Done, thanks Doug!On Mar 21, 2023, at 2:22 PM, Doug Rohrer wrote:Hi folks:I’d like to post a CEP, but given it’s the first time I’m trying to contribute to the wiki, I don’t have access.If someone with access could please grant user drohrer access to post, I’d greatly appreciate it.Thanks,Doug

Re: [EXTERNAL] Re: (CVE only) support for 3,11 beyond published EOL

If there’s lack of clarity around EOL policy and dates, we should absolutely make this clear.Most releases of the project have been “LTS” in that the release cadence since 2018 has not been rapid but focused on minor enhancements on long-lived branches like 3.0, 3.11, and 4.0.x. But I’d distinguish

Re: [VOTE] CEP-28: Reading and Writing Cassandra Data with Spark Bulk Analytics

+1nb.As someone familiar with this work, it's pretty hard to overstate the impact it has on completing Cassandra's HTAP story. Eliminating the overhead of bulk reads and writes on production OLTP clusters is transformative.– ScottOn May 4, 2023, at 9:47 AM, Doug Rohrer wrote:Hello all,I’d like

Re: [VOTE] CEP-8 Datastax Drivers Donation

+1nbOn Jun 13, 2023, at 10:25 AM, German Eichberger via dev wrote: + 1 Great to see this moving forward! From: Abe Ratnofsky Sent: Tuesday, June 13, 2023 10:09 AM To: dev@cassandra.apache.org Subject: [EXTERNAL] Re: [VOTE] CEP-8 Datastax Drivers Donation   +1 (nb) On Jun 13, 202

Re: [DISCUSS] Using ACCP or tc-native by default

+1 for ACCP and can attest to its results. ACCP also optimizes for a range of hash functions and other cryptographic primitives beyond TLS acceleration for Netty.On Jun 22, 2023, at 2:07 PM, Jeff Jirsa wrote:Either would be better than today. On Thu, Jun 22, 2023 at 1:57 PM Jordan West wrote:

Re: [VOTE] CEP 33 - CIDR filtering authorizer

+1nbOn Jun 28, 2023, at 6:40 PM, Abe Ratnofsky wrote:+1 (nb)On Jun 28, 2023, at 18:38, guo Maxwell wrote:+1 Nate McCall 于2023年6月29日 周四上午9:25写道：+1 On Wed, Jun 28, 2023 at 5:17 AM Shailaja Koppu wrote:Hi Team,(Starting a new thread for VOTE instead of reusi

Re: [DISCUSS] Conducting a User Survey

Thanks Patrick. I like the idea of a user survey.Added a handful of comments in the doc. 👍– ScottOn Jul 11, 2023, at 12:51 AM, Mick Semb Wever wrote:Looks good to me, thanks Patrick.On Tue, 11 Jul 2023 at 03:11, Patrick McFadin wrote:For quite a few years, I have done Twitter polls to gather

  1   2   >