Re: [VOTE][IP CLEARANCE] GoCQL driver

+1 On Wed, 26 Jun 2024 at 6:14, Jon Haddad wrote: > +1. > > On Wed, Jun 26, 2024 at 1:50 AM J. D. Jordan > wrote: > >> +1 nb. Good to see this heavily used driver get continued development in >> the project. >> >> > On Jun 25, 2024, at 5:29 PM, Michael Shuler >> wrote: >> > >> > +1 >> > >> >

Re: [VOTE] Release Apache Cassandra 5.0-rc1

+1 > On Jun 25, 2024, at 5:04 AM, Mick Semb Wever wrote: > >  > > Proposing the test build of Cassandra 5.0-rc1 for release. > > sha1: b43f0b2e9f4cb5105764ef9cf4ece404a740539a > Git: https://github.com/apache/cassandra/tree/5.0-rc1-tentative > Maven Artifacts: > https://repository.apache.o

Re: [VOTE][IP CLEARANCE] GoCQL driver

+1. On Wed, Jun 26, 2024 at 1:50 AM J. D. Jordan wrote: > +1 nb. Good to see this heavily used driver get continued development in > the project. > > > On Jun 25, 2024, at 5:29 PM, Michael Shuler > wrote: > > > > +1 > > > > Kind regards, > > Michael > > > >> On 6/25/24 12:29, Mick Semb Wever w

Re: [VOTE] Release Apache Cassandra 5.0-rc1

5.0 is a massive milestone. A huge thank you to everyone that's invested their time into the release. I've done a lot of testing, benchmarking, and tire kicking and it's truly mind blowing how much has gone into 5.0 and how great it is for the community. I am a bit concerned that CASSANDRA-19668

Re: [VOTE][IP CLEARANCE] GoCQL driver

+1 nb. Good to see this heavily used driver get continued development in the project. > On Jun 25, 2024, at 5:29 PM, Michael Shuler wrote: > > +1 > > Kind regards, > Michael > >> On 6/25/24 12:29, Mick Semb Wever wrote: >> Please vote on the acceptance of the GoCQL driver and its IP Clearanc

Re: [DISCUSS] CEP-42: Constraints Framework

> > - Alter and Drop constraints are as follows > ALTER CONSTRAINT [name] CHECK new_condition DROP CONSTRAINT [name] > I think you mean the following syntax to modify existing constraints, since constraints are part of the table definition. ALTER TABLE [keyspace_name.]table_name ALTER CONSTRAINT [

Re: [VOTE][IP CLEARANCE] GoCQL driver

+1 Kind regards, Michael On 6/25/24 12:29, Mick Semb Wever wrote: Please vote on the acceptance of the GoCQL driver and its IP Clearance: https://incubator.apache.org/ip-clearance/cassandra-gocql-driver.html All consent

Re: [VOTE][IP CLEARANCE] GoCQL driver

+1; appreciate you driving this Mick and everyone rallying. On Tue, Jun 25, 2024, at 1:32 PM, Mick Semb Wever wrote: > . > >> The vote will be open for 72 hours (or longer). Votes by PMC members are >> considered binding. A vote passes if there are at least three binding +1s >> and no -1's.

Re: [DISCUSS] CEP-42: Constraints Framework

I wonder how often it is that users will apply the constraints on tables with data while they know their data is probably not compliant with the constraint configuration. I humbly think that people are aware of this in advance and what usually happens is that there is some kind of a job which conso

Re: [DISCUSS] CEP-42: Constraints Framework

Abe, that's a good point. We need to call out distinct use-cases here. When a fresh cluster is set up with constraints we don't have any issues because the data written and read back is going to be compliant to the constraint(s). For existing data in a cluster where new constraints are applied or e

Re: [VOTE][IP CLEARANCE] GoCQL driver

+1 Kind Regards, Brandon On Tue, Jun 25, 2024 at 12:30 PM Mick Semb Wever wrote: > > > > Please vote on the acceptance of the GoCQL driver and its IP Clearance: > https://incubator.apache.org/ip-clearance/cassandra-gocql-driver.html > > All consent from original authors of the donation, and trac

Re: [DISCUSS] CEP-42: Constraints Framework

On the Analytics side, as long as the CQLSSTableWriter understands and enforces the constraints (which it should be able to , given we provide the table schema) we should be good to go. We should try hard to avoid scanning the data on import, as the Analytics library does a bunch of things to pu

Re: [DISCUSS] CEP-42: Constraints Framework

If we're going to introduce a feature that looks like SQL constraints, we should make sure it's "reasonably" compliant. In particular, we should avoid situations where a user creates a constraint, writes some data, then reads data that violates that constraint, unless they've expressed that viol

Re: [VOTE][IP CLEARANCE] GoCQL driver

+1 Thank you Mick and everyone else involved in this effort. On Tue, Jun 25, 2024 at 11:12 AM Jeff Jirsa wrote: > +1 > > Thank you for being explicit about which authors of gocql have signed the > ICLA > > > Where The Gocql Authors for copyright purposes are below. Those marked > with > > aster

Re: [VOTE][IP CLEARANCE] GoCQL driver

+1 Thank you for being explicit about which authors of gocql have signed the ICLA > Where The Gocql Authors for copyright purposes are below. Those marked with > asterisk have agreed to donate (copyright assign) their contributions to the > Apache Software Foundation, signing CLAs when appropriat

Re: [DISCUSS] CEP-42: Constraints Framework

On Tue, Jun 25, 2024 at 10:59 AM Josh McKenzie wrote: > > My intuition is the vote got called a *smidge* early but that things are > very much moving in the right direction and are very close. > Agreed and the vote thread got us more feedback which is valuable :)

Re: [DISCUSS] CEP-42: Constraints Framework

> I was referring to the name guardrail, using the same infra as guardrails Curious if there's a subtle distinction implicit in this (or just in my brain...). A guardrail is something one person puts in place for someone else - in our case operators to users. Constraints are something inherent to

Re: [DISCUSS] CEP-42: Constraints Framework

Hi Ariel, Your suggestions make sense, and I’ll be updating the CEP with the details. Basically: - We have an optional name for the constraints. If the name is not provided, a random name is generated for a constraint: CREATE TABLE keyspace.table ( p1 int, p2 int, ..., CONSTRAINT [name]

Re: [VOTE][IP CLEARANCE] GoCQL driver

. > The vote will be open for 72 hours (or longer). Votes by PMC members are > considered binding. A vote passes if there are at least three binding +1s > and no -1's. > +1

[VOTE][IP CLEARANCE] GoCQL driver

Please vote on the acceptance of the GoCQL driver and its IP Clearance: https://incubator.apache.org/ip-clearance/cassandra-gocql-driver.html All consent from original authors of the donation, and tracking of collected CLAs, is found in: - https://github.com/gocql/gocql/issues/1751 - https://cwi

Re: [DISCUSS] CEP-42: Constraints Framework

+1 on Doug's suggestion. The operator sets a limit that application developers should not be allowed to violate. This is precisely the type of safety that we should strive for. To Jordan's point, I also agree that the read before write type of constraints should be avoided but if there is a very g

Re: [DISCUSS] CEP-42: Constraints Framework

Hi, I am also +1 on Doug's distinction between things that can be managed by operators and things that can be managed by applications. Some things to note about the syntax is that there are parens around the condition in SQL. In your example there are multiple anonymous constraints on the same

Re: [DISCUSS] CEP-42: Constraints Framework

Got it. Thanks for the clarification Jon. Then, in terms of syntax, I think we can discard the option 2. In terms of GUARDRAIL vs CONSTRAINT concept you bring up, I guess here we have pros and cons for both sides. It is true that there is an existing concept of GUARDRAIL on Cassandra, and that

Re: [VOTE] Release Apache Cassandra 5.0-rc1

. Proposing the test build of Cassandra 5.0-rc1 for release. > > sha1: b43f0b2e9f4cb5105764ef9cf4ece404a740539a > Git: https://github.com/apache/cassandra/tree/5.0-rc1-tentative > Maven Artifacts: > https://repository.apache.org/content/repositories/orgapachecassandra-1336/org/apache/cassandra/cas

[VOTE] Release Apache Cassandra 5.0-rc1

Proposing the test build of Cassandra 5.0-rc1 for release. sha1: b43f0b2e9f4cb5105764ef9cf4ece404a740539a Git: https://github.com/apache/cassandra/tree/5.0-rc1-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1336/org/apache/cassandra/cassandra-all/5