Re: [DISCUSS] Modeling JIRA fix version for subprojects

2024-04-04 Thread Abe Ratnofsky
CEP-8 proposes using separate Jira projects per Cassandra sub-project: https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-8%3A+DataStax+Drivers+Donation > We suggest distinct Jira projects, one per driver, all to be created. I don't see any discussion changing that from the [DISCUSS] or vo

Re: [DISCUSS] Modeling JIRA fix version for subprojects

2024-04-04 Thread Jon Haddad
Imo it would be better to have standalone JIRA projects for each of the subprojects we have, just like we do the sidecar. On Thu, Apr 4, 2024 at 10:47 AM Francisco Guerrero wrote: > Hi Bret, > > Thanks for bringing up this issue. The Cassandra Analytics library will > also need to have its own v

Re: [DISCUSS] Modeling JIRA fix version for subprojects

2024-04-04 Thread Francisco Guerrero
Hi Bret, Thanks for bringing up this issue. The Cassandra Analytics library will also need to have its own versioning. We should align on version naming for subprojects and start using it for both the Java Driver and the Analytics library. I propose the following versioning "java-driver-${version

Re: [DISCUSS] NULL handling and the unfrozen collection issue

2024-04-04 Thread Caleb Rackliffe
The easiest way to check out how Accord uses IS NULL and IS NOT NULL is to look at the examples in the cep-15-accord branch: https://github.com/apache/cassandra/blob/cep-15-accord/test/distributed/org/apache/cassandra/distributed/test/accord/AccordCQLTestBase.java tl;dr We did indeed try to go wi

Re: [DISCUSS] NULL handling and the unfrozen collection issue

2024-04-04 Thread Benjamin Lerer
> > Now, in Cassandra setting a column to null means deleting it and if *all* > columns in a row are null the row is deleted. This might be another edge > case... It is slightly more complicated than that as the primary key columns count in (*all* columns) For example if you have the following t