Re: [DISCUSS] Modeling JIRA fix version for subprojects

2024-10-18 Thread Brandon Williams
I think for the sidecar we need the dash to avoid the typo-likely
'SSS' wart. I have updated INFRA-26212 to follow CASS-DRIVER-.

Kind Regards,
Brandon

On Fri, Oct 18, 2024 at 4:55 AM Mick Semb Wever  wrote:
>
> Could we also rename CASSANDRASC to CASSSIDECAR ?
>
> And tbh, i'd much rather CASS-DRIVER-, CASS-ANALYTICS and CASS-SIDECAR
>  (but ofc it's not really important)
>
>
>
> On Thu, 17 Oct 2024 at 23:11, Štefan Miklošovič  
> wrote:
>>
>> 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 the other so CASSANALYTICS be it.
>>
>>
>> On Thu, Oct 17, 2024 at 3:03 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.
>>>
>>> —
>>> Jon Haddad
>>> Rustyrazorblade Consulting
>>> rustyrazorblade.com
>>>
>>>
>>> On Thu, Oct 17, 2024 at 1:57 PM Štefan Miklošovič  
>>> wrote:

 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 
  wrote:
>
> +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 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 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: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 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 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
>> > >> >>
>> > >> >> +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 Wed, Oct 2, 2024 at 5:07 PM Brandon Williams 
>> > >> >>> 
>> > >> wrote:
>> > >> >>> >
>> > >> >>> > I think we just need to ask infra to create the jira 
>> > >> >>> > instances, but
>> > >> I
>> > >> >>> > guess we need to have some kind of consistent naming scheme 
>> > >> >>> > to help
>> > >> >>> > identify them?
>> > >> >>> >
>> > >> >>> > Kind Regards,
>> > >> >>> > Brandon
>> > >> >>> >
>> > >> >>> > On Wed, Oct 2, 2024 at 1:02 PM Francisco Guerrero <
>> > >> fran...@apache.org> wrote:
>> > >> >>> > >
>> > >> >>> > > +1 too on the points brought by Mick, we need more 
>> > >> >>> > > visibility into
>> > >> >>> > > subprojects. For starters, we should look into integrating 
>> > >> >>> > > Qbot
>> > >> >>> > > notifications in #cassandra-dev and #cassandra-noise for
>> > >> >>> > > CASSANDRASC tickets. Let me know if I can help with that.
>> > >> >>> > >
>> > >> >>> > > On 2024/10/02 17:39:28 Yifan Cai wrote:
>> > >> >>> > > > +1 on all the points raised by Mick. Please let me know if
>> > >> there is
>> > >> >>> > > > anything I can help with.
>> > >> >>> > > >
>> > >> >>> > > > - Yifan
>> > >> >>> > > >
>> > >> >>> > > > On Wed, Oct 2, 2024 at 8:13 AM Josh McKenzie <
>> > 

Re: [DISCUSS] Modeling JIRA fix version for subprojects

2024-10-18 Thread Patrick McFadin
Awesome. Now this is the bikeshedding I'm here for. :popcorn:

On Fri, Oct 18, 2024 at 5:26 AM Brandon Williams  wrote:

> I think for the sidecar we need the dash to avoid the typo-likely
> 'SSS' wart. I have updated INFRA-26212 to follow CASS-DRIVER-.
>
> Kind Regards,
> Brandon
>
> On Fri, Oct 18, 2024 at 4:55 AM Mick Semb Wever  wrote:
> >
> > Could we also rename CASSANDRASC to CASSSIDECAR ?
> >
> > And tbh, i'd much rather CASS-DRIVER-, CASS-ANALYTICS and
> CASS-SIDECAR
> >  (but ofc it's not really important)
> >
> >
> >
> > On Thu, 17 Oct 2024 at 23:11, Štefan Miklošovič 
> wrote:
> >>
> >> 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 the other so CASSANALYTICS be it.
> >>
> >>
> >> On Thu, Oct 17, 2024 at 3:03 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.
> >>>
> >>> —
> >>> Jon Haddad
> >>> Rustyrazorblade Consulting
> >>> rustyrazorblade.com
> >>>
> >>>
> >>> On Thu, Oct 17, 2024 at 1:57 PM Štefan Miklošovič <
> smikloso...@apache.org> wrote:
> 
>  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  wrote:
> >
> > yep. CASSANALYTICS sounds good to me. +1
> >
> > On Thu, Oct 17, 2024 at 1:45 PM Francisco Guerrero <
> fran...@apache.org> 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 wrote:
> >> > 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 <
> pmcfa...@gmail.com> 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:01 AM Brandon Williams <
> dri...@gmail.com> 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 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 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 <
> j...@rustyrazorblade.com>
> >> > >> wrote:
> >> > >> >>
> >> > >> >> Sgtm, let’s ship it
> >> > >> >>
> >> > >> >> +1
> >> > >> >>
> >> > >> >>
> >> > >> >>
> >> > >> >> On Thu, Oct 17, 2024 at 4:09 AM Brandon Williams <
> dri...@gmail.com>
> >> > >> 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 Wed, Oct 2, 2024 at 5:07 PM Brandon Williams <
> dri...@gmail.com>
> >> > >> wrote:
> >> > >> >>> >
> >> > >> >>> > I think we just need to ask infra to create the jira
> instances, but
> >> > >> I
> >> > >> >>> > guess we need to have some kind of consistent naming
> scheme to help
> >> > >> >>> > identify them?
> >> > >> >>> >
> >> > >> >>> > Kind Regards,
> >> > >> >>> > Brandon
> >> > >> >>> >
> >> > >> >>> > On Wed, Oct 2, 2024 at 1:02 PM Francisco Guerrero <
> >> > >> fran...@apache.org> wrote:
> >> > >> >>> > >
> >> > >> >>> > > +1 too on the points brought by Mick, we need more
> visibility into
> >> > >> >>> > > subprojects. For starters, we should look into
> integrating Qbot
> >> > >> >>> > > notifications in #cassandra-dev and #cassandra-noise
> for
> >> > >> >>> > > CASSANDRASC tickets. Let me know if I can help with
> that.
> >> > >> >>

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

2024-10-18 Thread Bernardo Botella
+1 nb

> On Oct 17, 2024, at 5:52 PM, Josh McKenzie  wrote:
> 
> +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,
>> 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
>> > Discussion thread: 
>> > https://lists.apache.org/thread/8k6njsnvdbmjb6jhyy07o1s7jz8xp1qg
>> >
>> > As per the CEP process documentation, this vote will be open for 72 hours 
>> > (longer if needed).
>> >
>> > Thanks!
>> > James.



Re: [DISCUSS] Modeling JIRA fix version for subprojects

2024-10-18 Thread Yifan Cai
That is good to know.

My preference would be moving the driver projects and analytics first, and
renaming the sidecar project later. However, if it is not a concern, I am
fine with doing the change in bulk, especially if it is more convenient.

- Yifan

On Fri, Oct 18, 2024 at 11:24 AM Jon Haddad  wrote:

> I'm 95% sure it redirects automatically.  I believe those redirects also
> work when moving issues from one project to another, so when we move all
> the driver issues to their own repos everything should keep working.
>
>
>
> On Fri, Oct 18, 2024 at 11:21 AM Francisco Guerrero 
> wrote:
>
>> This is one thing that comes to mind.
>>
>> All of the commits in Sidecar have a reference to the JIRA, if we switch
>> it from CASSANDRASC -> CASS-SIDECAR, will there he redirection of
>> these tickets? Or will be lose those links and the ability to
>> automatically
>> refer to the JIRAs?
>>
>> On 2024/10/18 18:17:16 Yifan Cai wrote:
>> > Anyone know if there are any traps when renaming a JIRA project? Since
>> we
>> > are talking about change CASSANDRASC to CASS-SIDECAR.
>> >
>> >
>> > - Yifan
>> >
>> > On Fri, Oct 18, 2024 at 10:50 AM Patrick McFadin 
>> wrote:
>> >
>> > > Awesome. Now this is the bikeshedding I'm here for. :popcorn:
>> > >
>> > > On Fri, Oct 18, 2024 at 5:26 AM Brandon Williams 
>> wrote:
>> > >
>> > >> I think for the sidecar we need the dash to avoid the typo-likely
>> > >> 'SSS' wart. I have updated INFRA-26212 to follow CASS-DRIVER-.
>> > >>
>> > >> Kind Regards,
>> > >> Brandon
>> > >>
>> > >> On Fri, Oct 18, 2024 at 4:55 AM Mick Semb Wever 
>> wrote:
>> > >> >
>> > >> > Could we also rename CASSANDRASC to CASSSIDECAR ?
>> > >> >
>> > >> > And tbh, i'd much rather CASS-DRIVER-, CASS-ANALYTICS and
>> > >> CASS-SIDECAR
>> > >> >  (but ofc it's not really important)
>> > >> >
>> > >> >
>> > >> >
>> > >> > On Thu, 17 Oct 2024 at 23:11, Štefan Miklošovič <
>> smikloso...@apache.org>
>> > >> wrote:
>> > >> >>
>> > >> >> 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 the other so CASSANALYTICS be it.
>> > >> >>
>> > >> >>
>> > >> >> On Thu, Oct 17, 2024 at 3:03 PM Jon Haddad <
>> j...@rustyrazorblade.com>
>> > >> 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.
>> > >> >>>
>> > >> >>> —
>> > >> >>> Jon Haddad
>> > >> >>> Rustyrazorblade Consulting
>> > >> >>> rustyrazorblade.com
>> > >> >>>
>> > >> >>>
>> > >> >>> On Thu, Oct 17, 2024 at 1:57 PM Štefan Miklošovič <
>> > >> smikloso...@apache.org> wrote:
>> > >> 
>> > >>  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 
>> wrote:
>> > >> >
>> > >> > yep. CASSANALYTICS sounds good to me. +1
>> > >> >
>> > >> > On Thu, Oct 17, 2024 at 1:45 PM Francisco Guerrero <
>> > >> fran...@apache.org> 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 wrote:
>> > >> >> > 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 <
>> > >> pmcfa...@gmail.com> 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:01 AM Brandon Williams <
>> > >> dri...@gmail.com> 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 Dimitrova
>> > >> >> > >>  wrote:
>> > >> >> > >> >
>> > >> >> > >> > It would have been nice to be in red italic but… :-)
>> > >> >> > >> >
>> > >> >> > >> > Thanks, Brandon, +1 to the suggestion on my end too.
>> Sounds
>> > >> reason

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

2024-10-18 Thread Dave Herrington
It seems like a natural extension of the CREATE TABLE statement.  Looking
forward to using it in the future.

-Dave

On Thu, Oct 17, 2024 at 5:11 PM Štefan Miklošovič 
wrote:

> 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 an "option". We can not "opt-out" from
> them. Remember we are copying a table here so if a base one has
> constraints, its copy will have them too. A user can subsequently "ALTER"
> them.
>
> On Thu, Oct 17, 2024 at 5:31 PM Dave Herrington 
> wrote:
>
>> 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_options ]
>>
>> | CLUSTERING ORDER BY '(' clustering_order ')'
>>
>> [ AND table_options ]  | options
>>
>> clustering_order::= column_name (ASC | DESC) ( ',' column_name (ASC |
>> DESC) )*
>>
>> included_objects::= dependent_objects [ AND dependent_objects ]
>>
>> dependent_objects:= INDEXES | TRIGGERS | CONSTRAINTS | VIEWS
>>
>>
>> CREATE TABLE [ IF NOT EXISTS ] [.] LIKE
>> [.]
>>
>>   [ WITH [  ]
>>
>>   [ [ AND ] [  ] ]
>>
>>   [ [ AND ] CLUSTERING ORDER BY [  (ASC | DESC) ]
>> ]
>>
>> ;
>>
>>
>> Examples:
>>
>>
>> -- Create base table:
>>
>> CREATE TABLE cycling.cyclist_name (
>>
>>   id UUID PRIMARY KEY,
>>
>>   lastname text,
>>
>>   firstname text
>>
>> );
>>
>> -- Create an exact copy of the base table, but do not create any
>> dependent objects:
>>
>> CREATE TABLE cycling.cyclist_name2 LIKE cycling.cyclist_name;
>>
>> -- Create an exact copy with all dependent objects (constraints excluded
>> for now):
>>
>> CREATE TABLE cycling.cyclist_name3 LIKE cycling.cyclist_name
>>
>> WITH INDEXES AND TRIGGERS AND VIEWS;
>>
>> -- Create a copy with LCS compaction, a default TTL and all dependent
>> objects except indexes:
>>
>> CREATE TABLE cycling.cyclist_name4 LIKE cycling.cyclist_name
>>
>> WITH TRIGGERS AND VIEWS
>>
>> AND compaction = { 'class' :  'LeveledCompactionStrategy' }
>>
>> AND default_time_to_live = 86400;
>>
>>
>>
>> This seems pretty clean & straightforward.
>>
>>
>> -Dave
>>
>> On Thu, Oct 17, 2024 at 4:05 PM Dave Herrington 
>> wrote:
>>
>>> 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č <
>>> smikloso...@apache.org> wrote:
>>>
 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 WITH INDICES from table options.


 I would

1. +0 on ALL. - we don't need this. If we have just INDICES,
TRIGGERS, VIEWS at this point, I don't think enumerating it all is too 
 much
to ask. This is just an implementation detail and if we find it 
 necessary
we can add it later. If you feel strongly about this then add that but 
 it
is not absolutely necessary.
2. omit OPTIONS - aren't all options copied by default? That is the
goal of the CEP, no? We might just use normal CQL while overriding
from the base table
3. mix keywords like TRIGGERS / INDICES / CONSTRAINTS into normal
table creation statement



 On Thu, Oct 17, 2024 at 3:20 PM Yifan Cai  wrote:

> 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 WITH compaction =
> {'class': ' } AND ... ", I think it only overrides the table options.
> The CEP suggests the coarse-grained keyword for each category like table
> options, indexes, etc. The functionality provided is not identical.
>
> I understand that the suggestions are to make operators' life easier
> by achieving table creation in a single statement. What is being proposed
> in the CEP seems to be at a good balance point. Operators can alter the
> table options if needed in the follow-up ALTER table statement.
>
> - Yifan
>
>
>
> On Thu, Oct 17, 2024 at 1:41 PM Štefan Miklošovič <
> smikloso...@apache.org

Re: [DISCUSS] Modeling JIRA fix version for subprojects

2024-10-18 Thread Štefan Miklošovič
Third time's the charm. In case somebody got I wrong, I want to correct
myself.


I wrote "Right ... I got it" at the end, what I meant by that is that I
actually don't.


My point is that if we are after readability, we should not shorten the
project name itself. It is inconsistent with CASSANDRA, there is no "CASS"
project either. There is CASSANDRA project so we should follow it.


If we made it so far to suggest "CASS-ANALYTICS", I don't get why we
shouldn't use "CASSANDRA-ANALYTICS". That is the same argument as instead
of "CASS-ANA" we just need to use "CASS-ANALYTICS". Why not expand "CASS"
as well? I just don't buy that it would be too long if the argument is like
that.

On Fri, Oct 18, 2024 at 2:11 PM Štefan Miklošovič 
wrote:

> I think that this:
>
> CASS-ANALYTICS
>
> is actually worse than this
>
> CASSANDRA-ANA (or any variation of that).
>
> I would just expand CASS to CASSANDRA everywhere, if we dont, then you are
> trying to say that this
>
> CASSANDRA-ANALYTICS
>
> is just too long, but this
>
> CASS-ANALYTICS
>
> isn't.
>
> Right ... got it.
>
>
>
> On Fri, Oct 18, 2024 at 1:35 PM Štefan Miklošovič 
> wrote:
>
>> So we will have:
>>
>>
>> CASSANDRA
>>
>> CASS-DRIVER-JAVA
>> CASS-DRIVER-GO
>>
>> CASS-ANALYTICS
>>
>> CASS-SIDECAR
>>
>>
>> Isn't it weird that you said that we should not save characters at the
>> cost of readability while we just use CASS everywhere except the main
>> project? Why do you think that having "CASS-" will make people
>> automatically think that this is Cassandra related. No other project in
>> Apache (afaik) makes the shortcuts like that.
>>
>> On Fri, Oct 18, 2024 at 1:31 PM Yifan Cai  wrote:
>>
>>> That is good to know.
>>>
>>> My preference would be moving the driver projects and analytics first,
>>> and renaming the sidecar project later. However, if it is not a concern, I
>>> am fine with doing the change in bulk, especially if it is more convenient.
>>>
>>> - Yifan
>>>
>>> On Fri, Oct 18, 2024 at 11:24 AM Jon Haddad 
>>> wrote:
>>>
 I'm 95% sure it redirects automatically.  I believe those redirects
 also work when moving issues from one project to another, so when we move
 all the driver issues to their own repos everything should keep working.



 On Fri, Oct 18, 2024 at 11:21 AM Francisco Guerrero 
 wrote:

> This is one thing that comes to mind.
>
> All of the commits in Sidecar have a reference to the JIRA, if we
> switch
> it from CASSANDRASC -> CASS-SIDECAR, will there he redirection of
> these tickets? Or will be lose those links and the ability to
> automatically
> refer to the JIRAs?
>
> On 2024/10/18 18:17:16 Yifan Cai wrote:
> > Anyone know if there are any traps when renaming a JIRA project?
> Since we
> > are talking about change CASSANDRASC to CASS-SIDECAR.
> >
> >
> > - Yifan
> >
> > On Fri, Oct 18, 2024 at 10:50 AM Patrick McFadin 
> wrote:
> >
> > > Awesome. Now this is the bikeshedding I'm here for. :popcorn:
> > >
> > > On Fri, Oct 18, 2024 at 5:26 AM Brandon Williams 
> wrote:
> > >
> > >> I think for the sidecar we need the dash to avoid the typo-likely
> > >> 'SSS' wart. I have updated INFRA-26212 to follow
> CASS-DRIVER-.
> > >>
> > >> Kind Regards,
> > >> Brandon
> > >>
> > >> On Fri, Oct 18, 2024 at 4:55 AM Mick Semb Wever 
> wrote:
> > >> >
> > >> > Could we also rename CASSANDRASC to CASSSIDECAR ?
> > >> >
> > >> > And tbh, i'd much rather CASS-DRIVER-, CASS-ANALYTICS and
> > >> CASS-SIDECAR
> > >> >  (but ofc it's not really important)
> > >> >
> > >> >
> > >> >
> > >> > On Thu, 17 Oct 2024 at 23:11, Štefan Miklošovič <
> smikloso...@apache.org>
> > >> wrote:
> > >> >>
> > >> >> 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 the other so CASSANALYTICS be it.
> > >> >>
> > >> >>
> > >> >> On Thu, Oct 17, 2024 at 3:03 PM Jon Haddad <
> j...@rustyrazorblade.com>
> > >> 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.
> > >> >>>
> > >> >>> —
> > >> >>> Jon Haddad
> > >> >>> Rustyrazorblade Consulting
> > >> >>> rustyrazorblade.com
> > >> >>>
> > >> >>>
> > >> >>> On Thu, Oct 17, 2024 at 1:57 PM Štefan Miklošovič <
> > >> smikloso...@apache.org> wrote:
> > >> 
> > >>  CASSANA would do it. CASSANALYTICS is just too long. P

Re: [DISCUSS] Modeling JIRA fix version for subprojects

2024-10-18 Thread Paulo Motta
+1 to Mick’s suggestion CASS-DRIVER- / CASS-SIDECAR / CASS-ANALYTICS,
this feels more consistent and readable than without the dash.

Also -1 to CASSANA fwiw, sorry Stefan 😅

/bikeshed

On Fri, 18 Oct 2024 at 05:55 Mick Semb Wever  wrote:

> Could we also rename CASSANDRASC to CASSSIDECAR ?
>
> And tbh, i'd much rather CASS-DRIVER-, CASS-ANALYTICS and
> CASS-SIDECAR
>  (but ofc it's not really important)
>
>
>
> On Thu, 17 Oct 2024 at 23:11, Štefan Miklošovič 
> wrote:
>
>> 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 the other so CASSANALYTICS be it.
>>
>> On Thu, Oct 17, 2024 at 3:03 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.
>>>
>>> —
>>> Jon Haddad
>>> Rustyrazorblade Consulting
>>> rustyrazorblade.com
>>>
>>>
>>> On Thu, Oct 17, 2024 at 1:57 PM Štefan Miklošovič <
>>> smikloso...@apache.org> wrote:
>>>
 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  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 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 suggestions for it...
>> >
>> > - Yifan
>> >
>> > On Thu, Oct 17, 2024 at 10:46 AM Patrick McFadin <
>> pmcfa...@gmail.com> 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:01 AM Brandon Williams <
>> dri...@gmail.com> 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 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 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 <
>> j...@rustyrazorblade.com>
>> > >> wrote:
>> > >> >>
>> > >> >> Sgtm, let’s ship it
>> > >> >>
>> > >> >> +1
>> > >> >>
>> > >> >>
>> > >> >>
>> > >> >> On Thu, Oct 17, 2024 at 4:09 AM Brandon Williams <
>> dri...@gmail.com>
>> > >> 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 Wed, Oct 2, 2024 at 5:07 PM Brandon Williams <
>> dri...@gmail.com>
>> > >> wrote:
>> > >> >>> >
>> > >> >>> > I think we just need to ask infra to create the jira
>> instances, but
>> > >> I
>> > >> >>> > guess we need to have some kind of consistent naming
>> scheme to help
>> > >> >>> > identify them?
>> > >> >>> >
>> > >> >>> > Kind Regards,
>> > >> >>> > Brandon
>> > >> >>> >
>> > >> >>> > On Wed, Oct 2, 2024 at 1:02 PM Francisco Guerrero <
>> > >> fran...@apache.org> wrote:
>> > >> >>> > >
>> > >> >>> > > +1 too on the points brought by Mick, we need more
>> visibility into
>> > >> >>> > > subprojects. For starters, we should look into
>> integrating Qbot
>> > >> >>> > > notifications in #cassandra-dev and #cassandra-noise for
>> > >> >>> > > CASSANDRASC tickets. Let me know if I can help with that.
>> > >> >>> > >
>> > >> >>> > > On 2024/10/02 17:39:28 Yifan Cai wrote:
>> > >> >>> > > > +1 on all the points raised by Mick. Please let me
>> know if
>> > >> there is
>> > >> >>> > > > anything I can help with.
>> > >> >>> > > >
>> > >> >>> > > > - Yifan
>> > >> 

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

2024-10-18 Thread Jon Haddad
+1

On Fri, Oct 18, 2024 at 10:51 AM Bernardo Botella <
conta...@bernardobotella.com> wrote:

> +1 nb
>
> On Oct 17, 2024, at 5:52 PM, Josh McKenzie  wrote:
>
> +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,
> 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
> > Discussion thread:
> https://lists.apache.org/thread/8k6njsnvdbmjb6jhyy07o1s7jz8xp1qg
> >
> > As per the CEP process documentation, this vote will be open for 72
> hours (longer if needed).
> >
> > Thanks!
> > James.
>
>
>


Re: [DISCUSS] Modeling JIRA fix version for subprojects

2024-10-18 Thread Francisco Guerrero
This is one thing that comes to mind.

All of the commits in Sidecar have a reference to the JIRA, if we switch
it from CASSANDRASC -> CASS-SIDECAR, will there he redirection of
these tickets? Or will be lose those links and the ability to automatically
refer to the JIRAs?

On 2024/10/18 18:17:16 Yifan Cai wrote:
> Anyone know if there are any traps when renaming a JIRA project? Since we
> are talking about change CASSANDRASC to CASS-SIDECAR.
> 
> 
> - Yifan
> 
> On Fri, Oct 18, 2024 at 10:50 AM Patrick McFadin  wrote:
> 
> > Awesome. Now this is the bikeshedding I'm here for. :popcorn:
> >
> > On Fri, Oct 18, 2024 at 5:26 AM Brandon Williams  wrote:
> >
> >> I think for the sidecar we need the dash to avoid the typo-likely
> >> 'SSS' wart. I have updated INFRA-26212 to follow CASS-DRIVER-.
> >>
> >> Kind Regards,
> >> Brandon
> >>
> >> On Fri, Oct 18, 2024 at 4:55 AM Mick Semb Wever  wrote:
> >> >
> >> > Could we also rename CASSANDRASC to CASSSIDECAR ?
> >> >
> >> > And tbh, i'd much rather CASS-DRIVER-, CASS-ANALYTICS and
> >> CASS-SIDECAR
> >> >  (but ofc it's not really important)
> >> >
> >> >
> >> >
> >> > On Thu, 17 Oct 2024 at 23:11, Štefan Miklošovič 
> >> wrote:
> >> >>
> >> >> 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 the other so CASSANALYTICS be it.
> >> >>
> >> >>
> >> >> On Thu, Oct 17, 2024 at 3:03 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.
> >> >>>
> >> >>> —
> >> >>> Jon Haddad
> >> >>> Rustyrazorblade Consulting
> >> >>> rustyrazorblade.com
> >> >>>
> >> >>>
> >> >>> On Thu, Oct 17, 2024 at 1:57 PM Štefan Miklošovič <
> >> smikloso...@apache.org> wrote:
> >> 
> >>  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  wrote:
> >> >
> >> > yep. CASSANALYTICS sounds good to me. +1
> >> >
> >> > On Thu, Oct 17, 2024 at 1:45 PM Francisco Guerrero <
> >> fran...@apache.org> 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 wrote:
> >> >> > 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 <
> >> pmcfa...@gmail.com> 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:01 AM Brandon Williams <
> >> dri...@gmail.com> 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 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 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 <
> >> j...@rustyrazorblade.com>
> >> >> > >> wrote:
> >> >> > >> >>
> >> >> > >> >> Sgtm, let’s ship it
> >> >> > >> >>
> >> >> > >> >> +1
> >> >> > >> >>
> >> >> > >> >>
> >> >> > >> >>
> >> >> > >> >> On Thu, Oct 17, 2024 at 4:09 AM Brandon Williams <
> >> dri...@gmail.com>
> >> >> > >> 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 Wed, Oct

Re: [DISCUSS] Modeling JIRA fix version for subprojects

2024-10-18 Thread Yifan Cai
Anyone know if there are any traps when renaming a JIRA project? Since we
are talking about change CASSANDRASC to CASS-SIDECAR.


- Yifan

On Fri, Oct 18, 2024 at 10:50 AM Patrick McFadin  wrote:

> Awesome. Now this is the bikeshedding I'm here for. :popcorn:
>
> On Fri, Oct 18, 2024 at 5:26 AM Brandon Williams  wrote:
>
>> I think for the sidecar we need the dash to avoid the typo-likely
>> 'SSS' wart. I have updated INFRA-26212 to follow CASS-DRIVER-.
>>
>> Kind Regards,
>> Brandon
>>
>> On Fri, Oct 18, 2024 at 4:55 AM Mick Semb Wever  wrote:
>> >
>> > Could we also rename CASSANDRASC to CASSSIDECAR ?
>> >
>> > And tbh, i'd much rather CASS-DRIVER-, CASS-ANALYTICS and
>> CASS-SIDECAR
>> >  (but ofc it's not really important)
>> >
>> >
>> >
>> > On Thu, 17 Oct 2024 at 23:11, Štefan Miklošovič 
>> wrote:
>> >>
>> >> 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 the other so CASSANALYTICS be it.
>> >>
>> >>
>> >> On Thu, Oct 17, 2024 at 3:03 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.
>> >>>
>> >>> —
>> >>> Jon Haddad
>> >>> Rustyrazorblade Consulting
>> >>> rustyrazorblade.com
>> >>>
>> >>>
>> >>> On Thu, Oct 17, 2024 at 1:57 PM Štefan Miklošovič <
>> smikloso...@apache.org> wrote:
>> 
>>  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  wrote:
>> >
>> > yep. CASSANALYTICS sounds good to me. +1
>> >
>> > On Thu, Oct 17, 2024 at 1:45 PM Francisco Guerrero <
>> fran...@apache.org> 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 wrote:
>> >> > 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 <
>> pmcfa...@gmail.com> 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:01 AM Brandon Williams <
>> dri...@gmail.com> 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 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 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 <
>> j...@rustyrazorblade.com>
>> >> > >> wrote:
>> >> > >> >>
>> >> > >> >> Sgtm, let’s ship it
>> >> > >> >>
>> >> > >> >> +1
>> >> > >> >>
>> >> > >> >>
>> >> > >> >>
>> >> > >> >> On Thu, Oct 17, 2024 at 4:09 AM Brandon Williams <
>> dri...@gmail.com>
>> >> > >> 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 Wed, Oct 2, 2024 at 5:07 PM Brandon Williams <
>> dri...@gmail.com>
>> >> > >> wrote:
>> >> > >> >>> >
>> >> > >> >>> > I think we just need to ask infra to create the jira
>> instances, but
>> >> > >> I
>> >> > >> >>> > guess we need to have some kind of consistent naming
>> scheme to help
>> >> > >> >>> > identify them?
>> >> > >> >>> >
>> >> > >> >>> > Kind Regards,
>> >> > >> >>> > Brandon
>> >> > >> >>> >
>> >> > >> >>> > On Wed, Oct 2, 2024 at 1:02 PM Francisco Guerrero <
>> >> > >> fran...@apache.org> wrote:
>> >> > >> >>> > >
>> >> >

Re: [DISCUSS] Modeling JIRA fix version for subprojects

2024-10-18 Thread Štefan Miklošovič
So we will have:


CASSANDRA

CASS-DRIVER-JAVA
CASS-DRIVER-GO

CASS-ANALYTICS

CASS-SIDECAR


Isn't it weird that you said that we should not save characters at the cost
of readability while we just use CASS everywhere except the main project?
Why do you think that having "CASS-" will make people automatically think
that this is Cassandra related. No other project in Apache (afaik) makes
the shortcuts like that.

On Fri, Oct 18, 2024 at 1:31 PM Yifan Cai  wrote:

> That is good to know.
>
> My preference would be moving the driver projects and analytics first, and
> renaming the sidecar project later. However, if it is not a concern, I am
> fine with doing the change in bulk, especially if it is more convenient.
>
> - Yifan
>
> On Fri, Oct 18, 2024 at 11:24 AM Jon Haddad 
> wrote:
>
>> I'm 95% sure it redirects automatically.  I believe those redirects also
>> work when moving issues from one project to another, so when we move all
>> the driver issues to their own repos everything should keep working.
>>
>>
>>
>> On Fri, Oct 18, 2024 at 11:21 AM Francisco Guerrero 
>> wrote:
>>
>>> This is one thing that comes to mind.
>>>
>>> All of the commits in Sidecar have a reference to the JIRA, if we switch
>>> it from CASSANDRASC -> CASS-SIDECAR, will there he redirection of
>>> these tickets? Or will be lose those links and the ability to
>>> automatically
>>> refer to the JIRAs?
>>>
>>> On 2024/10/18 18:17:16 Yifan Cai wrote:
>>> > Anyone know if there are any traps when renaming a JIRA project? Since
>>> we
>>> > are talking about change CASSANDRASC to CASS-SIDECAR.
>>> >
>>> >
>>> > - Yifan
>>> >
>>> > On Fri, Oct 18, 2024 at 10:50 AM Patrick McFadin 
>>> wrote:
>>> >
>>> > > Awesome. Now this is the bikeshedding I'm here for. :popcorn:
>>> > >
>>> > > On Fri, Oct 18, 2024 at 5:26 AM Brandon Williams 
>>> wrote:
>>> > >
>>> > >> I think for the sidecar we need the dash to avoid the typo-likely
>>> > >> 'SSS' wart. I have updated INFRA-26212 to follow CASS-DRIVER-.
>>> > >>
>>> > >> Kind Regards,
>>> > >> Brandon
>>> > >>
>>> > >> On Fri, Oct 18, 2024 at 4:55 AM Mick Semb Wever 
>>> wrote:
>>> > >> >
>>> > >> > Could we also rename CASSANDRASC to CASSSIDECAR ?
>>> > >> >
>>> > >> > And tbh, i'd much rather CASS-DRIVER-, CASS-ANALYTICS and
>>> > >> CASS-SIDECAR
>>> > >> >  (but ofc it's not really important)
>>> > >> >
>>> > >> >
>>> > >> >
>>> > >> > On Thu, 17 Oct 2024 at 23:11, Štefan Miklošovič <
>>> smikloso...@apache.org>
>>> > >> wrote:
>>> > >> >>
>>> > >> >> 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 the other so CASSANALYTICS be it.
>>> > >> >>
>>> > >> >>
>>> > >> >> On Thu, Oct 17, 2024 at 3:03 PM Jon Haddad <
>>> j...@rustyrazorblade.com>
>>> > >> 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.
>>> > >> >>>
>>> > >> >>> —
>>> > >> >>> Jon Haddad
>>> > >> >>> Rustyrazorblade Consulting
>>> > >> >>> rustyrazorblade.com
>>> > >> >>>
>>> > >> >>>
>>> > >> >>> On Thu, Oct 17, 2024 at 1:57 PM Štefan Miklošovič <
>>> > >> smikloso...@apache.org> wrote:
>>> > >> 
>>> > >>  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 
>>> wrote:
>>> > >> >
>>> > >> > yep. CASSANALYTICS sounds good to me. +1
>>> > >> >
>>> > >> > On Thu, Oct 17, 2024 at 1:45 PM Francisco Guerrero <
>>> > >> fran...@apache.org> 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 wrote:
>>> > >> >> > 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 <
>>> > >> pmcfa...@gmail.com> wrote:
>>> > >> >> >
>>> > >> >> > > I think it needs a bit more blue. Maybe some pink
>>> stripes.
>>> > >> I'll file a
>>> > >> >> > > Jira.
>>> > >> >> > >
>>> > >> >> > > On Thu, Oct 17, 202

Re: [DISCUSS] Modeling JIRA fix version for subprojects

2024-10-18 Thread Jon Haddad
I'm 95% sure it redirects automatically.  I believe those redirects also
work when moving issues from one project to another, so when we move all
the driver issues to their own repos everything should keep working.



On Fri, Oct 18, 2024 at 11:21 AM Francisco Guerrero 
wrote:

> This is one thing that comes to mind.
>
> All of the commits in Sidecar have a reference to the JIRA, if we switch
> it from CASSANDRASC -> CASS-SIDECAR, will there he redirection of
> these tickets? Or will be lose those links and the ability to automatically
> refer to the JIRAs?
>
> On 2024/10/18 18:17:16 Yifan Cai wrote:
> > Anyone know if there are any traps when renaming a JIRA project? Since we
> > are talking about change CASSANDRASC to CASS-SIDECAR.
> >
> >
> > - Yifan
> >
> > On Fri, Oct 18, 2024 at 10:50 AM Patrick McFadin 
> wrote:
> >
> > > Awesome. Now this is the bikeshedding I'm here for. :popcorn:
> > >
> > > On Fri, Oct 18, 2024 at 5:26 AM Brandon Williams 
> wrote:
> > >
> > >> I think for the sidecar we need the dash to avoid the typo-likely
> > >> 'SSS' wart. I have updated INFRA-26212 to follow CASS-DRIVER-.
> > >>
> > >> Kind Regards,
> > >> Brandon
> > >>
> > >> On Fri, Oct 18, 2024 at 4:55 AM Mick Semb Wever 
> wrote:
> > >> >
> > >> > Could we also rename CASSANDRASC to CASSSIDECAR ?
> > >> >
> > >> > And tbh, i'd much rather CASS-DRIVER-, CASS-ANALYTICS and
> > >> CASS-SIDECAR
> > >> >  (but ofc it's not really important)
> > >> >
> > >> >
> > >> >
> > >> > On Thu, 17 Oct 2024 at 23:11, Štefan Miklošovič <
> smikloso...@apache.org>
> > >> wrote:
> > >> >>
> > >> >> 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 the other so CASSANALYTICS be it.
> > >> >>
> > >> >>
> > >> >> On Thu, Oct 17, 2024 at 3:03 PM Jon Haddad <
> j...@rustyrazorblade.com>
> > >> 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.
> > >> >>>
> > >> >>> —
> > >> >>> Jon Haddad
> > >> >>> Rustyrazorblade Consulting
> > >> >>> rustyrazorblade.com
> > >> >>>
> > >> >>>
> > >> >>> On Thu, Oct 17, 2024 at 1:57 PM Štefan Miklošovič <
> > >> smikloso...@apache.org> wrote:
> > >> 
> > >>  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 
> wrote:
> > >> >
> > >> > yep. CASSANALYTICS sounds good to me. +1
> > >> >
> > >> > On Thu, Oct 17, 2024 at 1:45 PM Francisco Guerrero <
> > >> fran...@apache.org> 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 wrote:
> > >> >> > 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 <
> > >> pmcfa...@gmail.com> 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:01 AM Brandon Williams <
> > >> dri...@gmail.com> 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 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 me
> > >> >> > >> >
> > >> >> > >> >
> > >> >> > >> > On Thu, 17 Oct 2024 at 17:50, Abe Ratnofsky <
> a...@aber.io>
> > >> wrote:
> > >> >> > >> >>
> > >> >> > >> >> +1 to CASSDRIVER-JAVA et al.
> > >> >> > >> >>
> > >> >> > >> >> On Oct 17, 2024, at 10:37 AM, Jon Haddad <
> > >> j...@rustyrazorblade.com>
> > >> >> > >> wrote:
> > >> >> > >> >>
> > >> >> > >> >> Sgtm, let’s ship it
> >

Re: [DISCUSS] Modeling JIRA fix version for subprojects

2024-10-18 Thread Štefan Miklošovič
I think that this:

CASS-ANALYTICS

is actually worse than this

CASSANDRA-ANA (or any variation of that).

I would just expand CASS to CASSANDRA everywhere, if we dont, then you are
trying to say that this

CASSANDRA-ANALYTICS

is just too long, but this

CASS-ANALYTICS

isn't.

Right ... got it.



On Fri, Oct 18, 2024 at 1:35 PM Štefan Miklošovič 
wrote:

> So we will have:
>
>
> CASSANDRA
>
> CASS-DRIVER-JAVA
> CASS-DRIVER-GO
>
> CASS-ANALYTICS
>
> CASS-SIDECAR
>
>
> Isn't it weird that you said that we should not save characters at the
> cost of readability while we just use CASS everywhere except the main
> project? Why do you think that having "CASS-" will make people
> automatically think that this is Cassandra related. No other project in
> Apache (afaik) makes the shortcuts like that.
>
> On Fri, Oct 18, 2024 at 1:31 PM Yifan Cai  wrote:
>
>> That is good to know.
>>
>> My preference would be moving the driver projects and analytics first,
>> and renaming the sidecar project later. However, if it is not a concern, I
>> am fine with doing the change in bulk, especially if it is more convenient.
>>
>> - Yifan
>>
>> On Fri, Oct 18, 2024 at 11:24 AM Jon Haddad 
>> wrote:
>>
>>> I'm 95% sure it redirects automatically.  I believe those redirects also
>>> work when moving issues from one project to another, so when we move all
>>> the driver issues to their own repos everything should keep working.
>>>
>>>
>>>
>>> On Fri, Oct 18, 2024 at 11:21 AM Francisco Guerrero 
>>> wrote:
>>>
 This is one thing that comes to mind.

 All of the commits in Sidecar have a reference to the JIRA, if we switch
 it from CASSANDRASC -> CASS-SIDECAR, will there he redirection of
 these tickets? Or will be lose those links and the ability to
 automatically
 refer to the JIRAs?

 On 2024/10/18 18:17:16 Yifan Cai wrote:
 > Anyone know if there are any traps when renaming a JIRA project?
 Since we
 > are talking about change CASSANDRASC to CASS-SIDECAR.
 >
 >
 > - Yifan
 >
 > On Fri, Oct 18, 2024 at 10:50 AM Patrick McFadin 
 wrote:
 >
 > > Awesome. Now this is the bikeshedding I'm here for. :popcorn:
 > >
 > > On Fri, Oct 18, 2024 at 5:26 AM Brandon Williams 
 wrote:
 > >
 > >> I think for the sidecar we need the dash to avoid the typo-likely
 > >> 'SSS' wart. I have updated INFRA-26212 to follow
 CASS-DRIVER-.
 > >>
 > >> Kind Regards,
 > >> Brandon
 > >>
 > >> On Fri, Oct 18, 2024 at 4:55 AM Mick Semb Wever 
 wrote:
 > >> >
 > >> > Could we also rename CASSANDRASC to CASSSIDECAR ?
 > >> >
 > >> > And tbh, i'd much rather CASS-DRIVER-, CASS-ANALYTICS and
 > >> CASS-SIDECAR
 > >> >  (but ofc it's not really important)
 > >> >
 > >> >
 > >> >
 > >> > On Thu, 17 Oct 2024 at 23:11, Štefan Miklošovič <
 smikloso...@apache.org>
 > >> wrote:
 > >> >>
 > >> >> 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 the other so CASSANALYTICS be it.
 > >> >>
 > >> >>
 > >> >> On Thu, Oct 17, 2024 at 3:03 PM Jon Haddad <
 j...@rustyrazorblade.com>
 > >> 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.
 > >> >>>
 > >> >>> —
 > >> >>> Jon Haddad
 > >> >>> Rustyrazorblade Consulting
 > >> >>> rustyrazorblade.com
 > >> >>>
 > >> >>>
 > >> >>> On Thu, Oct 17, 2024 at 1:57 PM Štefan Miklošovič <
 > >> smikloso...@apache.org> wrote:
 > >> 
 > >>  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 
 wrote:
 > >> >
 > >> > yep. CASSANALYTICS sounds good to me. +1
 > >> >
 > >> > On Thu, Oct 17, 2024 at 1:45 PM Francisco Guerrero <
 > >> fran...@apache.org> 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 wrote:
 > >> >> >

Re: [Discuss] Repair inside C*

2024-10-18 Thread Mick Semb Wever
This is looking strong, thanks Jaydeep.

I would suggest folk take a look at the design doc and the PR in the CEP.
A lot is there (that I have completely missed).

I would especially ask all authors of prior art (Reaper, DSE nodesync,
ecchronos)  to take a final review of the proposal

Jaydeep, can we ask for a two week window while we reach out to these
people ?  There's a lot of prior art in this space, and it feels like we're
in a good place now where it's clear this has legs and we can use that to
bring folk in and make sure there's no remaining blindspots.


On Fri, 18 Oct 2024 at 01:40, Jaydeep Chovatia 
wrote:

> 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 <
> chovatia.jayd...@gmail.com> wrote:
>
>> 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 with the best possible design that not only significantly
>> simplifies repair operations but also includes the most common features
>> that everyone will benefit from running at Scale.
>>
>> For example,
>>
>>-
>>
>>Apache Cassandra must be capable of running multiple repair types,
>>such as Full, Incremental, Paxos, and Preview - so the framework should be
>>easily extendable with no additional overhead from the operator’s point of
>>view.
>>-
>>
>>An easy way to extend the token-split calculation algorithm with a
>>default implementation should exist.
>>-
>>
>>Running incremental repair reliably at Scale is pretty challenging,
>>so we need to place safeguards, such as migration/rollback w/o restart and
>>stopping incremental repair automatically if the disk is about to get 
>> full.
>>
>> We are glad to inform you that CEP-37 (i.e., Repair inside Cassandra) is
>> now officially ready for review after multiple rounds of design, testing,
>> code reviews, documentation reviews, and, more importantly, validation that
>> it runs at Scale!
>>
>>
>> Some facts about CEP-37.
>>
>>-
>>
>>Multiple members have verified all aspects of CEP-37 numerous times.
>>-
>>
>>The design proposed in CEP-37 has been thoroughly tried and tested on
>>an immense scale (hundreds of unique Cassandra clusters, tens of thousands
>>of Cassandra nodes, with tens of millions of QPS) on top of 4.1 
>> open-source
>>for more than five years; please see more details here
>>
>> 
>>.
>>-
>>
>>The following presentation
>>
>> 
>>highlights the rigorous applied to CEP-37, which was given during last
>>week’s Apache Cassandra Bay Area Meetup
>>,
>>
>>
>> Since things are massively overhauled, we believe it is almost ready for
>> a final pass pre-VOTE. We would like you to please review the CEP-37
>> 
>> and the associated detailed design doc
>> 
>> .
>>
>> Thank you everyone!
>>
>> Chris, Andy, Josh, Dinesh, Kristijonas, and Jaydeep
>>
>>
>>
>> On Thu, Sep 19, 2024 at 11:26 AM Josh McKenzie 
>> wrote:
>>
>>> Not quite; finishing touches on the CEP and design doc are in flight (as
>>> of last / this week).
>>>
>>> Soon(tm).
>>>
>>> On Thu, Sep 19, 2024, at 2:07 PM, Patrick McFadin wrote:
>>>
>>> Is this CEP ready for a VOTE thread?
>>> https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-37+%28DRAFT%29+Apache+Cassandra+Unified+Repair+Solution
>>>
>>> On Sun, Feb 25, 2024 at 12:25 PM Jaydeep Chovatia <
>>> chovatia.jayd...@gmail.com> wrote:
>>>
>>> Thanks, Josh. I've just updated the CEP
>>> 
>>> and included all the solutions you mentioned below.
>>>
>>> Jaydeep
>>>
>>> On Thu, Feb 22, 2024 at 9:33 AM Josh McKenzie 
>>> wrote:
>>>
>>>
>>> Very late response from me here (basically necro'ing this thread).
>>>
>>> I think it'd be useful to get this condensed into a CEP that we can then
>>> discuss in that format. It's clearly something we all agree we need and
>>> having an implementation that works, even if it's not in your preferred
>>> execution domain, is vastly better than nothing IMO.
>>>
>>> I don't have cycles (nor background ;) ) to do that, but it s

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

2024-10-18 Thread Dinesh Joshi
+1

On Fri, Oct 18, 2024 at 11:09 AM Jon Haddad  wrote:

> +1
>
> On Fri, Oct 18, 2024 at 10:51 AM Bernardo Botella <
> conta...@bernardobotella.com> wrote:
>
>> +1 nb
>>
>> On Oct 17, 2024, at 5:52 PM, Josh McKenzie  wrote:
>>
>> +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,
>> 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
>> > Discussion thread:
>> https://lists.apache.org/thread/8k6njsnvdbmjb6jhyy07o1s7jz8xp1qg
>> >
>> > As per the CEP process documentation, this vote will be open for 72
>> hours (longer if needed).
>> >
>> > Thanks!
>> > James.
>>
>>
>>


Re: [Discuss] Repair inside C*

2024-10-18 Thread Jaydeep Chovatia
Indeed, Mike - two additional weeks is not an issue at all.
Thanks!

Jaydeep


Re: [Discuss] Repair inside C*

2024-10-18 Thread Jaydeep Chovatia
Mick, I am highly sorry to mispronounce your name.

Indeed, Mick  - two additional weeks is not an issue at all.

Jaydeep

On Fri, Oct 18, 2024 at 1:41 PM Jaydeep Chovatia 
wrote:

> Indeed, Mike - two additional weeks is not an issue at all.
> Thanks!
>
> Jaydeep
>


Re: [DISCUSS] Modeling JIRA fix version for subprojects

2024-10-18 Thread Mick Semb Wever
Could we also rename CASSANDRASC to CASSSIDECAR ?

And tbh, i'd much rather CASS-DRIVER-, CASS-ANALYTICS and CASS-SIDECAR
 (but ofc it's not really important)



On Thu, 17 Oct 2024 at 23:11, Štefan Miklošovič 
wrote:

> 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 the other so CASSANALYTICS be it.
>
> On Thu, Oct 17, 2024 at 3:03 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.
>>
>> —
>> Jon Haddad
>> Rustyrazorblade Consulting
>> rustyrazorblade.com
>>
>>
>> On Thu, Oct 17, 2024 at 1:57 PM Štefan Miklošovič 
>> wrote:
>>
>>> 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  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 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 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: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 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 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 <
> j...@rustyrazorblade.com>
> > >> wrote:
> > >> >>
> > >> >> Sgtm, let’s ship it
> > >> >>
> > >> >> +1
> > >> >>
> > >> >>
> > >> >>
> > >> >> On Thu, Oct 17, 2024 at 4:09 AM Brandon Williams <
> dri...@gmail.com>
> > >> 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 Wed, Oct 2, 2024 at 5:07 PM Brandon Williams <
> dri...@gmail.com>
> > >> wrote:
> > >> >>> >
> > >> >>> > I think we just need to ask infra to create the jira
> instances, but
> > >> I
> > >> >>> > guess we need to have some kind of consistent naming scheme
> to help
> > >> >>> > identify them?
> > >> >>> >
> > >> >>> > Kind Regards,
> > >> >>> > Brandon
> > >> >>> >
> > >> >>> > On Wed, Oct 2, 2024 at 1:02 PM Francisco Guerrero <
> > >> fran...@apache.org> wrote:
> > >> >>> > >
> > >> >>> > > +1 too on the points brought by Mick, we need more
> visibility into
> > >> >>> > > subprojects. For starters, we should look into
> integrating Qbot
> > >> >>> > > notifications in #cassandra-dev and #cassandra-noise for
> > >> >>> > > CASSANDRASC tickets. Let me know if I can help with that.
> > >> >>> > >
> > >> >>> > > On 2024/10/02 17:39:28 Yifan Cai wrote:
> > >> >>> > > > +1 on all the points raised by Mick. Please let me know
> if
> > >> there is
> > >> >>> > > > anything I can help with.
> > >> >>> > > >
> > >> >>> > > > - Yifan
> > >> >>> > > >
> > >> >>> > > > On Wed, Oct 2, 2024 at 8:13 AM Josh McKenzie <
> > >> jmcken...@apache.org> wrote:
> > >> >>> > > >
> > >> >>> > > > > - Qbot notifications in #cassandra-dev and
> #cassandra-noise ,
> > >> as well as
> > >> >>> > > > > in any subproject channels
> > >> >>> > > > > - some cadence of dev@ ML updates, e.g. on
> activities, or
> > >> dependency
> > >> >>> > > > > changes, etc
> > >> >