Re: [VOTE] Release Apache Cassandra 5.0.2

reply below. > The vote will be open for 72 hours (longer if needed). Everyone who has > tested the build is invited to vote. Votes by PMC members are considered > binding. A vote passes if there are at least three binding +1s and no -1's. > +1 Checked - signing correct - checksums correct - s

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Nobody wants to suggest a color for this bikeshed? I'll start: CASSDRIVER-. I'd like to get on this sooner than later since during the time we wait the situation worsens. Kind Regards, Brandon On Wed, Oct 2, 2024 at 5:07 PM Brandon Williams wrote: > > I think we just need to ask infra to create

Re: [VOTE] Release Apache Cassandra 5.0.2

+1 Kind Regards, Brandon On Wed, Oct 16, 2024 at 7:19 AM Mick Semb Wever wrote: > > Proposing the test build of Cassandra 5.0.2 for release. > > sha1: f278f6774fc76465c182041e081982105c3e7dbb > Git: https://github.com/apache/cassandra/tree/5.0.2-tentative > Maven Artifacts: > https://repository

Re: [VOTE] CEP-44: Kafka integration for Cassandra CDC using Sidecar

+1 nb From: Brandon Williams Sent: Thursday, October 17, 2024 11:47:13 AM To: dev@cassandra.apache.org Subject: Re: [VOTE] CEP-44: Kafka integration for Cassandra CDC using Sidecar +1 Kind Regards, Brandon On Thu, Oct 17, 2024 at 1:08 PM James Berragan wrote:

Re: [DISCUSS] Modeling JIRA fix version for subprojects

> Can we include Cassandra Analytics to the infra ticket? I am looking > forward to jira project name suggestions for it... How about CASSANALYTICS ? On 2024/10/17 18:50:45 Yifan Cai wrote: > Can we include Cassandra Analytics to the infra ticket? I am looking > forward to jira project name sugge

Re: [Discuss] Repair inside C*

Sorry, there is a typo in the CEP-37 link; here is the correct link On Thu, Oct 17, 2024 at 4:36 PM Jaydeep Chovatia wrote: > First, thank you for your patience while we strengthened the CEP-

Re: [Discuss] Repair inside C*

First, thank you for your patience while we strengthened the CEP-37. Over the last eight months, Chris Lohfink, Andy Tolbert, Josh McKenzie, Dinesh Joshi, Kristijonas Zalys, and I have done tons of work (online discussions/a dedicated Slack channel #cassandra-repair-scheduling-cep37) to come up w

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

I would second Štefan's option for functionality simplicity. It seems to be unnecessary to have the keywords for both inclusion and exclusion in the CEP. If needed, the exclusion (WITHOUT) can be introduced later. It would still be backward compatible. Regarding "CREATE TABLE ks.tb_copy LIKE ks.tb

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

Well we could do something like: CREATE TABLE ks.tb_copy LIKE ks.tb WITH INDICES AND TRIGGERS AND compaction = {'class': ' } AND ... but I can admit it might be seen as an overreach and I am not sure at all how it would look like in the implementation because we would need to distinguish WI

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

Right?! Reads like English, the impact on the existing CQL is minimal. One LIKE which basically needs to be there and keywords of logical "components" which seamlessly integrate with WITH. I would _not_ use WITH CONSTRAINTS because constraints will be inherently part of a table schema. It is not a

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

I think we are starting to complicate it. For me the most important question is who is actually this feature for? If people want to just prototype something fast or they just want to have "the same table just under a different name", I think that is going to be used in 99% of cases. My assumption

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

This simple approach resonates with me. I think the Cassandra doc uses "INDEXES" as the plural for index, i.e.: https://cassandra.apache.org/doc/stable/cassandra/cql/indexes.html -Dave On Thu, Oct 17, 2024 at 2:39 PM Štefan Miklošovič wrote: > Well we could do something like: > > > CREATE TABL

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

Basing it on CREATE TABLE, the BNF definition of the simple implementation would look something like this: create_table_statement::= CREATE TABLE [ IF NOT EXISTS ] table_name LIKE base_table_name [ WITH included_objects ] [ [ AND ] table_options ] table_options::= COMPACT STORAGE [ AND table_opt

Re: [VOTE] CEP-44: Kafka integration for Cassandra CDC using Sidecar

+1 Kind Regards, Brandon On Thu, Oct 17, 2024 at 1:08 PM James Berragan wrote: > > Hi everyone, > > I would like to start the voting for CEP-44 as all the feedback in the > discussion thread seems to be addressed. > > Proposal: CEP-44: Kafka integration for Cassandra CDC using Sidecar > Discuss

Re: [VOTE] CEP-44: Kafka integration for Cassandra CDC using Sidecar

+1 looking forward to this contribution! On 2024/10/17 18:08:00 James Berragan wrote: > Hi everyone, > > I would like to start the voting for CEP-44 as all the feedback in the > discussion thread seems to be addressed. > > Proposal: CEP-44: Kafka integration for Cassandra CDC using Sidecar >

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Can we include Cassandra Analytics to the infra ticket? I am looking forward to jira project name suggestions for it... - Yifan On Thu, Oct 17, 2024 at 10:46 AM Patrick McFadin wrote: > I think it needs a bit more blue. Maybe some pink stripes. I'll file a > Jira. > > On Thu, Oct 17, 2024 at 9:

Re: [DISCUSS] Modeling JIRA fix version for subprojects

I'm with Jon here, -1 to CASSANA and +1 to CASSANALYTICS. Kind Regards, Brandon On Thu, Oct 17, 2024 at 4:00 PM Jon Haddad wrote: > > +1 to CASSANALYTICS > > a fierce -1 to CASSANA. I’ve never once in my life seen this convention and > id prefer clarity over saving a handful of characters. > >

[RELEASE] Apache Cassandra Gocql Driver 1.7.0 released

The Cassandra team is pleased to announce the release of Cassandra Gocql Driver version 1.7.0. The Source release is available here: https://dist.apache.org/repos/dist/release/cassandra/cassandra-gocql-driver/1.7.0/ The changelog for this release can be found at: https://github.com/apache/cass

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

By the way, why can we not do something like this? CREATE TABLE ks.tb_copy LIKE ks.tb WITH compaction = {'class': ' } AND ... That is, I just use the "LIKE" keyword to copy it all as it is in ks.tb but I just override "compaction" as I want (if I am _really_ after that). That way, I get all t

Re: [DISCUSS] Modeling JIRA fix version for subprojects

yep. CASSANALYTICS sounds good to me. +1 On Thu, Oct 17, 2024 at 1:45 PM Francisco Guerrero wrote: > > Can we include Cassandra Analytics to the infra ticket? I am looking > > forward to jira project name suggestions for it... > > How about CASSANALYTICS ? > > On 2024/10/17 18:50:45 Yifan Cai wr

Re: [DISCUSS] Modeling JIRA fix version for subprojects

+1 to CASSANALYTICS > On Oct 17, 2024, at 1:48 PM, Yifan Cai wrote: > > yep. CASSANALYTICS sounds good to me. +1 > > On Thu, Oct 17, 2024 at 1:45 PM Francisco Guerrero > wrote: >> > Can we include Cassandra Analytics to the infra ticket? I am looking >> > forward to

Re: [DISCUSS] Modeling JIRA fix version for subprojects

CASSANA would do it. CASSANALYTICS is just too long. People are used to the terminology of "ana" e.g. when naming their analytics data centers. On Thu, Oct 17, 2024 at 2:55 PM Bernardo Botella < conta...@bernardobotella.com> wrote: > +1 to CASSANALYTICS > > On Oct 17, 2024, at 1:48 PM, Yifan Cai

Re: [DISCUSS] Modeling JIRA fix version for subprojects

+1 to CASSANALYTICS a fierce -1 to CASSANA. I’ve never once in my life seen this convention and id prefer clarity over saving a handful of characters. — Jon Haddad Rustyrazorblade Consulting rustyrazorblade.com On Thu, Oct 17, 2024 at 1:57 PM Štefan Miklošovič wrote: > CASSANA would do it. CA

Re: [DISCUSS] Modeling JIRA fix version for subprojects

> CASSANA would do it. CASSANALYTICS is just too long. People are used to the > terminology of "ana" e.g. when naming their analytics data centers. CASSANA looks like a "Cassandra" typo to me. But naming is hard, so let's see if others have an opinion about this. On 2024/10/17 20:57:29 Štefan Mik

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Interesting, adding "-ana" suffix to a dc which is meant to be an analytical one was pretty common in cases I saw. People just want to look at it and see the difference, how do they name it then? dc2? Also, omitting 2 letters does not seem like a typo to me either. Anyway, we are clearly after th

Re: [VOTE] CEP-44: Kafka integration for Cassandra CDC using Sidecar

+1 On Thu, Oct 17, 2024, at 2:51 PM, Yifan Cai wrote: > +1 nb > > > *From:* Brandon Williams > *Sent:* Thursday, October 17, 2024 11:47:13 AM > *To:* dev@cassandra.apache.org > *Subject:* Re: [VOTE] CEP-44: Kafka integration for Cassandra CDC using > Sidecar > > +1 > > Kind Regards, > Bran

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Sgtm, let’s ship it +1 On Thu, Oct 17, 2024 at 4:09 AM Brandon Williams wrote: > Nobody wants to suggest a color for this bikeshed? I'll start: > CASSDRIVER-. I'd like to get on this sooner than later since > during the time we wait the situation worsens. > > Kind Regards, > Brandon > > On W

Re: [DISCUSS] Modeling JIRA fix version for subprojects

It would have been nice to be in red italic but… :-) Thanks, Brandon, +1 to the suggestion on my end too. Sounds reasonable to me On Thu, 17 Oct 2024 at 17:50, Abe Ratnofsky wrote: > +1 to CASSDRIVER-JAVA et al. > > On Oct 17, 2024, at 10:37 AM, Jon Haddad wrote: > > Sgtm, let’s ship it > > +

Re: [DISCUSS] Modeling JIRA fix version for subprojects

+1 to CASSDRIVER-JAVA et al. > On Oct 17, 2024, at 10:37 AM, Jon Haddad wrote: > > Sgtm, let’s ship it > > +1 > > > > On Thu, Oct 17, 2024 at 4:09 AM Brandon Williams > wrote: >> Nobody wants to suggest a color for this bikeshed? I'll start: >> CASSDRIVER-. I'd lik

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Thanks everyone, I've created https://issues.apache.org/jira/browse/INFRA-26212 Kind Regards, Brandon On Thu, Oct 17, 2024 at 9:55 AM Ekaterina Dimitrova wrote: > > It would have been nice to be in red italic but… :-) > > Thanks, Brandon, +1 to the suggestion on my end too. Sounds reasonable to

Re: [DISCUSS] Modeling JIRA fix version for subprojects

I think it needs a bit more blue. Maybe some pink stripes. I'll file a Jira. On Thu, Oct 17, 2024 at 9:01 AM Brandon Williams wrote: > Thanks everyone, I've created > https://issues.apache.org/jira/browse/INFRA-26212 > > Kind Regards, > Brandon > > On Thu, Oct 17, 2024 at 9:55 AM Ekaterina Dimit

[VOTE] CEP-44: Kafka integration for Cassandra CDC using Sidecar

Hi everyone, I would like to start the voting for CEP-44 as all the feedback in the discussion thread seems to be addressed. Proposal: CEP-44: Kafka integration for Cassandra CDC using Sidecar