Re: [DISCUSS] CEP-40: Data Transfer Using Cassandra Sidecar for Live Migrating Instances

These are the salient points here for me, yes:> My understanding from the proposal is that Sidecar would be able to migrate from a Cassandra instance that is already dead and cannot recover.> That’s one thing I like about having it an external process — not that it’s bullet proof but it’s one less

Re: [DISCUSS] CEP-40: Data Transfer Using Cassandra Sidecar for Live Migrating Instances

n’t downleveled unexpectedly during migration.- ScottOn Apr 8, 2024, at 2:15 PM, C. Scott Andreas wrote:Hi Jon,Thanks for taking the time to read and reply to this proposal. Would encourage you to approach it from an attitude of seeking understanding on the part of the first-time CEP aut

Re: [DISCUSS] CEP-40: Data Transfer Using Cassandra Sidecar for Live Migrating Instances

Hi Jon, Thanks for taking the time to read and reply to this proposal. Would encourage you to approach it from an attitude of seeking understanding on the part of the first-time CEP author, as this reply casts it off pretty quickly as NIH. The proposal isn't mine, but I'll offer a few notes on

Re: [DISCUSS] Add subscription mangement instructions to user@, dev@ message footers

d Regards, Brandon On Mon, Jan 22, 2024 at 12:10 PM C. Scott Andreas < sc...@paradoxica.net > wrote: Hi all, I'd like to propose appending the following two footers to messages sent to the user@ and dev@ lists. The proposed postscript including line breaks is between the "X" blo

[DISCUSS] Add subscription mangement instructions to user@, dev@ message footers

Hi all, I'd like to propose appending the following two footers to messages sent to the user@ and dev@ lists. The proposed postscript including line breaks is between the "X" blocks below. User List Footer: X --- Unsubscribe: Send a blank email to user-unsubscr...@cassandra.apache.org

Re: [Discuss] Generic Purpose Rate Limiter in Cassandra

Jaydeep, thanks for reaching out and for sharing this proposal. I like the direction. Please also take a look at https://issues.apache.org/jira/browse/CASSANDRA-16663 , which adds coordinator-level rate limiting on request rate. This ticket introduced a lockless rate limiter patterned on an

Re: [DISCUSS] CEP-39: Cost Based Optimizer

Thanks for this proposal and apologies for my delayed engagement during the Cassandra Summit last week. Benjamin, I appreciate your work on this and your engagement on this thread – I know it’s a lot of discussion to field.On ALLOW FILTERING:I share Chris Lohfink’s experience in operating clusters

Re: [DISCUSS] CEP-39: Cost Based Optimizer

Thanks for this proposal and apologies for my delayed engagement during the Cassandra Summit last week. Benjamin, I appreciate your work on this and your engagement on this thread – I know it’s a lot of discussion to field. On ALLOW FILTERING: I share Chris Lohfink’s experience in operating

Re: Welcome Francisco Guerrero Hernandez as Cassandra Committer

Congratulations, Francisco! - Scott > On Nov 28, 2023, at 10:53 AM, Dinesh Joshi wrote: > > The PMC members are pleased to announce that Francisco Guerrero Hernandez > has accepted > the invitation to become committer today. > > Congratulations and welcome! > > The Apache Cassandra PMC

Re: [VOTE] Release Apache Cassandra 5.0-beta1

Agreed with Brandon, yes. I'm at a "-0 (nb)" on a beta release at this point. We're clearly finding (and resolving) lots of significant and in some case serious issues - ones that violate fundamental properties of the database. I'm very glad that we're finding and fixing these, but they feel

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

I’d happily be the first to vote -1(nb) on a release containing a known and reproducible bug that can result in data loss or an incorrect response to a query. And I certainly wouldn’t run it.Since we have a programmatic repro within just a few seconds, this should not take long to root-cause.On

Re: [DISCUSS] CommitLog default disk access mode

Let’s please not change the default at the same time the feature is introduced.Making the capability available will allow users to evaluate and quantify the benefit of the work, as well as to call out any unintended consequences. As users and the project gain confidence in the results, we can

Re: [VOTE] Accept java-driver

+1 (nb)Accepting this donation would mark a huge milestone for the project.On Oct 3, 2023, at 4:25 AM, Josh McKenzie wrote:I see now this will likely be instead apache/cassandra-java-driverI was wondering about that. apache/java-driver seemed pretty broad. :)From the linked page:Check that all

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

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 lower read latency and I wouldn’t run with auto. I’ve also not observed substantial heap pressure after switching - it was strictly an improvement. -

Re: [VOTE] Release Apache Cassandra 5.0-alpha1

A snapshot artifact seems more appropriate for early testing to me, rather than a voted / released build issued by the project given how much has yet to land.- ScottOn Aug 25, 2023, at 8:46 AM, Ekaterina Dimitrova wrote:+1On Fri, 25 Aug 2023 at 11:14, Mick Semb Wever

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

Given how early we are in the cycle with even the branch only recently cut (and how much is not yet present in the alpha), housecleaning seems like a positive impulse.On Aug 23, 2023, at 7:28 AM, Ekaterina Dimitrova wrote:Hi everyone,I wanted to clarify something. I understood dependency

Re: [VOTE] Release dtest-api 0.0.16

+1nbOn Aug 19, 2023, at 9:50 AM, Blake Eggleston wrote:+1On Aug 17, 2023, at 12:37 AM, Alex Petrov wrote:+1On Thu, Aug 17, 2023, at 4:46 AM, Brandon Williams wrote:+1Kind Regards,BrandonOn Wed, Aug 16, 2023 at 4:34 PM Dinesh Joshi wrote:>> Proposing the test build of in-jvm

Re: [Discuss] Repair inside C*

I agree that it would be ideal for Cassandra to have a repair scheduler in-DB. That said I would happily support an effort to bring repair scheduling to the sidecar immediately. This has nothing blocking it, and would potentially enable the sidecar to provide an official repair scheduling

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

I think these concerns are well-intended, but they feel rooted in uncertainty rather than in factual examples of areas where risk is present. I would appreciate elaboration on the specific areas of risk that folks imagine.I would encourage those who express skepticism to try the patch, and I

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

not able to take this action on others' behalf.More information on the project's mailing lists and how to join/leave them is here: https://cassandra.apache.org/_/community.htmlCheers,– ScottOn Jul 26, 2023, at 7:11 AM, C. Scott Andreas wrote:Can you say more about the shape of your conce

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

Can you say more about the shape of your concern?JCA/JCE conformance and correctness of the functions implemented are a responsibility of the ACCP/Corretto test suite (link). These are thoroughly exercised by Amazon and bundled into the Corretto JDK distribution Amazon ships as well.With regard to

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

Jeremiah, that’s my understanding as well. ACCP accelerates a subset of functions and delegates the rest. In years of using ACCP with Cassandra, I have yet to see an issue - or any case in which adopting ACCP was anything other than a strict benefit. - Scott > On Jul 26, 2023, at 5:33 AM, J.

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

Ekaterina, thank you for spearheading JDK17 support for Apache Cassandra! Exciting to get to this point.- ScottOn Jul 24, 2023, at 7:11 PM, Ekaterina Dimitrova wrote:Good news! After run #1638-39 you should not see anything else failing than SSLFactory test class. This known issue will be fixed

Re: Changing the output of tooling between majors

is as if somebody is "greping" it and it is not there, it will break.Do you understand that the same way or am I interpreting that wrong?________From: C. Scott Andreas Sent: Thursday, July 13, 2023 16:35To: dev@cassandra.apache.orgCc: devSubject: Re: Changing the output of tooli

Re: Changing the output of tooling between majors

"From what I see you guys want to condition any change by offering json/yaml as well."I don't think I've seen a proposal to block changes to nodetool output on machine-parseable formats in this thread.Additions of new delimited fields to nodetool output are mostly straightforward. Changes to

Re: Changing the output of tooling between majors

Agreed with Eric’s point here, yes.- ScottOn Jul 12, 2023, at 10:48 AM, Eric Evans wrote:On Wed, Jul 12, 2023 at 1:54 AM Miklosovic, Stefan wrote:I agree with Jackson that having a different output format (JSON/YAML) in order to be able to change the default output

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

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

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

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,

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

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

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

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

Re: [DISCUSS] Enhanced Disk Error Handling

is 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] 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,

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

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

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

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: [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

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

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

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

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

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

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

Re: Should we change 4.1 to G1 and offheap_objects ?

Jon, thanks for flagging that I didn't get a reply to your question on the thread.My main point in this thread is that I don't think post-beta is an appropriate time for a major prop change like this in the release cycle. Ideally at this point in the release cycle, major contributors and large

Re: Should we change 4.1 to G1 and offheap_objects ?

We have precedent for changing defaults that have near-universal positive impact in patchlevel releases, yep. disk_access_mode: auto -> mmap_index_only comes to mind. - Scott > On Nov 16, 2022, at 6:49 PM, Derek Chen-Becker wrote: > > I'm fine with not including G1 in 4.1, but would we

Re: Should we change 4.1 to G1 and offheap_objects ?

I share David and Aleksey’s views on this. We shouldn’t make major defaults changes right before RC. Might be worth adding a release note recommending users try them, and that they may become default in a future release though. — Scott > On Nov 16, 2022, at 3:38 PM, David Capwell wrote: > >

Re: CASSANDRA-14227 removing the 2038 limit

A 2-3% increase in storage volume is roughly equivalent to giving up the gain from LZ4 -> LZ4HC, or a one to two-level bump in Zstandard compression levels. This regression could be very expensive for storage-bound use cases.From the perspective of storage overhead, the unsigned int approach

Re: [VOTE] Release Apache Cassandra 4.0.7

+1nb — Scott > On Oct 21, 2022, at 4:06 AM, Brandon Williams wrote: > > +1 > > Kind Regards, > Brandon > >> On Wed, Oct 19, 2022 at 4:41 AM Mick Semb Wever wrote: >> >> >> Proposing the test build of Cassandra 4.0.7 for release. >> >> sha1: 277fa4fca4a80eb327be6559f993c91e42dd4009 >>

Re: [VOTE] Release Apache Cassandra 3.11.14

+1nb — Scott > On Oct 21, 2022, at 4:05 AM, Brandon Williams wrote: > > +1 > > Kind Regards, > Brandon > >> On Wed, Oct 19, 2022 at 4:41 AM Mick Semb Wever wrote: >> >> >> Proposing the test build of Cassandra 3.11.14 for release. >> >> sha1: 9d3327ef1321fe1bf4e7fc73ed6111da7c994553 >>

Re: [VOTE] Release Apache Cassandra 3.0.28

+1nb — Scott > On Oct 21, 2022, at 4:04 AM, Brandon Williams wrote: > > +1 > > Kind Regards, > Brandon > >> On Wed, Oct 19, 2022 at 4:41 AM Mick Semb Wever wrote: >> >> >> Proposing the test build of Cassandra 3.0.28 for release. >> >> sha1: 96c5332ee15f45ca5410caaa787cc88d6947b3c9 >>

Re: Cassandra Token ownership split-brain (3.0.14)

Hi Jaydeep,Thanks for reaching out and for bumping this thread.This is probably not the answer you’re after, but mentioning as it may address the issue.C* 3.0.14 was released over five years ago, with many hundreds of important bug fixes landing since July 2017. These include fixes for issues that

Re: [VOTE] Release Apache Cassandra 4.0.6

+1nbOn Aug 22, 2022, at 8:55 AM, 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 and no -1's.+1Checked- signing

Re: [DISCUSS] Remove Dead Pull Requests

Claude, can you say more about the goal or purpose that closing tickets advances? There are quite a lot of tickets with patches attached that the project has either not been able to act on at the time; or which the original contributor started but was unable to complete. We’ve picked up many

Re: [DISCUSS] Improve Commitlog write path

Amit, welcome and thank you for contributing the results from your test and opening this discussion.I don’t think anyone is arguing that the database shouldn’t take advantage of available hardware.A few things important to keep in mind when considering a patch like this:- Where the actual

Re: Welcome Jacek Lewandowski as Cassandra committer

Congratulations, Jacek!On Jul 6, 2022, at 7:38 AM, Mick Semb Wever wrote:Congrats Jacek! On Wed, 6 Jul 2022 at 15:00, Ekaterina Dimitrova wrote:Well deserved, congrats!  On Wed, 6 Jul 2022 at 8:56, Brandon Williams wrote:Congrats!On Wed, Jul 6, 2022, 7:00 AM Benjamin Lerer wrote:The PMC

Re: [VOTE] Release Apache Cassandra 4.1-alpha1

+1nb > On May 26, 2022, at 10:21 PM, Berenguer Blasi > wrote: > >  > +1 nb > > On 26/5/22 16:25, Ekaterina Dimitrova wrote: >> +1 (nb) >> >> On Tue, 24 May 2022 at 11:37, Andrés de la Peña wrote: >>> +1 nb >>> >>> On Tue, 24 May 2022 at 16:10, Benjamin Lerer wrote: +1 Le

Re: Appetite for a 4.1-alpha1 ?

Yep, supportive of anything that has the potential to increase the number of users evaluating a pre-release build. Alpha sounds great.On May 18, 2022, at 9:29 AM, David Capwell wrote:Works for meOn May 18, 2022, at 7:36 AM, Josh McKenzie wrote:+1 from me on the grounds that I expect users to

Re: [VOTE] Release Apache Cassandra 3.11.13

+1nb > On May 9, 2022, at 5:24 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

Re: [VOTE] Release Apache Cassandra 4.0.4

+1nb > On May 5, 2022, at 9:49 AM, Brandon Williams wrote: > > +1 > > Also passed dependency-check > > Kind Regards, > Brandon > >> On Wed, May 4, 2022 at 9:33 AM Mick Semb Wever wrote: >> >> Proposing the test build of Cassandra 4.0.4 for release. >> >> sha1:

Re: [VOTE] Release Apache Cassandra 3.0.27

+1, with special attention to CASSANDRA-14752 - didn’t realize we hadn’t released a build with a resolution for this yet. > On May 9, 2022, at 5:23 PM, Mick Semb Wever wrote: > >  >> >> > The vote will be open for 72 hours (longer if needed). Everyone who >> > has tested the build is invited

Re: [VOTE] Release dtest-api 0.0.13

+1nbOn Mar 31, 2022, at 10:21 AM, Dinesh Joshi wrote:+1On Mar 31, 2022, at 10:04 AM, David Capwell wrote:+1On Mar 31, 2022, at 9:53 AM, Alex Petrov wrote:Proposing the test build of in-jvm dtest API 0.0.13 for

Re: [DISSCUSS] Cassandra and Java 17

Ekaterina, thank you very much for sharing this! I admit, it’s much more involved than I expected to be. The —add-opens and —add-exports flags seem suitable for development and perhaps experimental support, but we’ll probably want to make changes to remove as many as we can before considering

Re: [VOTE] CEP-7: Storage Attached Index

+1nbOn Feb 17, 2022, at 2:37 PM, J. D. Jordan wrote:+1 nbOn Feb 17, 2022, at 4:25 PM, Brandon Williams wrote:+1On Thu, Feb 17, 2022 at 4:23 PM Caleb Rackliffe wrote:Hi everyone,I'd like to call a vote to approve CEP-7.Proposal:

Re: [VOTE] CEP-19: Trie memtable implementation

+1nb > On Feb 16, 2022, at 5:59 AM, Jeremy Hanna wrote: > > +1 nb. Thanks for all of the great work on this Branimir. Excited to see > this moving forward. > >> On Feb 16, 2022, at 7:56 AM, J. D. Jordan wrote: >> >> +1 nb >> On Feb 16, 2022, at 7:30 AM, Josh McKenzie wrote:

Re: [VOTE] release cassandra-harry 0.0.1

+1nb > On Feb 8, 2022, at 4:18 AM, Brandon Williams wrote: > > +1 > >> On Mon, Feb 7, 2022 at 8:44 AM Alex Petrov wrote: >> >> Proposing the test build of cassandra-harry 0.0.1 for release, to start >> using it in Cassandra tree. >> >> Repository: >>

Re: [VOTE] Release Apache Cassandra 3.11.12

Hi Dorian,I see that the following download URLs appear to work fine for me and result in the tarballs being downloaded as expected.–  https://dist.apache.org/repos/dist/dev/cassandra/3.11.12/apache-cassandra-3.11.12-src.tar.gz– 

Re: [DISCUSS] CEP-19: Trie memtable implementation

Branimir, thank you for sharing these results. The numbers are exciting - particularly the UCS test in which compaction keeps up, and your note mentioning 30% larger L0 flushes due to the more compact memory representation. Great work. — Scott > On Feb 7, 2022, at 8:39 AM, Branimir Lambov

Re: [VOTE] Release Apache Cassandra 3.0.26

+1nbOn Feb 7, 2022, at 6:14 AM, Mick Semb Wever wrote:Proposing the test build of Cassandra 3.0.26 for release.sha1: b18adcba1a808cf77576905dc2ceccd7783bdb18Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.26-tentativeMaven Artifacts:

Re: [VOTE] Release Apache Cassandra 4.0.2

+1nbOn Feb 7, 2022, at 6:15 AM, Mick Semb Wever wrote:Proposing the test build of Cassandra 4.0.2 for release.sha1: 25012d2fec1984cc9c1a352f214eb912ca4f10f5Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.2-tentativeMaven Artifacts:

Re: UDF future

I also (+1nb) support a proposal to deprecate JavaScript UDFs; to offer an interface for those who would like to supply a UDF implementation; and to extract/remove our current implementation. JDK17 support seems like a much higher priority than in-tree JS UDFs. — Scott > On Jan 18, 2022, at

Re: [VOTE] Formalizing our CI process

+1nb, with and without the amendment.Reason for mentioning without: I see the ability to cut a release to address an urgent security or data loss issue as one of the strongest arguments for maintaining green CI as a resting state so we are ready in the event of an emergency.Test results that

Re: [DISCUSSION] Next release roadmap

gt; >> > > *Pluggability improvements:*> > >> > > * Pluggable schema manager (CEP pending)> > > * Pluggable filesystem (CEP pending)> > > * Pluggable authenticator for CQLSH (CASSANDRA-16456). A CEP> draft> > > can be> > >

Re: [DISCUSS] Disabling MIME-part filtering on this mailing list

+1, this would be great to have fixed. Thanks for talking with Infra about this, Bowen. > On Dec 4, 2021, at 9:16 AM, Bowen Song wrote: > > Hello, > > > Currently this mailing list has MIME-part filtering turned on, which will > results in "From:" address munging (appending ".INVALID" to

Re: [DISCUSS] CEP-3: Guardrails

Re: "I think you all know my feels on JMX." –Super fair - I'd meant to speak in terms of desired outcome ("the feature should be dynamically configurable at runtime") rather than implementation ("this should be via JMX"). On Nov 1, 2021, at 1:24 PM, David Capwell wrote:If anyone wants to bite

Re: [DISCUSS] CEP-3: Guardrails

Thank you for starting discussion on this CEP, Andrés!Can the "Scope" section of the doc be filled out? It currently reads "TBD," but having a better understanding of the scope of work would help focus discussion: https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-3%3A+GuardrailsRe:

Re: [VOTE] Release dtest-api 0.0.11

+1nb > On Oct 29, 2021, at 6:17 AM, bened...@apache.org wrote: > > +1 > > From: Mick Semb Wever > Date: Friday, 29 October 2021 at 13:45 > To: dev@cassandra.apache.org > Subject: [VOTE] Release dtest-api 0.0.11 > Proposing the test build of in-jvm dtest API 0.0.11 for release. > >

Re: [VOTE] CEP-15: General Purpose Transactions

1. +1nb 2. +1nb 3. +1nb It’s been encouraging to follow discussion advancing potential enhancements to this proposal on the other threads. I disagree that it is a good outcome for the project and the Apache Cassandra user community to veto significant progress in this area on grounds that the

Re: [DISCUSS] CEP-15: General Purpose Transactions

in collaboration with other contributors; engage with members of the developer and user community on feedback, enhancements, and bugs; and intend deliver it to completion at a standard of readiness suitable for production transactional systems of record.Thanks,– ScottOn Oct 6, 2021, at 8:25 AM, C. Scott

Re: [DISCUSS] CEP-15: General Purpose Transactions

Adding a few notes from my perspective as well – Re: the UX question, thanks for asking this.I agree that offering a set of example queries and use cases may help make the specific use cases more understandable; perhaps we can prepare these as examples to be included in the CEP.I do think that

Re: [VOTE] Release dtest-api 0.0.9

+1nb > > On Sep 9, 2021, at 2:03 PM, David Capwell wrote: > > +1 > >> On Sep 9, 2021, at 1:52 PM, Mick Semb Wever wrote: >> >> +1 >> >>> On Thu, 2 Sept 2021 at 13:20, Mick Semb Wever wrote: >>> >>> Proposing the test build of in-jvm dtest API 0.0.9 for release. >>> >>> Repository: >>>

Re: [VOTE] Release Apache Cassandra 4.0.1

+1nb > On Sep 1, 2021, at 6:54 AM, Jeff Jirsa wrote: > > +1 > > >> On Wed, Sep 1, 2021 at 4:54 AM Sam Tunnicliffe wrote: >> >> Proposing the test build of Cassandra 4.0.1 for release. >> >> sha1: 6709111ed007a54b3e42884853f89cabd38e4316 >> Git: >>

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: >>

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

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

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

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: > >

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

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

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: >

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

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: 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

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: 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 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

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

  1   2   >