Re: [VOTE] Simplifying our release versioning process

+1 > On 17 Apr 2025, at 16:58, Josh McKenzie wrote: > > [DISCUSS] thread: > https://lists.apache.org/thread/jy6vodbkh64plhdfwqz3l3364gsmh2lq > > The proposed new versioning mechanism: > • We no longer use semver .MINOR > • Online upgrades are supported for all GA supported releases at

Re: [DISCUSS] Virtualise system_schema (CASSANDRA-19129)

In trunk that durability comes from the metadata log, the system_schema tables are only maintained for backwards compatibility (i.e. downgrades) and for drivers. > On 21 Feb 2025, at 00:29, Jeff Jirsa wrote: > > The schema has to be durable on disk for cold start > > You could put a virtua

Re: [VOTE] Release Apache Cassandra 4.0.17

+1 > On 6 Feb 2025, at 10:31, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 4.0.17 for release. > > sha1: 0354c915a9f8be6ab671af5ff93b8178e6f2e76f > Git: https://github.com/apache/cassandra/tree/4.0.17-tentative > Maven Artifacts: > https://repository.apache.org/content/repos

Re: [VOTE] Release Apache Cassandra 3.0.32

+1 > On 6 Feb 2025, at 07:00, Štefan Miklošovič wrote: > > Proposing the test build of Cassandra 3.0.32 for release. > > sha1: c559cf89624802fdb770e6ea962b45f102e48224 > Git: https://github.com/apache/cassandra/tree/3.0.32-tentative > Maven Artifacts: > https://repository.apache.org/content/re

Re: [VOTE] Release Apache Cassandra 3.11.19

+1 > On 6 Feb 2025, at 07:02, Štefan Miklošovič wrote: > > Proposing the test build of Cassandra 3.11.19 for release. > > sha1: ecbafb52750f1a2ab8523cbd7cc88c760dd3632b > Git: https://github.com/apache/cassandra/tree/3.11.19-tentative > Maven Artifacts: > https://repository.apache.org/content/

Re: 【DISCUSS】What is the current status of triggers in Cassandra ?

This is really a bug with the current implementation of CreateTriggerStatement and I've filed CASSANDRA-20287 to address it. Thanks, Sam > On 3 Feb 2025, at 21:06, Štefan Miklošovič wrote: > > Correct, snapshotting is the way to go here via nodetool cms snapshot > > But, you see? One more

Re: [DISCUSS] 5.1 should be 6.0

> initializing TCM? > > -Jeremiah > > On Dec 11, 2024 at 7:41:48 AM, Sam Tunnicliffe wrote: >> My point is that the upgrade to 5.1/6.0 isn't really complete until the CMS >> is initialised and this can't be done while running with SCM CASSANDRA_4 >>

Re: [DISCUSS] Deprecation of IEndpointSnitch (CASSANDRA-19488)

ne using a custom snitch implementation is able to check it out and help verify that. > On 31 Oct 2024, at 16:53, Sam Tunnicliffe wrote: > > Since CEP-21, the source of truth for topology info (a node's datacenter & > rack) is ClusterMetadata. Each node provides its dc/rack w

Re: [DISCUSS] 5.1 should be 6.0

od. Thanks, Sam > On 11 Dec 2024, at 13:29, Brandon Williams wrote: > > On Wed, Dec 11, 2024 at 7:22 AM Sam Tunnicliffe wrote: >> >> so running in any SCM mode for a prolonged period is not really viable. > > This is what many users want to do though, upgrade one

Re: [DISCUSS] 5.1 should be 6.0

arcus Eriksson wrote: >> >> Staying slightly off topic - we'd also have to run upgrade tests for all >> these upgrade combinations, including different storage compatibility mode >> settings, that is going to be very expensive. >> >> /Marcus &g

Re: [DISCUSS] 5.1 should be 6.0

Maybe this is not the right place to bring up practicalities, but the more upgrade paths we support the more complexity we take on. The ongoing issues mentioned in CASSANDRA-20118 are illustrative and the introduction of Storage Compatibility Mode adds further dimensions and operational complexi

[DISCUSS] Deprecation of IEndpointSnitch (CASSANDRA-19488)

Since CEP-21, the source of truth for topology info (a node's datacenter & rack) is ClusterMetadata. Each node provides its dc/rack when it registers itself with the cluster prior to joining and this information is effectively immutable (for now). This significantly reduces the scope of IEndpoin

Re: [VOTE] Release test-api 0.0.17

+1 > On 10 Sep 2024, at 15:34, Doug Rohrer wrote: > > Proposing the test build of in-jvm dtest API 0.0.17 for release > > Repository: > https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git > > Candidate SHA: > https://github.com/apache/cassandra-in-jvm-dtest-api/commit/85b538ca

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

Sorry to derail the discussion but just on a point of order, there is actually precedent for requiring a minimum patch level before a major upgrade. For instance, from NEWS.txt: Upgrade to 3.0 is supported from Cassandra 2.1 versions greater or equal to 2.1.9, or Cassandra 2.2 version

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

-1 I'm afraid we have found an issue with coordinator level latency metrics being artificially inflated for certain types of queries. Unfortunately this is a new regression, introduced by CASSANDRA-19534, so we shouldn't knowingly include it in the release. The good news is that only a subset

Re: Suggestions for CASSANDRA-18078

100% Option 1. Once it's out in GA release we're stuck with it so any short term disruption to adopters of pre-release versions is a trivial price to pay. > On 20 Jun 2024, at 17:46, Štefan Miklošovič wrote: > > List, > > we need your opinions about CASSANDRA-18078. > > That ticket is about

Re: [DISCUSS] CEP-42: Constraints Framework

We've been working on a draft CEP for migrating config from yaml to cluster metadata but have been a bit short of time recently, I'll try to get something out for discussion as soon as possible. A little delay isn't such a bad thing IMO, as we're still ironing out the kinks in the TCM implement

Re: [DISCUSS] New CQL command/option for listing roles with superuser privileges

>Regarding removal of inheriting superuser role needs broader discussion. There >must be a reason why it was done and removing this feature may impact existing >use cases. The reason behind the current behaviour is almost irrelevant, the fact is that this is the way that it works and has done s

Re: [Discuss] CASSANDRA-16999 introduction of a column in system.peers_v2

Late to the party I'm afraid, but I'd agree with Abe's proposal to deprecate the dual port approach given that CASSANDRA-10559 makes it pretty much redundant. Adding further yaml options like "default ssl/no ssl" feels like another nasty band-aid that we'll have to live with for the foreseeable

Re: [VOTE] Release Harry 0.0.2

+1 > On 29 Nov 2023, at 11:14, Alex Petrov wrote: > > Even though we would like to bring harry in-tree, this is not an immediate > priority. Meanwhile, we need to unblock RPM builds for trunk, which means no > custom jars. We will have at least one more Harry release with outstanding > featur

Re: Welcome Francisco Guerrero Hernandez as Cassandra Committer

Congrats Francisco! > On 28 Nov 2023, at 18:52, 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 members

Re: CEP-21 - Transactional cluster metadata merged to trunk

I ought to clarify, we did actually have green CI modulo 3 flaky tests on our internal CI system. I've attached the test artefacts to CASSANDRA-18330 now[1][2]: 2 of the 3 failures are upgrade dtests, with 1 other python dtest failure noted. None of these were reproducible in a dev setup, so we

Re: [DISCUSS] Harry in-tree

Definite +1 to bringing harry-core in tree. > On 24 Nov 2023, at 15:43, Alex Petrov wrote: > > Hi everyone, > > With TCM landed, there will be way more Harry tests in-tree: we are using it > for many coordination tests, and there's now a simulator test that uses > Harry. During development, H

Re: Push TCM (CEP-21) and Accord (CEP-15) to 5.1 (and cut an immediate 5.1-alpha1)

+1 from me too. Regarding Benedict's point, backwards incompatibility should be minimal; we modified snitch behaviour slightly, so that local snitch config only relates to the local node, all peer info is fetched from cluster metadata. There is also a minor change to the way failed bootstraps

Re: [DISCUSSION] Drift backwards compatibility from native protocol version growth to feature flags

There are some completely valid points here, but you are conflating internode messaging with native (aka client) protocol somewhat. Since native protocol V5 in C* 4.0, there is a degree of code re-use between the two, native protocol having adopted the framing model and resource allocation from

Re: [VOTE] CEP-8 Datastax Drivers Donation

+1 > On 13 Jun 2023, at 15:14, Jeremy Hanna wrote: > > Calling for a vote on CEP-8 [1]. > > To clarify the intent, as Benjamin said in the discussion thread [2], the > goal of this vote is simply to ensure that the community is in favor of the > donation. Nothing more. > The plan is to introd

Re: [VOTE] Release Apache Cassandra 4.1.2

+1 > On 25 May 2023, at 16:12, 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/repos

Re: [VOTE] Release Apache Cassandra 4.0.10

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

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

+1 > On 4 May 2023, at 17:46, Doug Rohrer wrote: > > Hello all, > > I’d like to put CEP-28 to a vote. > > Proposal: > > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-28%3A+Reading+and+Writing+Cassandra+Data+with+Spark+Bulk+Analytics > > Jira: > https://issues.apache.org/jira/brow

Re: Welcome our next PMC Chair Josh McKenzie

Congrats Josh and big thanks to Mick for everything this past year > On 23 Mar 2023, at 08:22, Mick Semb Wever wrote: > > It is time to pass the baton on, and on behalf of the Apache Cassandra > Project Management Committee (PMC) I would like to welcome and congratulate > our next PMC Chair Jo

Re: [DISCUSS] CEP-21 Ongoing Development

created a Jira epic (CASSANDRA-18330) as an umberella for CEP-21 and over the coming days we'll start to file seperate tickets for the upcoming/remaining work. [1] https://app.circleci.com/pipelines/github/beobal/cassandra/406/workflows/00cdb02e-4b3e-477a-b997-403121172249 > On 13 Feb 202

Re: [EXTERNAL] [DISCUSS] Next release date

Currently, we anticipate CEP-21 being in a mergeable state around late July/August. We're intending to push a feature branch with an implementation covering much of the core functionality to the ASF repo this week. Doing so will obviously help us get a better idea of the remaining work as we in

[DISCUSS] CEP-21 Ongoing Development

Hi, In the recent DISCUSS thread on merging incremental feature work[1] I mentioned that we've been preparing a code contribution to support CEP-21[2]. Today we have a branch based off trunk which supports a significant subset of the functionality described in the CEP. Whilst being mindful of t

Re: [VOTE] CEP-21 Transactional Cluster Metadata

The vote passes with 23 +1s (13 binding) and no negative votes. Thanks all, Sam > On 6 Feb 2023, at 16:15, Sam Tunnicliffe wrote: > > Hi everyone, > > I would like to start a vote on this CEP. > > Proposal: > https://cwiki.apache.org/confluence/display/CASSANDRA

[VOTE] CEP-21 Transactional Cluster Metadata

Hi everyone, I would like to start a vote on this CEP. Proposal: https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-21%3A+Transactional+Cluster+Metadata Discussion: https://lists.apache.org/thread/h25skwkbdztz9hj2pxtgh39rnjfzckk7 The vote will be open for 72 hours. A vote passes if there

Re: [DISCUSS] Merging incremental feature work

This is quite timely as we're just gearing up to begin pushing the work we've been doing on CEP-21 into the public domain. This CEP is a slightly different from others that have gone before in that it touches almost every area of the system. This presents a few implementation challenges, most

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

+1 > On 7 Dec 2022, at 21:40, Mick Semb Wever wrote: > > > Proposing the (second) test build of Cassandra 4.1.0 for release. > > sha1: f9e033f519c14596da4dc954875756a69aea4e78 > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.1.0-tentative > Maven Artifacts

Re: CEP-21 and complete cluster replacement.

ting StartJoin for all nodes, > while the range is locked, but block execution of `MidJoin` for any of the > nodes until StartJoin for all of them is executed and, similarly, throttling > FinishJoin before MidJoin is executed for all the nodes. In other words, I > think there

Re: CEP-21 and complete cluster replacement.

be performed in sequence. My > understanding is that you can't add more than one node at a time. What we > would like to do is do this is 3 steps: > Add A', B', C' to the cluster. > Wait for all 3 to be accepted and functioning. > Remove A, B, C from the cluster.

Re: CEP-21 and complete cluster replacement.

I'm not sure I 100% understand the question, but the things covered in CEP-21 won't enable you to as an operator to bootstrap all your new nodes without fully joining, then perform an atomic CAS to replace the existing members. CEP-21 alone also won't solve all cross-version streaming issues, wh

Re: Shall 4.2 become 5.0 ?

> do we want to drop support in trunk for upgrading from 3.x ? This is a bit premature as it hasn't even gone to a vote yet, but if accepted, CEP-21 might make this something we want to do. https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-21:+Transactional+Cluster+Metadata#CEP21:Transac

Re: [DISCUSS] CEP-21: Transactional Cluster Metadata

pt of "token" ownership in CMS; all CMS nodes own > an entire range from MIN to MAX token. This means that during bootstrap, we > do not have to split ranges, or have some nodes "lose" a part of the ring... > > This sounds like an implementation of everywhere replicati

Re: [DISCUSS] CEP-21: Transactional Cluster Metadata

> On 5 Sep 2022, at 22:02, Henrik Ingo wrote: > > Mostly I just wanted to ack that at least someone read the doc (somewhat > superficially sure, but some parts with thought...) > Thanks, it's a lot to digest, so we appreciate that people are working through it. > One pre-feature that we wo

Re: [DISCUSS] CEP-21: Transactional Cluster Metadata

Good catch, I'll update the doc. Thanks, Sam > On 24 Aug 2022, at 10:24, Claude Warren, Jr via dev > wrote: > > Should > > (**) It may seem counterintuitive, that A is being written to even after > we've stopped reading from it. This is done in order to guarantee that by the > time we sto

Re: [DISCUSS] CEP-21: Transactional Cluster Metadata

improving modularity in Cassandra and one of >> the ideas I'm discussing is pluggably (?) replacing gossip with something(s) >> that allow us to externalize some of the complexity of maintaining >> consistency. I need to digest the proposal you've made, but I don&#x

Re: [DISCUSS] CEP-21: Transactional Cluster Metadata

h something(s) > that allow us to externalize some of the complexity of maintaining > consistency. I need to digest the proposal you've made, but I don't see the > two ideas being at odds on my first read. > > Cheers, > > Derek > > On Mon, Aug 22, 2022

[DISCUSS] CEP-21: Transactional Cluster Metadata

Hi, I'd like to open discussion about this CEP: https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-21%3A+Transactional+Cluster+Metadata Cluster metadata in Cassandra comprises a number

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

+1 > On 7 May 2022, at 07:39, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 4.0.4 for release. > This is from the (take4) test artifact. > > sha1: 052125f2c6ed308f1473355dfe43470f0da44364 > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0

Re: [VOTE] Release Apache Cassandra 3.11.13

+1 > On 7 May 2022, at 07:38, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 3.11.13 for release. > > sha1: 836ab2802521a685efe84382cb48db56caf4478d > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.13-tentative > Maven Artifacts: > http

Re: [VOTE] Release Apache Cassandra 3.0.27

+1 > On 7 May 2022, at 07:37, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 3.0.27 for release. > > sha1: 205366131484967a3a8a749f1d1d841c952127e8 > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.27-tentative > Maven Artifacts: > https:

Re: Code freeze starts 1st May. Anything to be addressed?

sers > which normally know what they're doing. We have tons of potentially dangerous > knobs and I don't get why this particular one is any different. > > Em qua., 27 de abr. de 2022 às 14:05, Sam Tunnicliffe <mailto:s...@beobal.com>> escreveu: > CASSANDR

Re: Code freeze starts 1st May. Anything to be addressed?

CASSANDRA-14582 added support for users to supply an arbitrary value for HOST_ID when booting a new node. IMO it's a pretty bad and potentially dangerous idea for the unique identifier to be settable in this way. Hint delivery is already routed by host id and there have been several JIRAs which

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

+1 > On 16 Feb 2022, at 08:57, Branimir Lambov wrote: > > Hi everyone, > > I'd like to propose CEP-19 for approval. > > Proposal: > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-19%3A+Trie+memtable+implementation > >

Re: [VOTE] Formalizing our CI process

+1 with/without amendment > On 13 Jan 2022, at 05:26, Berenguer Blasi wrote: > > Oh I completely agree with you. I was just trying to explain that > getting to 2/3 failures is a realistic target. > > +1 also on the amendment. > > On 12/1/22 17:39, Joseph Lynch wrote: >> On Wed, Jan 12, 2022 at

Re: [VOTE] CEP-17: SSTable format API

+1 > On 15 Nov 2021, at 19:42, Branimir Lambov wrote: > > Hi everyone, > > I would like to start a vote on this CEP. > > Proposal: > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-17%3A+SSTable+format+API > > Discussion: > https://lists.apache.org/thread.html/r636bebcab4e678dbee042

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

1. +1 2. +1 3. +1 Thanks, Sam > On 14 Oct 2021, at 17:31, bened...@apache.org wrote: > > Hi everyone, > > I would like to start a vote on this CEP, split into three sub-decisions, as > discussion has been circular for some time. > > 1. Do you support adopting this CEP? > 2. Do you support the

[DISCUSS] CASSANDRA-16922 CEP-10: Major Prerequisites (Phase 1)

This umbrella issue covers the major structural refactorings to enable the higher level pieces of CEP-10. The current proposal is to post separate patches for each JIRA to lessen the review burden as much as possible. However, the patches are incremental, so there is a dependency from one to the

[RELEASE] Apache Cassandra 4.0.1 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 4.0.1. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of sourc

Re: [VOTE] Release Apache Cassandra 4.0.1

This vote has passed with 16 +1 votes (10 binding) and no -1 votes. > On 1 Sep 2021, at 12:54, Sam Tunnicliffe wrote: > > Proposing the test build of Cassandra 4.0.1 for release. > > sha1: 6709111ed007a54b3e42884853f89cabd38e4316 > Git: > https://gitbox.apache.org/repos/

[VOTE] Release Apache Cassandra 4.0.1

Proposing the test build of Cassandra 4.0.1 for release. sha1: 6709111ed007a54b3e42884853f89cabd38e4316 Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.1-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1247/org/

[ANNOUNCE] Apache Cassandra 4.0.1 test artifact available

The test build of Cassandra 4.0.1 is available. sha1: 6709111ed007a54b3e42884853f89cabd38e4316 Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.1-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1247/org/apache/ca

Re: [VOTE] CEP-14: Paxos Improvements

+1 > On 27 Aug 2021, at 20:48, bened...@apache.org wrote: > > Hi everyone, I’m proposing this CEP for approval. > > Proposal: > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-14%3A+Paxos+Improvements > Discussion: > https://lists.apache.org/thread.html/r1af3da2d875ef93479e3874072ee6

Potential issues during 4.0 upgrade

Hi all, I just opened a JIRA which is relevant to those running large clusters (around the 400 node range) and who have plans to upgrade to 4.0 upgrades soon. https://issues.apache.org/jira/browse/CASSANDRA-16877 The issue is that in la

Re: [VOTE] CEP-11: Pluggable memtable implementations

+1 > On 19 Aug 2021, at 17:10, Branimir Lambov wrote: > > Hello everyone, > > I am proposing the CEP-11 (Pluggable memtable implementations) for adoption > > Discussion thread: > https://lists.apache.org/thread.html/rb5e950f882196764744c31bc3c13dfbf0603cb9f8bc2f6cfb976d285%40%3Cdev.cassandra.a

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

+1 > On 26 Jul 2021, at 11:51, bened...@apache.org wrote: > > Proposing the CEP-10 (Cluster and Code Simulations) for adoption > > Proposal: > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-10%3A+Cluster+and+Code+Simulations > Discussion: > https://lists.apache.org/thread.html/rc908

Re: [VOTE] Release Apache Cassandra 3.0.25

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

Re: [VOTE] Release Apache Cassandra 3.11.11

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

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

+1 > On 22 Jul 2021, at 23:40, Brandon Williams wrote: > > I am proposing the test build of Cassandra 4.0.0 for release. > > sha1: 902b4d31772eaa84f05ffdc1e4f4b7a66d5b17e6 > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.0-tentative > Maven Artifacts: > h

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

+1 > On 13 Jul 2021, at 23:13, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 4.0.0 for release. > > sha1: 924bf92fab1820942137138c779004acaf834187 > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.0-tentative > Maven Artifacts: > https:/

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

Spoiler alert: I am pretty familiar with the proposal and the off-list work that has been done toward it. From my perspective, I have no qualms about putting this CEP up for a vote. Having seen the potential (and to some degree, realised) benefit of this proposal, I am convinced of its value.

Re: [VOTE] Release Apache Cassandra 4.0-rc2

+1 > On 29 Jun 2021, at 05:30, Jeff Jirsa wrote: > > +1 > > >> On Jun 28, 2021, at 9:00 PM, Jeremy Hanna wrote: >> >> +1 (nb) nice to see all of the fixes and the use of newer TLS by default >> and obfuscation of passwords in the audit log for the 4.0 release. >> >>> On Jun 29, 2021, at 6

Re: Additions to Cassandra ecosystem page?

+1 > On 23 Jun 2021, at 22:31, Jeff Jirsa wrote: > > This would be my preference. > > > On Wed, Jun 23, 2021 at 2:22 PM Ben Bromhead wrote: > >> I'm also comfortable with a strict approach where we just list actual >> Apache Cassandra offerings, that also provides good solid clarity to users

Re: Obfuscation of passwords in audit loging, in or not in 4.0?

> On 4 Jun 2021, at 03:44, Jonathan Koppenhofer wrote: > > +1 to this being a serious bug. As a large user, if we used internal > passwords, this would completely prevent me from using Cassandra native > audit log capabilities. Disabling DCL is not a great option, as DCL is > probably the most

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

+1 > On 23 Apr 2021, at 04:19, Jasonstack Zhao Yang > wrote: > > +1 > > On Fri, 23 Apr 2021 at 08:16, Nate McCall wrote: > >> +1 >> >> >> On Thu, Apr 22, 2021 at 6:59 AM Mick Semb Wever wrote: >> >>> Proposing the test build of Cassandra 4.0-rc1 for release. >>> >>> sha1: 3282f5ecf187ec

Re: [DISCUSS] Releases after 4.0

+1 > On 29 Mar 2021, at 15:41, Joseph Lynch wrote: > > I am slightly concerned about removing support for critical bug fixes > in 3.0 on a short time-frame (<1 year). I know of at least a few major > installations, including ours, who are just now able to finish > upgrades to 3.0 in production d

Re: Download source release / binary files in source release

I agree with Jeff. The inclusion of binary dependencies to assist developers building from a source release doesn't seem like a deal breaker to me personally as long as these are purely a convenience and not a requirement. That said, the stance of the ASF as recorded in the incubator thread is

Re: [DISCUSS] Releases after 4.0

+1 to both the yearly cadence and the periodic publishing of bleeding edge snapshots. > On 5 Feb 2021, at 16:14, Benedict Elliott Smith wrote: > > +1 > > +1 also to mixing this with an experiment on regular "releasable" (without > API stability) snapshots from trunk. > > On 05/02/2021, 16:0

Re: [VOTE] Release Apache Cassandra 3.0.24

+1 > On 29 Jan 2021, at 13:21, Oleksandr Petrov wrote: > >> Proposing the test build of Cassandra 4.0-beta4 for release. > > Correction: test build of 3.0.24. The rest looks right. > > On Fri, Jan 29, 2021 at 1:48 PM Oleksandr Petrov > wrote: > >> Proposing the test build of Cassandra 4.0-be

Re: [VOTE] Release Apache Cassandra 3.11.10

+1 > On 29 Jan 2021, at 12:50, Oleksandr Petrov wrote: > > Proposing the test build of Cassandra 3.11.10 for release. > > sha1: 181a4969290f1c756089b2993a638fe403bc1314 > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.10-tentative > Maven Artifacts: > htt

Re: Which fix version should be used for the Quality Testing tickets

> On 17 Dec 2020, at 10:54, Michael Semb Wever wrote: > > >> I propose to: >> >> - update the documentation to clarify the meaning of the fix version as >> 'The version in which the item must be fixed' (e.g 4.0-beta if the ticket >> must be fixed in a beta release) >> - create a 4.0-

Re: [DISCUSS] Bringing protocol v5 out of beta and dropping support from 3.11.x

> What's the verdict now for CASSANDRA-14973 ? My aim is to have a C* patch and PRs for the python and java drivers this week, but really there's nothing to block cutting a new C* beta now (or whenever we're ready). > On 15 Dec 2020, at 15:39, Mick Semb Wever wrote: > >> >> To use a beta fla

Re: [DISCUSS] Bringing protocol v5 out of beta and dropping support from 3.11.x

.atlassian.net/browse/PYTHON-1232 [3] https://datastax-oss.atlassian.net/browse/JAVA-2704 [4] https://datastax-oss.atlassian.net/browse/JAVA-2705 > On 9 Dec 2020, at 11:02, Sam Tunnicliffe wrote: > > > >> On 9 Dec 2020, at 02:41, Sumanth Pasupuleti >> wrote: >> >

Re: [DISCUSS] Bringing protocol v5 out of beta and dropping support from 3.11.x

> On 9 Dec 2020, at 02:41, Sumanth Pasupuleti > wrote: > > +1 to moving v5-beta changes in trunk to new protocol v6. > > Regarding 3.11 and v5, I suppose we could say, v5 could never get matured > beyond beta, but not sure if it would be confusing to see v6 while v5 is > still in beta (curio

Re: [DISCUSS] Bringing protocol v5 out of beta and dropping support from 3.11.x

void this > issue? > > On 08/12/2020, 10:53, "Sam Tunnicliffe" wrote: > >CASSANDRA-15299 has revised the wire format of CQL native protocol to add > a framing layer around the existing CQL messages. This is targetted at > protocol v5, which is (still) cu

[DISCUSS] Bringing protocol v5 out of beta and dropping support from 3.11.x

CASSANDRA-15299 has revised the wire format of CQL native protocol to add a framing layer around the existing CQL messages. This is targetted at protocol v5, which is (still) currently in beta. There's a small problem with this though; while v5-beta is supported in Cassandra 3.11.x and 4.0.0, th

Changes to JMX metric names in 4.0 beta

In CASSANDRA-15299, native protocol V5 is being reworked to incorporate the framing format of internode messaging. This is mildly controversial given we're well into the beta now and there has been discussion[1] about this previously, so I won't rehash that here but I did want to call out anothe

Re: Cassandra Contributor Meeting to focus on outstanding 4.0 issues

> On 29 Sep 2020, at 09:50, Mick Semb Wever wrote: > >> Regarding the proposed agenda of going through the unassigned issues to >> improve visibility on what needs to be done to ship 4.0 GA I think this is >> a great start but only covers part of the problem. >> >> I think we have 3 outstandi

Re: [VOTE] Release dtest-api 0.0.5

+1 > On 25 Sep 2020, at 15:45, Oleksandr Petrov wrote: > > Proposing the test build of in-jvm dtest API 0.0.5 for release. > > Repository: > https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git;a=shortlog;h=refs/tags/0.0.5 > Candidate SHA: > https://github.com/apache/cassandra-i

Re: [VOTE] Accept the Harry donation

+1 > On 16 Sep 2020, at 11:07, Benjamin Lerer wrote: > > +1 > > On Wed, Sep 16, 2020 at 12:00 PM Mick Semb Wever wrote: > >>> Please cast your votes: >>> [ ] +1 Accept the contribution into Cassandra >>> [ ] -1 Do not >>> >> >> >> +1 >> --

Re: [DISCUSS] Change style guide to recommend use of @Override

+1 > On 2 Sep 2020, at 09:03, Benjamin Lerer wrote: > > +1 > > > > On Wed, Sep 2, 2020 at 5:36 AM Berenguer Blasi > wrote: > >> +1 >> >> On 2/9/20 5:09, Joshua McKenzie wrote: >>> +1 >>> >>> On Tue, Sep 1, 2020 at 6:26 PM Jordan West wrote: >>> +1 On Tue, Sep 1, 2020 at

CVE-2020-13946 Apache Cassandra RMI Rebind Vulnerability

CVE-2020-13946 Apache Cassandra RMI Rebind Vulnerability Versions Affected: All versions prior to: 2.1.22, 2.2.18, 3.0.22, 3.11.8 and 4.0-beta2 Description: It is possible for a local attacker without access to the Apache Cassandra process or configuration files to manipulate the RMI registry to

Re: [VOTE] Release Apache Cassandra 2.1.22

+1 > On 28 Aug 2020, at 16:42, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 2.1.22 for release. > > sha1: 94e9149c22f6a7772c0015e1b1ef2e2961155c0a > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.22-tentative > Maven Artifacts: > https:

Re: [VOTE] Release Apache Cassandra 3.11.8

+1 > On 28 Aug 2020, at 14:37, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 3.11.8 for release. > > sha1: 8b29b698630960a0ebb2c695cc5b21dee4686d09 > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.8-tentative > Maven Artifacts: > https:

Re: [VOTE] Release Apache Cassandra 2.2.18

+1 > On 28 Aug 2020, at 13:44, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 2.2.18 for release. > > sha1: d4938cf4e488a9ef3ac48164a3e946f16255d721 > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.18-tentative > Maven Artifacts: > https:

Re: [VOTE] Release Apache Cassandra 3.0.22

+1 > On 28 Aug 2020, at 14:09, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 3.0.22 for release. > > sha1: 45331bb612dc7847efece7e26cdd0b376bd11249 > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.22-tentative > Maven Artifacts: > https:

Re: [VOTE] Release Apache Cassandra 4.0-beta2

+1 > On 28 Aug 2020, at 15:18, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 4.0-beta2 for release. > > sha1: 56eadf2004399a80f0733041cacf03839832249a > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-beta2-tentative > Maven Artifacts: >

Re: [VOTE] Release Apache Cassandra 2.2.17

+1 > On 24 Jul 2020, at 12:07, Mick Semb Wever wrote: > >> Proposing the test build of Cassandra 2.2.17 for release. >> >> sha1: cd006d275aa9b6e937c6ebd036d4d27c4ed18dbe > > > +1 (binding) > > > Test Results: > https://ci-cassandra.apache.org/job/Cassandra-2.2/28/testReport/ > > > Check

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

+1 > On 22 Jun 2020, at 08:54, Sylvain Lebresne wrote: > > +1 > -- > Sylvain > > > On Mon, Jun 22, 2020 at 9:48 AM Benjamin Lerer > wrote: > >> +1 >> >> On Mon, Jun 22, 2020 at 8:54 AM Marcus Eriksson >> wrote: >> >>> +1 >>> >>> >>> On 22 June 2020 at 08:37:39, Mick Semb Wever (m...@apa

Re: [VOTE] Project governance wiki doc

+1 (binding) > On 17 Jun 2020, at 09:11, Jorge Bay Gondra wrote: > > +1 nb > > On Wed, Jun 17, 2020 at 7:41 AM Mick Semb Wever wrote: > >> +1 (binding) >> >> On Tue, 16 Jun 2020 at 18:19, Joshua McKenzie >> wrote: >> >>> Added unratified draft to the wiki here: >>> >>> >> https://cwiki.a

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

> On 17 Jun 2020, at 09:36, Benedict Elliott Smith wrote: > > If these tickets are the only blockers I agree with Scott's assessment. We > could even disable the v5 protocol if we're keen to get it out of the door > today, and only enable it once 15299 lands. I don't personally think the >

  1   2   >