Re: [VOTE] Release Apache Cassandra 4.0.6

+1 nb -Original Message- From: Brandon Williams mailto:brandon%20williams%20%3cdri...@gmail.com%3e>> Reply-To: dev@cassandra.apache.org To: dev mailto:dev%20%3c...@cassandra.apache.org%3e>> Subject: Re: [VOTE] Release Apache Cassandra 4.0.6 Date: Mon, 22 A

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

“ The proposed mechanism for dealing with both of these failure types is to enable a manual operator override mode. This would allow operators to inject metadata changes (potentially overriding the complete metadata state) directly on any and all nodes in a cluster. At the most extreme end of th

[Marketing] For Review: Learn How CommitLog Works in Apache Cassandra

Opening up Alex Sorokoumov's guide 'Learn How CommitLog Works in Apache Cassandra' for a 72-hr community review by lazy consensus. Please add any amends and suggestions in the comments: https://docs.google.com/document/d/1cyOi-IeU_I9GBkpQbJS6IIrmemAesEqvzLb-eeFs_rM/edit# Thanks! -- Chris Thorn

Re: [VOTE] Release Apache Cassandra 4.0.6

+1 On Sun, Aug 21, 2022 at 7:44 AM Mick Semb Wever wrote: > > > Proposing the test build of Cassandra 4.0.6 for release. > > sha1: eb2375718483f4c360810127ae457f2a26ccce67 > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.6-tentative > Maven Artifacts: > ht

Re: [VOTE] Release Apache Cassandra 4.0.6

+1 (nb) On 2022/08/22 20:08:11 Sylwester Lachiewicz wrote: > +1 nb > > pon., 22 sie 2022 o 21:28 C. Scott Andreas napisał(a): > > > > +1nb > > > > On 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 > >>

Re: [VOTE] Release Apache Cassandra 4.0.6

+1 nb pon., 22 sie 2022 o 21:28 C. Scott Andreas napisał(a): > > +1nb > > On 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

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] CEP-20: Dynamic Data Masking

One thought: The way the CEP is currently written, it is only possible to mask a column one way. You can only define one masking function for a column, and since you use the original column name, you could only return one version of it in the result set, even if you had a way to define several func

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

This looks really interesting; thanks for putting this together! Just so I'm clear on CEP nomenclature, having external management of metadata as a non-goal doesn't preclude some future use, correct? Coincidentally, I'm working on my ApacheCon talk on improving modularity in Cassandra and one of th

Re: CEP-15 multi key transaction syntax

I wasn't referring to specific syntax but to the concept. If a SQL dialect (or better, the standard) has a way to select data into a variable, let's adopt it. If such syntax doesn't exist, LET (a, b, c) = (SELECT x, y, z FROM tab) is my preference. On 8/22/22 19:13, Patrick McFadin wrote: T

Re: CEP-15 multi key transaction syntax

The replies got trashed pretty badly in the responses. When you say: "Agree it's better to reuse existing syntax than invent new syntax." Which syntax are you referring to? Patrick On Mon, Aug 22, 2022 at 1:36 AM Avi Kivity via dev wrote: > Agree it's better to reuse existing syntax than inve

Re: [VOTE] Release Apache Cassandra 4.0.6

> > > 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. > > +1 Checked - signing correct - checksums are correct - source

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

I just want to say I’m really excited about this work. It’s one of the last remaining major inadequacies of the project that makes it hard for people to deploy, and hard for us to develop. Can’t wait for it to be fixed. > On 22 Aug 2022, at 13:45, Sam Tunnicliffe wrote: > Hi, > > I'd like to

[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: [DISCUSS] CEP-20: Dynamic Data Masking

> > Isn't there an assumption here that encryption can not be used? Would we > not be better served to build in an encryption strategy that keeps the data > encrypted until the user shows permissions to decrypt, like the unmask > property? An encryption strategy that can work within the Cassandra

Re: [DISCUSS] CEP-20: Dynamic Data Masking

> > Maybe a small improvement is the redacted value could be of the form > `XXX1...1000` meaning XXX followed by a rand number from 1 to 1000: XXX54, > XXX998, XXX456,... Some randomness would prevent some apps flattening all > rows to a single XXX'ed one, giving a more realistic redacted data > di

Re: [VOTE] Release Apache Cassandra 4.0.6

> Maven Artifacts: > https://repository.apache.org/content/repositories/orgapachecassandra-/org/apache/cassandra/cassandra-all/4.0.6/ > Correction. Maven Artifacts are at: https://repository.apache.org/content/repositories/orgapachecassandra-1275/org/apache/cassandra/cassandra-all/4.0.6/

Re: CEP-15 multi key transaction syntax

Agree it's better to reuse existing syntax than invent new syntax. On 8/21/22 16:52, Konstantin Osipov wrote: * Avi Kivity via dev [22/08/14 15:59]: MySQL supports SELECT INTO FROM ... WHERE ... PostgreSQL supports pretty much the same syntax. Maybe instead of LET use the ANSI/MySQL/Postgr