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

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

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

used in user schemas. If the proposal introduces this as a reserved word that would require it to be quoted if used in table or column names, this will create incompatibility for existing user queries on upgrade.Otherwise, ignore me. :)Thanks,– Scott–––MobileOn Apr 10, 2025, at 7:47 AM, Jon Haddad

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: [VOTE][IP CLEARANCE] Cassandra Cluster Manager (CCM)

+1 > On Mar 9, 2025, at 7:50 AM, Jeremiah Jordan wrote: > > +1 > > On Sun, Mar 9, 2025 at 8:03 AM Brandon Williams > wrote: >> +1 >> >> Kind Regards, >> Brandon >> >> On Sun, Mar 9, 2025 at 7:18 AM Mick Semb Wever > > wrote: >> > >> > Please v

Re: [DISCUSS] AWS IAM-based client authentication

x27;ve started here. That discussion will gauge receptivity and whether to proceed by acclamation; or whether the proposal is significant enough in scope to warrant a CEP doc and vote thread [3]. Cheers, – Scott [1] http://issues.apache.org/jira/browse/CASSANDRA [2] http://issues.apache.org/jira/b

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

production database process.The reason people care about object is that it’s 70%+ cheaper than flash - and 90%+ cheaper if the software querying it isn’t always running, too.– Scott—MobileOn Mar 4, 2025, at 12:29 PM, Štefan Miklošovič wrote:Jeff,when it comes to snapshots, there was already discussion in

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

/commit/3078aea1cfc70092a185bab8ac5dc8a35627330f CASSANDRA-15452: Improve disk access patterns during compaction and range reads (PR available) https://github.com/apache/cassandra/pull/3606 Thanks, – Scott On Feb 12, 2025, at 9:45 PM, guo Maxwell wrote: Of course, I definitely hope to see it merged

Re: [DISCUSS] Default Selection of 2i

the default in trunk seems fine.- Scott—MobileOn Feb 6, 2025, at 11:42 AM, Caleb Rackliffe wrote:System property works for me, even if I have to leave the default alone in 5.0.xOn Thu, Feb 6, 2025 at 1:34 PM Jeremiah Jordan <jeremiah.jor...@gmail.com> wrote: Rather than changing the d

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 >

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 Willi

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

mention of compaction-stress. :) – Scott > On Oct 13, 2024, at 8:01 PM, Štefan Miklošovič wrote: > > * easy-cass-stress, sorry. Everything else holds. > > On Sun, Oct 13, 2024 at 9:00 PM Štefan Miklošovič <mailto:smikloso...@apache.org>> wrote: >> What does "rep

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

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

/decompression, and deprecation of the prior approach sounds both reasonable and desirable to me.– Scott—MobileOn Aug 30, 2024, at 10:25 PM, Bowen Song via dev wrote: I'm not sure what is the concern here. Is it a malicious user exploiting this? Or human error

Re: [VOTE] Release Apache Cassandra 4.1.6

ou bringing it to everyone's attention. – Scott On Jul 31, 2024, at 1:05 PM, Caleb Rackliffe wrote: +1 to proceeding with a simple upgrade note in NEWS On Wed, Jul 31, 2024 at 12:50 PM Josh McKenzie < jmcken...@apache.org > wrote: Unfortunately, I can not immediately see a good way to pr

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

e the Foundation's vulnerability management process in conjunction with project maintainers. Note that this dev@ list is publicly archived and searchable. Replies here will be indexed and accessible via public internet. Thanks, – Scott On Jul 27, 2024, at 4:32 PM, musso...@sjtu.edu.cn wrote: De

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

in progress. – We shouldn't introduce upgrade paths that require users to upgrade to at-minimum-patchlevel versions of current releases before upgrading to future majors; I'm -1 on that. Thanks, – Scott On Jul 31, 2024, at 2:04 PM, Jon Haddad wrote: I'm kind of neutral on

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

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: [VOTE] Release Apache Cassandra 5.0-rc1 (take2)

observe alarmingly high latency stats following upgrade to a build including this bug, though they are not reflective of the actual query execution latency. This should be a quick patch to apply and re-vote on with a fresh build prepared. – Scott > On Jul 5, 2024, at 10:34 AM, Sam Tunnicli

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

t for Spark jobs that operate with a high degree of selectivity; vs. larger bulk scoops. – Scott On Jun 24, 2024, at 1:29 AM, Jon Haddad wrote: I also think it would be a great contribution, especially since the bulk analytics library can’t be used by the majority of teams, since it’s hard coded to

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

looks promising: https://tinselcity.github.io/SSL_Sendfile/– Scott—MobileOn Apr 19, 2024, at 11:31 AM, Jordan West wrote:If we are considering the main process then we have to do some additional work to ensure that it doesn’t put pressure on the JVM and introduce latency. That’s one thing I like about

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

ather than monitoring the output of a shell script. I'll yield to Hari to share more, though today is a public holiday in India. I do see this CEP as solving an important problem. Thanks, – Scott On Apr 8, 2024, at 10:23 AM, Jon Haddad wrote: This seems like a lot of work to create an rsy

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

er invalidation, but am not curious enough to learn how they make that work right now. :) I withdraw the proposal. 👍 – Scott On Jan 22, 2024, at 10:56 AM, Brandon Williams wrote: That's right, I'd forgotten about this. I change my +1 to -1, there's not enough value in this to

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

ing a message footer, I'll file an INFRA ticket with a link to this thread. Thanks, – Scott

Re: [Discuss] Generic Purpose Rate Limiter in Cassandra

beyond the scope of our direct control. Any server should have mechanisms to defend itself against any client; official or non–. Jon's also right that an implementation in the Spark Cassandra Connector may help jobs make progress at the maximum safe pace. Thanks for sharing this thoughtful docum

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

— appreciate and enjoying it.– Scott–––MobileOn Dec 20, 2023, at 7:52 AM, Benjamin Lerer wrote: If we are to address that within the CEP itself then we should discuss it here, as I would like to fully understand the approach as well as how it relates to consistency of execution and the idea of

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

proposal and discussion so far — appreciate and enjoying it. – Scott On Dec 20, 2023, at 7:52 AM, Benjamin Lerer wrote: If we are to address that within the CEP itself then we should discuss it here, as I would like to fully understand the approach as well as how it relates to consistency of

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! > &g

Re: [VOTE] Release Apache Cassandra 5.0-beta1

s rushed and timeline-driven rather than anchored in values of quality and data integrity. – Scott On Nov 28, 2023, at 9:20 AM, Brandon Williams wrote: If we are going to commit to beta2 before the summit because "putting a beta w/ SAI in this state into users’ hands at summit would be very

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

. - Scott — Mobile > On Sep 6, 2023, at 8:50 AM, Paulo Motta wrote: > >  > Hi, > > I've been bitten by OOMs with disk_access_mode:auto/mmap that were fixed by > changing to disk_access_mode:mmap_index_only. In a particular benchmark I got > 5x more read throughput on

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*

nothing that would prevent someone from continuing to use a sidecar-based solution in perpetuity if they preferred. - Scott > On Jul 26, 2023, at 3:25 PM, Jon Haddad wrote: > > I'm 100% in favor of repair being part of the core DB, not the sidecar. The > current (and past) stat

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

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: Changing the output of tooling between majors

OT, but would gladly +1(nb) a `nodetool --output-format=json` CEP. :) [ Some discussion also in: https://issues.apache.org/jira/browse/CASSANDRA-12698 ] > On Jul 8, 2023, at 11:26 AM, Josh McKenzie wrote: > >> I think they should not parse that output in the first place. Gradually >> introduc

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] Release Apache Cassandra 4.1.2

+1nb > On May 25, 2023, at 10:12 AM, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 4.1.2 for release. > > sha1: c5c075f0080f3f499d2b01ffb155f89723076285 > Git: https://github.com/apache/cassandra/tree/4.1.2-tentative > Maven Artifacts: > https://repository.apache.org/content

Re: [VOTE] Release Apache Cassandra 4.0.10

+1nb > On May 25, 2023, at 10:14 AM, Brandon Williams wrote: > > +1 > > Kind Regards, > Brandon > > On Thu, May 25, 2023 at 10:13 AM Mick Semb Wever wrote: >> >> Proposing the test build of Cassandra 4.0.10 for release. >> >> sha1: da77d3f729160e84fbab37666de99550be794265 >> Git: https://gi

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

ack count. A discuss thread seems fine for this rather than a CEP to me. — Scott > On Mar 6, 2023, at 2:51 AM, Miklosovic, Stefan > wrote: > > Hi all, > > some time ago we identified an issue with NetworkTopologyStrategy. The > problem is that when RF > number of ra

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

Re: [VOTE] CEP-21 Transactional Cluster Metadata

+1 nb > On Feb 6, 2023, at 9:05 PM, Ariel Weisberg wrote: > > +1 > > On Mon, Feb 6, 2023, at 11:15 AM, Sam Tunnicliffe wrote: >> Hi everyone, >> >> I would like to start a vote on this CEP. >> >> Proposal: >> https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-21%3A+Transactional+Cluste

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,

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

internal systems for unauthorized access from December 21. Details: https://circleci.com/blog/january-4-2023-security-alert/ — Scott

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: Cassandra Summit CFP update

things we build with it. One more thing. We need sponsors! If your employer > can, this is a great opportunity to get your brand out in front of people > building the future. I’ll be back. Go submit a talk. You’ll be happy you > did! Patrick* > -- Scott Hirleman scott.hirle...@gmail.com

Re: [DISCUSSION] Cassandra's code style and source code analysis

that users of modern build tools get for free. It also demands continuous, incremental work to adapt to changes in security and build tooling in use at many companies that don’t need to be made for projects using well-supported tools like Maven or Gradle. – Scott > On Nov 25, 2022, at 4:56

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

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 wr

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

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

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

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

. - Scott > On Aug 10, 2022, at 1:00 AM, Claude Warren, Jr via dev > wrote: > >  > At the moment we have 222 open pull requests. Some dating back 4 years. For > some the repository from which they were pulled from has been deleted. For > many there are branch conflict

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

  1   2   3   >