[RESULT][VOTE] Release Apache Cassandra 4.0.6

The vote passes with elleven +1's (four binding) and no vetoes. On Tue, 23 Aug 2022 at 14:56, Berenguer Blasi wrote: > +1 > On 23/8/22 14:50, Ekaterina Dimitrova wrote: > > > +1(nb) > On Tue, 23 Aug 2022 at 8:49, Josh McKenzie wrote: > >> +1 >> >> On Tue, Aug 23, 2022, at 6:47 AM, Benjamin L

[RELEASE] Apache Cassandra 4.0.6 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 4.0.6. 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 source an

Invitation to take the 2022 ASF Community Survey

Hello everyone, The 2022 ASF Community Survey is looking to gather scientific data that allows us to understand our community better, both in its demographic composition, and also in collaboration styles and preferences. We want to find areas where we can continue to do great work, and others whe

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

I have modified the proposal adding a new SELECT_MASKED permission. Using masked columns on WHERE/IF clauses would require having SELECT and either UNMASK or SELECT_MASKED permissions. Seeing the unmasked values in the query results would always require both SELECT and UNMASK. This way we can have

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

To make sure I understand, if I wanted to use a masked column for a conditional update, you're saying we would need SELECT_MASKED to use it in the IF clause? I worry that this proposal is increasing in complexity; I would actually be OK starting with something smaller in scope. Perhaps just providi

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

Note that conditional updates return true or false to notify whether the update has happened or not. That can also be exploited to infer the masked data. Indeed, at the moment they also require SELECT permissions. The masking functions can always be used on their own, as any other CQL function and

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

I’m inclined to agree that this seems a more straightforward approach that makes fewer implied promises. Perhaps we could deliver simple views backed by virtual tables, and model our approach on that of Postgres, MySQL et al? Views in C* would be very simple, just offering a subset of fields wi

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

> > Perhaps we could deliver simple views backed by virtual tables, and model > our approach on that of Postgres, MySQL et al? The approach of PostgresSQL allows attaching masking functions to columns and users with command

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

Yes, I was thinking that simple projection views (essentially a SELECT statement with application of transform functions) would complement masking functions, and from the discussion it sounds like this is basically what some of the other databases do. Projection views seem like they would be useful