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

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

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

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

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 clust

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

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

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

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

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

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 reusi

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

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

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

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 ?

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 sounds

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

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

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

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

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

  1   2   >