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

Re: Changing the output of tooling between majors

ebody 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

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 b

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. D

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

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

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 end

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 soluti

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

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

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. - Sco

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] 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 evalu

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 Fri

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 lik

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 memb

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 clust

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] 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 appr

[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] Add subscription mangement instructions to user@, dev@ message footers

ail.com > wrote: +1 Kind 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 i

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 w

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

s aren’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 author,

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] spark-cassandra-connector donation to Analytics subproject

Supportive of accepting a donation of the Spark Cassandra Connector under the project's umbrella as well - I think that would be very welcome and appreciated. Spark Cassandra Connector and the Analytics library are also suited to slightly different usage patterns. SCC can be a good fit for Spar

Re: [VOTE] Release Apache Cassandra 5.0-rc1

We capture this as part of our release lifecycle document: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=132320437We define releases from our “Beta” milestone onward as API-stable:BetaDefinition / Expectations:Should be interface-stable, so that consumers do not have to incur any

Re: Welcome Joey Lynch as Cassandra PMC member

Congratulations Joey! - Scott — Mobile > On Jul 24, 2024, at 7:12 AM, Benjamin Lerer wrote: > >  > The PMC's members are pleased to announce that Joey Lynch has accepted the > invitation to become a PMC member. > > Thanks a lot, Joey, for everything you have done for the project all these

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

There are a few things unclear to me in this thread and the ticket, and details in the Jira are slim. Yifan / others supportive of backporting this feature, could you help me answer these questions? – What's this for? I'd appreciate a detailed explanation of what "Enhance CQLSSTableWriter to not

Re: Urgent: Potential Privacy Leakage Detected in Your Docker Hub Images

Hequan, thanks for your email. If you'd like to report a potential security/privacy issue in Apache Cassandra, a few paths are available: – Email priv...@cassandra.apache.org to report the issue privately to the Apache Cassandra Project Management Committee, who can privately review your report

Re: [VOTE] Release Apache Cassandra 4.1.6

Sorry to veer off from a vote in a vote thread. @Alex, can you say more about this statement: > " I think I would prefer to not introduce the change I have proposed (the one that would bring back non-binary compatibility)." If we have a path that resolves the issue and also maintains full compati

Re: 【DISCUSS】The configuration of Commitlog archiving

I appreciate this report and would love to work toward the direction it recommends.I’m also familiar with past concerns raised by others with our FQL configuration parameters that allow passing shell commands for FQL segment archival.We bias toward ensuring an MBean exists for dynamic modification

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

Thanks all for discussion on this.It’s hard to describe the sinking feeling that hit me when it became clear to me how common this problem is - and how horribly difficult it is to prove one has encountered this bug.Two years ago, my understanding was that this is an exceptionally rare and transient

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: >> https://gitbox.apache.org/repos/asf?p=cass

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

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

Hi folks,Thanks for discussion on this proposal, and also to Benedict who’s been fielding questions on the list!I’d like to restate the goals and problem statement captured by this proposal and frame context.Today, lightweight transactions limit users to transacting over a single partition. Thi

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

on the project; execute this development on ASF JIRA 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 rec

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

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

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] 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 th

Re: [DISCUSSION] Next release roadmap

has been identified> > >> > > *Pluggability improvements:*> > >> > > * Pluggable schema manager (CEP pending)> > > * Pluggable filesystem (CEP pending)> > > * Pluggable authenticator for CQLSH (CASSANDRA-16456). A CEP> draft> >

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 we

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

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: https://repository.apach

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: https://repository.apa

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 w

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–  https://dist.apache.org/repos/dist/dev/cassandra/3.11.12/apache-cas

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: >> https://gitbox.apache.org/repos/asf?p=c

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] 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: https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-7%3A+

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 J

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 release.Repository:https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-ap

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

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

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 m

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 m

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 bottlenec

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 of

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

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

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

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 sounds

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

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 u

Re: [VOTE] Release Apache Cassandra 5.0.2

+1. CASSANDRA-19989 and CASSANDRA-19968 will be good fixes to get out. On Oct 16, 2024, at 5:20 AM, Mick Semb Wever wrote: 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

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

Separating the two is completely fine yep -- just mentioned since deprecation/removal of stress also came up in the thread. Let's complete the donation. Just wanted to make sure we don't remove compaction-stress without a substitute. – Scott On Oct 14, 2024, at 10:46 AM, Brandon Williams wrote:

Re: [VOTE] Release Apache Cassandra 4.0.15

+1 - Scott > On Nov 13, 2024, at 12:47 PM, Brandon Williams > wrote: > > Proposing the test build of Cassandra 4.0.15 for release. > > sha1: b88fe80910deccc4eb648038a92729e31976e291 > Git: https://github.com/apache/cassandra/tree/4.0.15-tentative > Maven Artifacts: > https://repository.apach

Re: [DISCUSS] Chronicle Queue's development model and a hypothetical replacement of the library

Agree with Benedict's proposal here. In circumstances when I've needed to capture and work with FQL, I've found it cumbersome to work with Chronicle. The dial-home functionality and release process changes put it over the top for me. – Scott On Sep 19, 2024, at 8:40 AM, Josh McKenzie wrote: th

Re: [DISCUSS] Default Selection of 2i

Preference for a yaml property and MBean. Briefly:– All other secondary index config is defined in yaml.– System properties are more cumbersome to manage in that they’re less structured and commingle JVM configuration with database configuration.– We need an MBean hot property so users can flip to

Re: [VOTE] CEP-45: Mutation Tracking

+1 On Feb 5, 2025, at 2:50 PM, Alex Petrov wrote: +1 On Wed, Feb 5, 2025, at 11:03 PM, Blake Eggleston wrote: Ok ok, I've jumped gun here, sorry, small off by 24 error. Please continue voting, and I'll be back tomorrow :D On Wed, Feb 5, 2025, at 1:49 PM, Blake Eggleston wrote: The vote passes

Re: Merging compaction improvements to 5.0

Checking to confirm the specific patches proposed for backport – is it the trunk commit for C-20092 and the open GitHub PR against the 5.0 branch for C-15452 linked below? CASSANDRA-20092: Introduce SSTableSimpleScanner for compaction (committed to trunk) https://github.com/apache/cassandra/commi

Re: [VOTE][IP CLEARANCE] Spark-Cassandra-Connector

+1 On Mar 18, 2025, at 7:46 AM, Paulo Motta wrote: . PMC members, please check carefully the IP Clearance requirements before voting. 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.

Re: Constraint's "not null" alignment with transactions and their simplification

If the proposal does not introduce “check” as a reserved keyword that would require quoting in existing DDL/DML, this concern doesn’t apply and the email below can be ignored. This might be the case if “CHECK NOT NULL” is the full token introduced rather than “CHECK” separately from constraints tha

Re: [VOTE] Release Apache Cassandra 5.0.4

+1 Important we get a release out that resolves CASSANDRA-20449: Serialization can lose complex deletions in a mutation with multiple collections in a row On Apr 8, 2025, at 4:07 AM, Brandon Williams wrote: +1 On Mon, Apr 7, 2025 at 7:35 AM Brandon Williams wrote: Proposing the test build of

Re: [VOTE] Simplifying our release versioning process

+1 To the point on breaking changes and deprecations, I'd like to maintain a *very* high bar for user API-breaking changes – much higher than "our rules allow us to". Any time we break users, the project loses release uptake and creates friction for the community. – Scott On Apr 17, 2025, at 2:

Re: [DISCUSS] 5.1 should be 6.0

+1 6.0- Scott—MobileOn Apr 10, 2025, at 1:34 PM, Jeremy Hanna wrote:+1 for 6.0 for TCM/Accord changes, making it easier to make a case to upgrade dependencies like the Java/Python versions.On Apr 10, 2025, at 3:24 PM, Bernardo Botella wrote:+1 on 6.0On Apr 10, 2025, at 1:07 PM, Josh McKenzie wr

Re: [VOTE] Simplifying our release versioning process

I propose we:- Exclude JDK support from the subject of this vote.- And start a separate [DISCUSS] and [VOTE] thread to cover JDK/JRE lifecycle.Josh’s proposal that we are voting on does not address JDK versioning, and I don’t interpret the text of the proposal as a referendum on it. Many / most did

Re: CEP permission

Hi Runtian, thanks for reaching out. Your username should now have permission to create new wiki pages for CEPs in ASF Confluence. Cheers, – Scott On Apr 29, 2025, at 9:04 AM, Runtian Liu wrote: Hi, Could you please grant me permission to create a new CEP? My ID is curlylrt. Thank you! Thanks,

Re: [DISCUSS] AWS IAM-based client authentication

Joel, thanks for reaching out. This sounds interesting, I bet there are many who would benefit from IAM-based authentication. If you haven't yet, could you request a Jira account? Someone will be able to approve it almost immediately if you don't have one yet. https://selfserve.apache.org/jira-

Re: [DISCUSS] CEP-36: A Configurable ChannelProxy to alias external storage locations

e to Cassandra's class path, introducing potential problems with dependencies and their possible incompatibilities / different versions etc ... On Thu, Feb 27, 2025 at 6:21 AM C. Scott Andreas <sc...@paradoxica.net> wrote:I’d love to see this implemented — where “this” is a proxy for

Re: [DISCUSS] CEP-36: A Configurable ChannelProxy to alias external storage locations

I’d love to see this implemented — where “this” is a proxy for some notion of support for remote object storage, perhaps usable by compaction strategies like TWCS to migrate data older than a threshold from a local filesystem to remote object.It’s not an area where I can currently dedicate enginee

Re: CEP-15 Update

I’m also supportive of proceeding to merge.The CEP contributors have worked incredibly hard on the protocol and feature and I’m proud it’s reached this point.If the concern is trunk stability - we have been deploying trunk-derived builds for over six months and will continue to do so post-merge. Ma

Re: Dropwizard/Codahale metrics deprecation in Cassandra server

No strong opinion on particular choice of metrics library.My primary feedback is that if we swap metrics implementations and the new values are *different*, we can anticipate broad user confusion/interest.In particular if latency stats are reported higher post-upgrade, we should expect users to int

Re: Cassandra 5+ JDK Minimum Compatibility Requirement

My thinking is most closely aligned with Blake and Benedict’s views here.For the specific refactor in question, I support adoption of the language feature for new code or to cut existing code over to the new syntax as changes are made to the respective areas of the codebase. But I don’t support a s

Re: [VOTE] CEP-46: Finish Transient Replication/Witnesses

+1On May 12, 2025, at 10:00 AM, David Capwell wrote:+1On May 12, 2025, at 9:26 AM, Štefan Miklošovič wrote:+1, great stuff, looking forward to bring it out of experimentalOn Mon, May 12, 2025 at 4:27 PM Ariel Weisberg wrote:Hi dev@, I would like to start the voting for CEP-4

<    1   2