Re: [Discuss] CEP-24 Password validation and generation

Stefan, thanks for moving this CEP forward. This CEP brings a lot of value to Cassandra without needing to wait for TCM. I can see how a misconfigured node can be problematic, but the issue is not something introduced in this CEP, and it affects many other features in Cassandra. I think it needs to

Re: [DISCUSS] CEP-42: Constraints Framework

Hi Štephan I'll address the different points: 1) An example (possibly a stretch) of use case for != constraint would be: Let's say you have a table in which you want to record a movement, from position p1 to position p2. You may want to check that those two are different to make sure there is ac

[DISCUSS] LWT conditions behavior on collections is inconsistent (CASSANDRA-19637)

Hi everybody, I wanted to raise attention to CASSANDRA-19637 that I already mentioned in the "[DISCUSS] NULL handling and the unfrozen collection issue" thread. The patch attempts to fix some inconsistencies in the way LWT conditions work wi

Re: [DISCUSS] CEP-42: Constraints Framework

Hi Bernardo, 1) Could you elaborate on these two constraints? == and != ? What is the use case? Why would I want to have data in a database stored in some column which would need to be _same as my constraint_ and which _could not_ be same as my constraint? Can you give me at least one example of

Re: [Discuss] CEP-24 Password validation and generation

Agree on your point - password rotation logic is business specific and database doesn’t have to worry about that. > On Jun 7, 2024, at 6:58 PM, Štefan Miklošovič > wrote: > > Hi Shailaja, > > thanks for taking a look at this. > > That was indeed just an example we can change. It was more a