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

> I see that implementing a Replicated Log > > needs significant changes, particularly about how two phases of Paxos are > implemented over the entire log. So will it be better to use

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

Hi Sam, Great to see this CEP. I have been documenting a few common 'patterns of distributed systems, and have documented a pattern called 'consistent core ' referring to the source code of various systems whic

Re: [DISCUSS] LWT UPDATE semantics with + and - when null

The approach 2) is the one used by CQL operators. SELECT v + 1 FROM t WHERE pk = 1; Will return null if the row exists but the v is null. Le mer. 31 août 2022 à 18:05, David Capwell a écrit : > Sounds like matching SQL is the current favor, the current patch matches > this so will leave this th

Re: [DISCUSS] Removing support for java 8

+1 to remove from trunk > On Aug 30, 2022, at 7:54 PM, Caleb Rackliffe wrote: > > +1 on removing 8 for trunk > > On Tue, Aug 30, 2022 at 2:42 PM Jon Haddad > wrote: > +1 to removal of 8 in trunk. > > On 2022/08/29 20:09:55 Blake Eggleston wrote: > > Hi all,

Re: [DISCUSS] LWT UPDATE semantics with + and - when null

Sounds like matching SQL is the current favor, the current patch matches this so will leave this thread open a while longer before trying to merge the patch. > On Aug 31, 2022, at 5:07 AM, Ekaterina Dimitrova > wrote: > > I am also +1 to match SQL, option 2. Also, I like Andres’ suggestion >

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

Update: Some sections have been flagged by the PMC for further revision. Author, Alex Sorokoumov will review on 2 September. Revising publication date to 8 September. On Fri, Aug 26, 2022 at 11:15 PM Alexander Sorokoumov < aleksandr.sorokou...@gmail.com> wrote: > Hey Rhaul, > > Thanks for the fe

Re: [Marketing] For Review: Performance Benchmarking of Apache Cassandra in the Cloud

Update: This blog is on hold for additional discussion and amends. Work is also required to supply filtered links to certain benchmarks referenced which won't be complete until 2 September. For that reason, revising the suggested publication date to 6 September, but as it's a public holiday in the

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

> > Is there enough support here for VIEWS to be the implementation strategy > for displaying masking functions? I'm not sure that views should be "the" strategy for masking functions. We have multiple approaches here: 1) CQL functions only. Users can decide to use the masking functions on their

Re: [DISCUSS] LWT UPDATE semantics with + and - when null

I am also +1 to match SQL, option 2. Also, I like Andres’ suggestion On Wed, 31 Aug 2022 at 7:15, Claude Warren via dev wrote: > I like this approach. However, in light of some of the discussions on > view and the like perhaps the function is (column value as returned by > select ) + 42 > > So

Re: [DISCUSS] LWT UPDATE semantics with + and - when null

I like this approach.  However, in light of some of the discussions on view and the like perhaps the function is  (column value as returned by select ) + 42 So a null counter column becomes 0 before the update calculation is applied. Then any null can be considered null unless addressed by IfN

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

Is there enough support here for VIEWS to be the implementation strategy for displaying masking functions? It seems to me the view would have to store the query and apply a where clause to it, so the same PK would be in play. It has data leaking properties. It has more use cases as it can be

Re: [DISCUSS] LWT UPDATE semantics with + and - when null

I think I'd prefer 2), the SQL behaviour. We could also get the convenience of 3) by adding CQL functions such as "ifNull(column, default)" or "zeroIfNull(column)", as it's done by other dbs. So we could do things like "UPDATE ... SET name = zeroIfNull(name) + 42". On Wed, 31 Aug 2022 at 04:54, Ca