Re: Cassandra PMC Chair Rotation, 2024 Edition

[Jeremy Hanna]

Thanks for being willing to serve in this capacity. Thanks also to Josh for 
doing a lot of this behind the scenes work this past year. 

> On Jun 20, 2024, at 11:22 PM, Maxim Muzafarov  wrote:
> 
> Congratulations Dinesh!
> 
>> On Fri, 21 Jun 2024 at 05:12, Abhijeet Dubey  
>> wrote:
>> 
>> Thank you Josh for the amazing work.
>> 
>> Congrats, Dinesh. Welcome to the new role :)
>> 
>> Regards,
>> Abhijeet
>> 
>>> On Fri, Jun 21, 2024 at 4:09 AM Dinesh Joshi  wrote:
>>> 
>>> Thank you everybody. I hope to do my best in this role. A big thanks to 
>>> Josh who has been a great PMC Chair!
>>> 
>>> On Thu, Jun 20, 2024 at 11:40 AM Yifan Cai  wrote:
 
 Thank you for the service, Josh!
 Congrats, Dinesh!
 
 On Thu, Jun 20, 2024 at 11:32 AM Jean-Armel Luce  
 wrote:
> 
> Josh, thanks for the job
> Dinesh, congrats!!
> 
> Le jeu. 20 juin 2024 à 19:42, David Capwell  a écrit :
>> 
>> Congrats!
>> 
>> On Jun 20, 2024, at 9:10 AM, Melissa Logan  wrote:
>> 
>> Josh, thank you for your time as chair + congrats Dinesh!
>> 
>> On Thu, Jun 20, 2024 at 9:08 AM Abe Ratnofsky  wrote:
>>> 
>>> Congrats Dinesh! Thank you Josh!
>>> 
>>> On Jun 20, 2024, at 11:53 AM, Jeremiah Jordan 
>>>  wrote:
>>> 
>>> Welcome to the Chair role Dinesh!  Congrats!
>>> 
>>> On Jun 20, 2024 at 10:50:37 AM, Josh McKenzie  
>>> wrote:
 
 Another PMC Chair baton pass incoming! On behalf of the Apache 
 Cassandra Project Management Committee (PMC) I would like to welcome 
 and congratulate our next PMC Chair Dinesh Joshi (djoshi).
 
 Dinesh has been a member of the PMC for a few years now and many of 
 you likely know him from his thoughtful, measured presence on many of 
 our collective discussions as we've grown and evolved over the past 
 few years.
 
 I appreciate the project trusting me as liaison with the board over 
 the past year and look forward to supporting Dinesh in the role in the 
 future.
 
 Repeating Mick (repeating Paulo's) words from last year: The chair is 
 an administrative position that interfaces with the Apache Software 
 Foundation Board, by submitting regular reports about project status 
 and health. Read more about the PMC chair role on Apache projects:
 - https://www.apache.org/foundation/how-it-works.html#pmc
 - https://www.apache.org/foundation/how-it-works.html#pmc-chair
 - 
 https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers
 
 The PMC as a whole is the entity that oversees and leads the project 
 and any PMC member can be approached as a representative of the 
 committee. A list of Apache Cassandra PMC members can be found on: 
 https://cassandra.apache.org/_/community.html
>>> 
>>> 
>> 
>> 
>> 
>> --
>> Abhijeet Dubey
>> Software Engineer @ Apple Inc.
>> IIT Bombay Computer Science & Engineering Class of 2019
>> Apple Inc. | IIT Bombay

Re: Cassandra PMC Chair Rotation, 2024 Edition

[Maxim Muzafarov]

Congratulations Dinesh!

On Fri, 21 Jun 2024 at 05:12, Abhijeet Dubey  wrote:
>
> Thank you Josh for the amazing work.
>
> Congrats, Dinesh. Welcome to the new role :)
>
> Regards,
> Abhijeet
>
> On Fri, Jun 21, 2024 at 4:09 AM Dinesh Joshi  wrote:
>>
>> Thank you everybody. I hope to do my best in this role. A big thanks to Josh 
>> who has been a great PMC Chair!
>>
>> On Thu, Jun 20, 2024 at 11:40 AM Yifan Cai  wrote:
>>>
>>> Thank you for the service, Josh!
>>> Congrats, Dinesh!
>>>
>>> On Thu, Jun 20, 2024 at 11:32 AM Jean-Armel Luce  wrote:

 Josh, thanks for the job
 Dinesh, congrats!!

 Le jeu. 20 juin 2024 à 19:42, David Capwell  a écrit :
>
> Congrats!
>
> On Jun 20, 2024, at 9:10 AM, Melissa Logan  wrote:
>
> Josh, thank you for your time as chair + congrats Dinesh!
>
> On Thu, Jun 20, 2024 at 9:08 AM Abe Ratnofsky  wrote:
>>
>> Congrats Dinesh! Thank you Josh!
>>
>> On Jun 20, 2024, at 11:53 AM, Jeremiah Jordan 
>>  wrote:
>>
>> Welcome to the Chair role Dinesh!  Congrats!
>>
>> On Jun 20, 2024 at 10:50:37 AM, Josh McKenzie  
>> wrote:
>>>
>>> Another PMC Chair baton pass incoming! On behalf of the Apache 
>>> Cassandra Project Management Committee (PMC) I would like to welcome 
>>> and congratulate our next PMC Chair Dinesh Joshi (djoshi).
>>>
>>> Dinesh has been a member of the PMC for a few years now and many of you 
>>> likely know him from his thoughtful, measured presence on many of our 
>>> collective discussions as we've grown and evolved over the past few 
>>> years.
>>>
>>> I appreciate the project trusting me as liaison with the board over the 
>>> past year and look forward to supporting Dinesh in the role in the 
>>> future.
>>>
>>> Repeating Mick (repeating Paulo's) words from last year: The chair is 
>>> an administrative position that interfaces with the Apache Software 
>>> Foundation Board, by submitting regular reports about project status 
>>> and health. Read more about the PMC chair role on Apache projects:
>>> - https://www.apache.org/foundation/how-it-works.html#pmc
>>> - https://www.apache.org/foundation/how-it-works.html#pmc-chair
>>> - https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers
>>>
>>> The PMC as a whole is the entity that oversees and leads the project 
>>> and any PMC member can be approached as a representative of the 
>>> committee. A list of Apache Cassandra PMC members can be found on: 
>>> https://cassandra.apache.org/_/community.html
>>
>>
>
>
>
> --
> Abhijeet Dubey
> Software Engineer @ Apple Inc.
> IIT Bombay Computer Science & Engineering Class of 2019
> Apple Inc. | IIT Bombay

Re: [DISCUSS] Increments on non-existent rows in Accord

[Caleb Rackliffe]

It does, but the primary reason it does is that it is setting a value, not incrementing one. When we’re setting a value, we don’t care what was there before. Incrementing a value is not possible in a non-transitional update, hence this thread…On Jun 20, 2024, at 5:17 PM, Bernardo Botella  wrote:Doesn’t an UPDATE statement creates a row if the partition key does not exist? That’s also confirmed by the official Cassandra documentation here:”Unlike in SQL, UPDATE does not check the prior existence of the row by default. The row is created if none existed before, and updated otherwise. Furthermore, there is no means of knowing which action occurred.”That being the case, I think the second option you mention is what keeps consistency with the UPDATEs out of the transaction.Kind regards,BernardoOn Jun 20, 2024, at 1:54 PM, Caleb Rackliffe  wrote:We had a bug report a while back from Luis E Fernandez and team in CASSANDRA-18988 around the behavior of increments/decrements on numeric fields for non-existent rows. Consider the following, wich can be run on the cep-15-accord branch:CREATE KEYSPACE accord WITH replication = {'class': 'SimpleStrategy', 'replication_factor': '1'} AND durable_writes = trueCREATE TABLE accord.accounts (
    partition text,
    account_id int,
    balance int,
    PRIMARY KEY (partition, account_id)
) WITH CLUSTERING ORDER BY (account_id ASC) AND transactional_mode='full'BEGIN TRANSACTION
INSERT INTO accord.accounts (partition, account_id, balance) VALUES ('default', 0, 100);
INSERT INTO accord.accounts (partition, account_id, balance) VALUES ('default', 1, 100);
COMMIT TRANSACTIONBEGIN TRANSACTION
UPDATE accord.accounts SET balance -= 10 WHERE partition = 'default' AND account_id = 1;
UPDATE accord.accounts SET balance += 10 WHERE partition = 'default' AND account_id = 3;
COMMIT TRANSACTIONReading the 'default' partition will produce the following result. partition | account_id | balance
---++-
   default |          0 |     100
   default |          1 |      90As you will notice, we have not implicitly inserted a row for account_id 3, which does not exist when we request that its balance be incremented by 10. This is by design, as null + 10 == null.Before I close CASSANDRA-18988, I'd like to confirm with everyone reading this that the behavior above is reasonable. The only other option I've seen proposed that would make sense is perhaps producing a result like: partition | account_id | balance
---++-
   default |          0 |     100
   default |          1 |      90   default |          3 |    nullNote however that this is exactly what we would produce if we had first inserted a row w/ no value for balance:INSERT INTO accord.accounts (partition, account_id) VALUES ('default', 3);

Re: Cassandra PMC Chair Rotation, 2024 Edition

[Abhijeet Dubey]

Thank you Josh for the amazing work.

Congrats, Dinesh. Welcome to the new role :)

Regards,
Abhijeet

On Fri, Jun 21, 2024 at 4:09 AM Dinesh Joshi  wrote:

> Thank you everybody. I hope to do my best in this role. A big thanks to
> Josh who has been a great PMC Chair!
>
> On Thu, Jun 20, 2024 at 11:40 AM Yifan Cai  wrote:
>
>> Thank you for the service, Josh!
>> Congrats, Dinesh!
>>
>> On Thu, Jun 20, 2024 at 11:32 AM Jean-Armel Luce 
>> wrote:
>>
>>> Josh, thanks for the job
>>> Dinesh, congrats!!
>>>
>>> Le jeu. 20 juin 2024 à 19:42, David Capwell  a
>>> écrit :
>>>
 Congrats!

 On Jun 20, 2024, at 9:10 AM, Melissa Logan 
 wrote:

 Josh, thank you for your time as chair + congrats Dinesh!

 On Thu, Jun 20, 2024 at 9:08 AM Abe Ratnofsky  wrote:

> Congrats Dinesh! Thank you Josh!
>
> On Jun 20, 2024, at 11:53 AM, Jeremiah Jordan <
> jeremiah.jor...@gmail.com> wrote:
>
> Welcome to the Chair role Dinesh!  Congrats!
>
> On Jun 20, 2024 at 10:50:37 AM, Josh McKenzie 
> wrote:
>
>> Another PMC Chair baton pass incoming! On behalf of the Apache
>> Cassandra Project Management Committee (PMC) I would like to welcome and
>> congratulate our next PMC Chair Dinesh Joshi (djoshi).
>>
>> Dinesh has been a member of the PMC for a few years now and many of
>> you likely know him from his thoughtful, measured presence on many of our
>> collective discussions as we've grown and evolved over the past few 
>> years.
>>
>> I appreciate the project trusting me as liaison with the board over
>> the past year and look forward to supporting Dinesh in the role in the
>> future.
>>
>> Repeating Mick (repeating Paulo's) words from last year: The chair is
>> an administrative position that interfaces with the Apache Software
>> Foundation Board, by submitting regular reports about project status and
>> health. Read more about the PMC chair role on Apache projects:
>> - https://www.apache.org/foundation/how-it-works.html#pmc
>> - https://www.apache.org/foundation/how-it-works.html#pmc-chair
>> -
>> https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers
>>
>> The PMC as a whole is the entity that oversees and leads the project
>> and any PMC member can be approached as a representative of the 
>> committee.
>> A list of Apache Cassandra PMC members can be found on:
>> https://cassandra.apache.org/_/community.html
>>
>
>


-- 
*Abhijeet Dubey*
Software Engineer @ Apple Inc.
IIT Bombay Computer Science & Engineering Class of 2019
Apple Inc. | IIT Bombay

Re: Cassandra PMC Chair Rotation, 2024 Edition

[Dinesh Joshi]

Thank you everybody. I hope to do my best in this role. A big thanks to
Josh who has been a great PMC Chair!

On Thu, Jun 20, 2024 at 11:40 AM Yifan Cai  wrote:

> Thank you for the service, Josh!
> Congrats, Dinesh!
>
> On Thu, Jun 20, 2024 at 11:32 AM Jean-Armel Luce 
> wrote:
>
>> Josh, thanks for the job
>> Dinesh, congrats!!
>>
>> Le jeu. 20 juin 2024 à 19:42, David Capwell  a
>> écrit :
>>
>>> Congrats!
>>>
>>> On Jun 20, 2024, at 9:10 AM, Melissa Logan 
>>> wrote:
>>>
>>> Josh, thank you for your time as chair + congrats Dinesh!
>>>
>>> On Thu, Jun 20, 2024 at 9:08 AM Abe Ratnofsky  wrote:
>>>
 Congrats Dinesh! Thank you Josh!

 On Jun 20, 2024, at 11:53 AM, Jeremiah Jordan <
 jeremiah.jor...@gmail.com> wrote:

 Welcome to the Chair role Dinesh!  Congrats!

 On Jun 20, 2024 at 10:50:37 AM, Josh McKenzie 
 wrote:

> Another PMC Chair baton pass incoming! On behalf of the Apache
> Cassandra Project Management Committee (PMC) I would like to welcome and
> congratulate our next PMC Chair Dinesh Joshi (djoshi).
>
> Dinesh has been a member of the PMC for a few years now and many of
> you likely know him from his thoughtful, measured presence on many of our
> collective discussions as we've grown and evolved over the past few years.
>
> I appreciate the project trusting me as liaison with the board over
> the past year and look forward to supporting Dinesh in the role in the
> future.
>
> Repeating Mick (repeating Paulo's) words from last year: The chair is
> an administrative position that interfaces with the Apache Software
> Foundation Board, by submitting regular reports about project status and
> health. Read more about the PMC chair role on Apache projects:
> - https://www.apache.org/foundation/how-it-works.html#pmc
> - https://www.apache.org/foundation/how-it-works.html#pmc-chair
> -
> https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers
>
> The PMC as a whole is the entity that oversees and leads the project
> and any PMC member can be approached as a representative of the committee.
> A list of Apache Cassandra PMC members can be found on:
> https://cassandra.apache.org/_/community.html
>


>>>

Re: [DISCUSS] Increments on non-existent rows in Accord

[Bernardo Botella]

Doesn’t an UPDATE statement creates a row if the partition key does not exist? 
That’s also confirmed by the official Cassandra documentation here 
:

”Unlike in SQL, UPDATE does not check the prior existence of the row by 
default. The row is created if none existed before, and updated otherwise. 
Furthermore, there is no means of knowing which action occurred.”

That being the case, I think the second option you mention is what keeps 
consistency with the UPDATEs out of the transaction.

Kind regards,
Bernardo

> On Jun 20, 2024, at 1:54 PM, Caleb Rackliffe  wrote:
> 
> We had a bug report a while back from Luis E Fernandez and team in 
> CASSANDRA-18988  
> around the behavior of increments/decrements on numeric fields for 
> non-existent rows. Consider the following, wich can be run on the 
> cep-15-accord branch:
> 
> CREATE KEYSPACE accord WITH replication = {'class': 'SimpleStrategy', 
> 'replication_factor': '1'} AND durable_writes = true
> 
> CREATE TABLE accord.accounts (
> partition text,
> account_id int,
> balance int,
> PRIMARY KEY (partition, account_id)
> ) WITH CLUSTERING ORDER BY (account_id ASC) AND transactional_mode='full'
> 
> BEGIN TRANSACTION
> INSERT INTO accord.accounts (partition, account_id, balance) VALUES 
> ('default', 0, 100);
> INSERT INTO accord.accounts (partition, account_id, balance) VALUES 
> ('default', 1, 100);
> COMMIT TRANSACTION
> 
> BEGIN TRANSACTION
> UPDATE accord.accounts SET balance -= 10 WHERE partition = 'default' AND 
> account_id = 1;
> UPDATE accord.accounts SET balance += 10 WHERE partition = 'default' AND 
> account_id = 3;
> COMMIT TRANSACTION
> 
> Reading the 'default' partition will produce the following result.
> 
>  partition | account_id | balance
> ---++-
>default |  0 | 100
>default |  1 |  90
> 
> As you will notice, we have not implicitly inserted a row for account_id 3, 
> which does not exist when we request that its balance be incremented by 10. 
> This is by design, as null + 10 == null.
> 
> Before I close CASSANDRA-18988 
> , I'd like to confirm 
> with everyone reading this that the behavior above is reasonable. The only 
> other option I've seen proposed that would make sense is perhaps producing a 
> result like:
> 
>  partition | account_id | balance
> ---++-
>default |  0 | 100
>default |  1 |  90
>default |  3 |null
> 
> 
> Note however that this is exactly what we would produce if we had first 
> inserted a row w/ no value for balance:
> 
> INSERT INTO accord.accounts (partition, account_id) VALUES ('default', 3);

[DISCUSS] Increments on non-existent rows in Accord

[Caleb Rackliffe]

We had a bug report a while back from Luis E Fernandez and team in
CASSANDRA-18988 
around the behavior of increments/decrements on numeric fields for
non-existent rows. Consider the following, wich can be run on the
cep-15-accord branch:

CREATE KEYSPACE accord WITH replication = {'class': 'SimpleStrategy',
'replication_factor': '1'} AND durable_writes = true


CREATE TABLE accord.accounts (
partition text,
account_id int,
balance int,
PRIMARY KEY (partition, account_id)
) WITH CLUSTERING ORDER BY (account_id ASC) AND transactional_mode='full'


BEGIN TRANSACTION
INSERT INTO accord.accounts (partition, account_id, balance)
VALUES ('default', 0, 100);
INSERT INTO accord.accounts (partition, account_id, balance)
VALUES ('default', 1, 100);
COMMIT TRANSACTION


BEGIN TRANSACTION
UPDATE accord.accounts SET balance -= 10 WHERE partition =
'default' AND account_id = 1;
UPDATE accord.accounts SET balance += 10 WHERE partition =
'default' AND account_id = 3;
COMMIT TRANSACTION


Reading the 'default' partition will produce the following result.


 partition | account_id | balance
---++-
   default |  0 | 100
   default |  1 |  90


As you will notice, we have not implicitly inserted a row for
account_id 3, which does not exist when we request that its balance be
incremented by 10. This is by design, as null + 10 == null.


Before I close CASSANDRA-18988
, *I'd like to
confirm with everyone reading this that the behavior above is
reasonable*. The only other option I've seen proposed that would make
sense is perhaps producing a result like:


 partition | account_id | balance
---++-
   default |  0 | 100
   default |  1 |  90

   default |  3 |null



Note however that this is exactly what we would produce if we had
first inserted a row w/ no value for balance:


INSERT INTO accord.accounts (partition, account_id) VALUES ('default', 3);

Re: Cassandra PMC Chair Rotation, 2024 Edition

[Mick Semb Wever]

Thank you Josh for being an amazing VP.  The past year has been very
transformative for the project and you've done a ton of critical work
behind the scenes that few know about.

Welcome Dinesh!



On Thu, 20 Jun 2024 at 17:53, Josh McKenzie  wrote:

> Another PMC Chair baton pass incoming! On behalf of the Apache Cassandra
> Project Management Committee (PMC) I would like to welcome and congratulate
> our next PMC Chair Dinesh Joshi (djoshi).
>
> Dinesh has been a member of the PMC for a few years now and many of you
> likely know him from his thoughtful, measured presence on many of our
> collective discussions as we've grown and evolved over the past few years.
>
> I appreciate the project trusting me as liaison with the board over the
> past year and look forward to supporting Dinesh in the role in the future.
>
> Repeating Mick (repeating Paulo's) words from last year: The chair is an
> administrative position that interfaces with the Apache Software Foundation
> Board, by submitting regular reports about project status and health. Read
> more about the PMC chair role on Apache projects:
> - https://www.apache.org/foundation/how-it-works.html#pmc
> - https://www.apache.org/foundation/how-it-works.html#pmc-chair
> - https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers
>
> The PMC as a whole is the entity that oversees and leads the project and
> any PMC member can be approached as a representative of the committee. A
> list of Apache Cassandra PMC members can be found on:
> https://cassandra.apache.org/_/community.html
>

Re: Suggestions for CASSANDRA-18078

[Mick Semb Wever]

On Thu, 20 Jun 2024 at 18:46, Štefan Miklošovič 
wrote:

> List,
>
> we need your opinions about CASSANDRA-18078.
>
> That ticket is about the removal of MAXWRITETIME function which was added
> in CASSANDRA-17425 and firstly introduced in 5.0-alpha1.
>
> This function was identified to be redundant in favor of CASSANDRA-8877
> and CASSANDRA-18060.
>
> The idea of the removal was welcomed and the patch was prepared doing so
> but it was never delivered and the question what to do with it, in
> connection with 5.0.0, still remains.
>
> The options are:
>
> 1) since 18078 was never released in GA, there is still time to remove it.
> 2) it is too late for the removal hence we would keep it in 5.0.0 and we
> would deprecate it in 5.0.1 and remove it in trunk.
>
> It is worth to say that there is a precedent in 2), in CASSANDRA-17495,
> where it was the very same scenario. A guardrail was introduced in alpha1.
> We decided to release and deprecate in 5.0.1 and remove in trunk. The same
> might be applied here, however we would like to have it confirmed if this
> is indeed the case or we prefer to just go with 1) and be done with it.
>


Option (2) is my vote.

Rationale: it's our agreed guidelines, we say it hasn't been released but
that's not accurate as we consider betas releases in this context.  It's
also the correct approach to take that we shouldn't ever try to avoid.  It
should never be a big deal to deal with a deprecate cycle regardless of how
likely we think it isn't needed.   I think this is especially true when we
are right at the cusp of cutting 5.0-rc1, and effectively been in rc mode
for a while now.  (Yifan's comment hits this point on – not ever rush
something at the last minute.)

But I also have no objections if a waiver to our release lifecycle is
agreed upon. Let common sense prevail – I haven't personally dug into the
issue.

Re: Cassandra PMC Chair Rotation, 2024 Edition

[Jacek Lewandowski]

Congratulations!!!


- - -- --- -  -
Jacek Lewandowski


czw., 20 cze 2024 o 21:00 lorinapoland  napisał(a):

> Congrats, Dinesh!
>
>
>
> Sent from my Verizon, Samsung Galaxy smartphone
>
>
>  Original message 
> From: Josh McKenzie 
> Date: 6/20/24 08:51 (GMT-08:00)
> To: dev 
> Subject: Cassandra PMC Chair Rotation, 2024 Edition
>
> Another PMC Chair baton pass incoming! On behalf of the Apache Cassandra
> Project Management Committee (PMC) I would like to welcome and congratulate
> our next PMC Chair Dinesh Joshi (djoshi).
>
> Dinesh has been a member of the PMC for a few years now and many of you
> likely know him from his thoughtful, measured presence on many of our
> collective discussions as we've grown and evolved over the past few years.
>
> I appreciate the project trusting me as liaison with the board over the
> past year and look forward to supporting Dinesh in the role in the future.
>
> Repeating Mick (repeating Paulo's) words from last year: The chair is an
> administrative position that interfaces with the Apache Software Foundation
> Board, by submitting regular reports about project status and health. Read
> more about the PMC chair role on Apache projects:
> - https://www.apache.org/foundation/how-it-works.html#pmc
> - https://www.apache.org/foundation/how-it-works.html#pmc-chair
> - https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers
>
> The PMC as a whole is the entity that oversees and leads the project and
> any PMC member can be approached as a representative of the committee. A
> list of Apache Cassandra PMC members can be found on:
> https://cassandra.apache.org/_/community.html
>

RE: Cassandra PMC Chair Rotation, 2024 Edition

[lorinapoland]

Congrats, Dinesh!Sent from my Verizon, Samsung Galaxy smartphone
 Original message From: Josh McKenzie  
Date: 6/20/24  08:51  (GMT-08:00) To: dev  Subject: 
Cassandra PMC Chair Rotation, 2024 Edition Another PMC Chair baton pass 
incoming! On behalf of the Apache Cassandra Project Management Committee (PMC) 
I would like to welcome and congratulate our next PMC Chair Dinesh Joshi 
(djoshi).Dinesh has been a member of the PMC for a few years now and many of 
you likely know him from his thoughtful, measured presence on many of our 
collective discussions as we've grown and evolved over the past few years.I 
appreciate the project trusting me as liaison with the board over the past year 
and look forward to supporting Dinesh in the role in the future.Repeating Mick 
(repeating Paulo's) words from last year: The chair is an administrative 
position that interfaces with the Apache Software Foundation Board, by 
submitting regular reports about project status and health. Read more about the 
PMC chair role on Apache projects:- 
https://www.apache.org/foundation/how-it-works.html#pmc- 
https://www.apache.org/foundation/how-it-works.html#pmc-chair- 
https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officersThe PMC 
as a whole is the entity that oversees and leads the project and any PMC member 
can be approached as a representative of the committee. A list of Apache 
Cassandra PMC members can be found on: 
https://cassandra.apache.org/_/community.html

Re: Cassandra PMC Chair Rotation, 2024 Edition

[Yifan Cai]

Thank you for the service, Josh!
Congrats, Dinesh!

On Thu, Jun 20, 2024 at 11:32 AM Jean-Armel Luce  wrote:

> Josh, thanks for the job
> Dinesh, congrats!!
>
> Le jeu. 20 juin 2024 à 19:42, David Capwell  a écrit :
>
>> Congrats!
>>
>> On Jun 20, 2024, at 9:10 AM, Melissa Logan  wrote:
>>
>> Josh, thank you for your time as chair + congrats Dinesh!
>>
>> On Thu, Jun 20, 2024 at 9:08 AM Abe Ratnofsky  wrote:
>>
>>> Congrats Dinesh! Thank you Josh!
>>>
>>> On Jun 20, 2024, at 11:53 AM, Jeremiah Jordan 
>>> wrote:
>>>
>>> Welcome to the Chair role Dinesh!  Congrats!
>>>
>>> On Jun 20, 2024 at 10:50:37 AM, Josh McKenzie 
>>> wrote:
>>>
 Another PMC Chair baton pass incoming! On behalf of the Apache
 Cassandra Project Management Committee (PMC) I would like to welcome and
 congratulate our next PMC Chair Dinesh Joshi (djoshi).

 Dinesh has been a member of the PMC for a few years now and many of you
 likely know him from his thoughtful, measured presence on many of our
 collective discussions as we've grown and evolved over the past few years.

 I appreciate the project trusting me as liaison with the board over the
 past year and look forward to supporting Dinesh in the role in the future.

 Repeating Mick (repeating Paulo's) words from last year: The chair is
 an administrative position that interfaces with the Apache Software
 Foundation Board, by submitting regular reports about project status and
 health. Read more about the PMC chair role on Apache projects:
 - https://www.apache.org/foundation/how-it-works.html#pmc
 - https://www.apache.org/foundation/how-it-works.html#pmc-chair
 -
 https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers

 The PMC as a whole is the entity that oversees and leads the project
 and any PMC member can be approached as a representative of the committee.
 A list of Apache Cassandra PMC members can be found on:
 https://cassandra.apache.org/_/community.html

>>>
>>>
>>

Re: Cassandra PMC Chair Rotation, 2024 Edition

[Jean-Armel Luce]

Josh, thanks for the job
Dinesh, congrats!!

Le jeu. 20 juin 2024 à 19:42, David Capwell  a écrit :

> Congrats!
>
> On Jun 20, 2024, at 9:10 AM, Melissa Logan  wrote:
>
> Josh, thank you for your time as chair + congrats Dinesh!
>
> On Thu, Jun 20, 2024 at 9:08 AM Abe Ratnofsky  wrote:
>
>> Congrats Dinesh! Thank you Josh!
>>
>> On Jun 20, 2024, at 11:53 AM, Jeremiah Jordan 
>> wrote:
>>
>> Welcome to the Chair role Dinesh!  Congrats!
>>
>> On Jun 20, 2024 at 10:50:37 AM, Josh McKenzie 
>> wrote:
>>
>>> Another PMC Chair baton pass incoming! On behalf of the Apache Cassandra
>>> Project Management Committee (PMC) I would like to welcome and congratulate
>>> our next PMC Chair Dinesh Joshi (djoshi).
>>>
>>> Dinesh has been a member of the PMC for a few years now and many of you
>>> likely know him from his thoughtful, measured presence on many of our
>>> collective discussions as we've grown and evolved over the past few years.
>>>
>>> I appreciate the project trusting me as liaison with the board over the
>>> past year and look forward to supporting Dinesh in the role in the future.
>>>
>>> Repeating Mick (repeating Paulo's) words from last year: The chair is an
>>> administrative position that interfaces with the Apache Software Foundation
>>> Board, by submitting regular reports about project status and health. Read
>>> more about the PMC chair role on Apache projects:
>>> - https://www.apache.org/foundation/how-it-works.html#pmc
>>> - https://www.apache.org/foundation/how-it-works.html#pmc-chair
>>> - https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers
>>>
>>> The PMC as a whole is the entity that oversees and leads the project and
>>> any PMC member can be approached as a representative of the committee. A
>>> list of Apache Cassandra PMC members can be found on:
>>> https://cassandra.apache.org/_/community.html
>>>
>>
>>
>

Re: Suggestions for CASSANDRA-18078

[Yifan Cai]

I am voting against this for now.

There is an unaddressed gap between the functions. I do not believe there
is an equivalent replacement for the MAXWRITETIME function already, which
will disrupt its adopters.

MAXWRITETIME handles both single value columns and collections as input.
Meanwhile, COLLECTION_MAX(WRITETIME(..)) only applies to collections. There
is CASSANDRA-18085 aims to extend COLLECTION_MAX to non-collection values.
After merging CASSANDRA-18085, then we have a true replacement and can
remove MAXWRITETIME.

- Yifan

On Thu, Jun 20, 2024 at 10:32 AM Jon Haddad  wrote:

> Agreed. If we release it, we can’t remove it after. Option 2 is off the
> table.
>
> —
> Jon Haddad
> Rustyrazorblade Consulting
> rustyrazorblade.com
>
>
> On Thu, Jun 20, 2024 at 7:13 PM Jeff Jirsa  wrote:
>
>> If we have a public-facing API that we’re contemplating releasing to the
>> public, and we don’t think it’s needed, we should remove it before it’s
>> launched and we’re stuck with it forever.
>>
>>
>>
>>
>> On Jun 20, 2024, at 9:55 AM, Jeremiah Jordan 
>> wrote:
>>
>> +1 from me for 1, just remove it now.
>> I think this case is different from CASSANDRA-19556/CASSANDRA-17425.  The
>> new guardrail from 19556 which would deprecate the 17425 has not been
>> committed yet.  In the case of MAXWRITETIME the replacement is already in
>> the code, we just didn’t remove MAXWRITETIME yet.
>>
>> Jeremiah Jordan
>> e. jerem...@datastax.com
>> w. www.datastax.com
>>
>>
>>
>> On Jun 20, 2024 at 11:46:08 AM, Štefan Miklošovič 
>> wrote:
>>
>>> List,
>>>
>>> we need your opinions about CASSANDRA-18078.
>>>
>>> That ticket is about the removal of MAXWRITETIME function which was
>>> added in CASSANDRA-17425 and firstly introduced in 5.0-alpha1.
>>>
>>> This function was identified to be redundant in favor of CASSANDRA-8877
>>> and CASSANDRA-18060.
>>>
>>> The idea of the removal was welcomed and the patch was prepared doing so
>>> but it was never delivered and the question what to do with it, in
>>> connection with 5.0.0, still remains.
>>>
>>> The options are:
>>>
>>> 1) since 18078 was never released in GA, there is still time to remove
>>> it.
>>> 2) it is too late for the removal hence we would keep it in 5.0.0 and we
>>> would deprecate it in 5.0.1 and remove it in trunk.
>>>
>>> It is worth to say that there is a precedent in 2), in CASSANDRA-17495,
>>> where it was the very same scenario. A guardrail was introduced in alpha1.
>>> We decided to release and deprecate in 5.0.1 and remove in trunk. The same
>>> might be applied here, however we would like to have it confirmed if this
>>> is indeed the case or we prefer to just go with 1) and be done with it.
>>>
>>> Regards
>>>
>>
>>

Re: Suggestions for CASSANDRA-18078

[Jon Haddad]

Agreed. If we release it, we can’t remove it after. Option 2 is off the
table.

—
Jon Haddad
Rustyrazorblade Consulting
rustyrazorblade.com


On Thu, Jun 20, 2024 at 7:13 PM Jeff Jirsa  wrote:

> If we have a public-facing API that we’re contemplating releasing to the
> public, and we don’t think it’s needed, we should remove it before it’s
> launched and we’re stuck with it forever.
>
>
>
>
> On Jun 20, 2024, at 9:55 AM, Jeremiah Jordan 
> wrote:
>
> +1 from me for 1, just remove it now.
> I think this case is different from CASSANDRA-19556/CASSANDRA-17425.  The
> new guardrail from 19556 which would deprecate the 17425 has not been
> committed yet.  In the case of MAXWRITETIME the replacement is already in
> the code, we just didn’t remove MAXWRITETIME yet.
>
> Jeremiah Jordan
> e. jerem...@datastax.com
> w. www.datastax.com
>
>
>
> On Jun 20, 2024 at 11:46:08 AM, Štefan Miklošovič 
> wrote:
>
>> List,
>>
>> we need your opinions about CASSANDRA-18078.
>>
>> That ticket is about the removal of MAXWRITETIME function which was added
>> in CASSANDRA-17425 and firstly introduced in 5.0-alpha1.
>>
>> This function was identified to be redundant in favor of CASSANDRA-8877
>> and CASSANDRA-18060.
>>
>> The idea of the removal was welcomed and the patch was prepared doing so
>> but it was never delivered and the question what to do with it, in
>> connection with 5.0.0, still remains.
>>
>> The options are:
>>
>> 1) since 18078 was never released in GA, there is still time to remove it.
>> 2) it is too late for the removal hence we would keep it in 5.0.0 and we
>> would deprecate it in 5.0.1 and remove it in trunk.
>>
>> It is worth to say that there is a precedent in 2), in CASSANDRA-17495,
>> where it was the very same scenario. A guardrail was introduced in alpha1.
>> We decided to release and deprecate in 5.0.1 and remove in trunk. The same
>> might be applied here, however we would like to have it confirmed if this
>> is indeed the case or we prefer to just go with 1) and be done with it.
>>
>> Regards
>>
>
>

Re: Suggestions for CASSANDRA-18078

[Jeff Jirsa]

If we have a public-facing API that we’re contemplating releasing to the 
public, and we don’t think it’s needed, we should remove it before it’s 
launched and we’re stuck with it forever. 




> On Jun 20, 2024, at 9:55 AM, Jeremiah Jordan  wrote:
> 
> +1 from me for 1, just remove it now.
> I think this case is different from CASSANDRA-19556/CASSANDRA-17425.  The new 
> guardrail from 19556 which would deprecate the 17425 has not been committed 
> yet.  In the case of MAXWRITETIME the replacement is already in the code, we 
> just didn’t remove MAXWRITETIME yet.
> 
> Jeremiah Jordan
> e. jerem...@datastax.com 
> w. www.datastax.com 
> 
> 
> 
> On Jun 20, 2024 at 11:46:08 AM, Štefan Miklošovič  > wrote:
>> List,
>> 
>> we need your opinions about CASSANDRA-18078.
>> 
>> That ticket is about the removal of MAXWRITETIME function which was added in 
>> CASSANDRA-17425 and firstly introduced in 5.0-alpha1.
>> 
>> This function was identified to be redundant in favor of CASSANDRA-8877 and 
>> CASSANDRA-18060.
>> 
>> The idea of the removal was welcomed and the patch was prepared doing so but 
>> it was never delivered and the question what to do with it, in connection 
>> with 5.0.0, still remains.
>> 
>> The options are:
>> 
>> 1) since 18078 was never released in GA, there is still time to remove it.
>> 2) it is too late for the removal hence we would keep it in 5.0.0 and we 
>> would deprecate it in 5.0.1 and remove it in trunk.
>> 
>> It is worth to say that there is a precedent in 2), in CASSANDRA-17495, 
>> where it was the very same scenario. A guardrail was introduced in alpha1. 
>> We decided to release and deprecate in 5.0.1 and remove in trunk. The same 
>> might be applied here, however we would like to have it confirmed if this is 
>> indeed the case or we prefer to just go with 1) and be done with it.
>> 
>> Regards

Re: Cassandra PMC Chair Rotation, 2024 Edition

[Tolbert, Andy]

🎉 congrats Dinesh and thank you Josh!


On Thu, Jun 20, 2024 at 11:54 AM Ekaterina Dimitrova 
wrote:

> Thank you, Josh, and congrats, Dinesh! 🥳
>
> On Thu, 20 Jun 2024 at 19:44, Joseph Lynch  wrote:
>
>> This is exciting news!!
>>
>> Congratulations Dinesh and thank you for taking on this role!  Also thank
>> you to Josh for taking the role this year!
>>
>> -Joey
>>
>> On Thu, Jun 20, 2024 at 12:39 PM Rahul Xavier Singh <
>> rahul.xavier.si...@gmail.com> wrote:
>>
>>> Congrats Dinesh!
>>>
>>> On Thu, Jun 20, 2024 at 12:27 PM Francisco Guerrero 
>>> wrote:
>>>
 Thanks Josh for your contributions to the project as PMC Chair.
 Congratulations Dinesh!

 On 2024/06/20 16:25:26 David Capwell wrote:
 > Congrats!
 >
 > > On Jun 20, 2024, at 9:10 AM, Melissa Logan 
 wrote:
 > >
 > > Josh, thank you for your time as chair + congrats Dinesh!
 > >
 > > On Thu, Jun 20, 2024 at 9:08 AM Abe Ratnofsky >>> a...@aber.io>> wrote:
 > >> Congrats Dinesh! Thank you Josh!
 > >>
 > >>> On Jun 20, 2024, at 11:53 AM, Jeremiah Jordan <
 jeremiah.jor...@gmail.com > wrote:
 > >>>
 > >>> Welcome to the Chair role Dinesh!  Congrats!
 > >>>
 > >>> On Jun 20, 2024 at 10:50:37 AM, Josh McKenzie <
 jmcken...@apache.org > wrote:
 >  Another PMC Chair baton pass incoming! On behalf of the Apache
 Cassandra Project Management Committee (PMC) I would like to welcome and
 congratulate our next PMC Chair Dinesh Joshi (djoshi).
 > 
 >  Dinesh has been a member of the PMC for a few years now and many
 of you likely know him from his thoughtful, measured presence on many of
 our collective discussions as we've grown and evolved over the past few
 years.
 > 
 >  I appreciate the project trusting me as liaison with the board
 over the past year and look forward to supporting Dinesh in the role in the
 future.
 > 
 >  Repeating Mick (repeating Paulo's) words from last year: The
 chair is an administrative position that interfaces with the Apache
 Software Foundation Board, by submitting regular reports about project
 status and health. Read more about the PMC chair role on Apache projects:
 >  - https://www.apache.org/foundation/how-it-works.html#pmc
 >  - https://www.apache.org/foundation/how-it-works.html#pmc-chair
 >  -
 https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers
 > 
 >  The PMC as a whole is the entity that oversees and leads the
 project and any PMC member can be approached as a representative of the
 committee. A list of Apache Cassandra PMC members can be found on:
 https://cassandra.apache.org/_/community.html
 > >>
 >
 >

>>>

Re: Suggestions for CASSANDRA-18078

[Jeremiah Jordan]

 +1 from me for 1, just remove it now.
I think this case is different from CASSANDRA-19556/CASSANDRA-17425.  The
new guardrail from 19556 which would deprecate the 17425 has not been
committed yet.  In the case of MAXWRITETIME the replacement is already in
the code, we just didn’t remove MAXWRITETIME yet.

Jeremiah Jordan
e. jerem...@datastax.com
w. www.datastax.com



On Jun 20, 2024 at 11:46:08 AM, Štefan Miklošovič 
wrote:

> List,
>
> we need your opinions about CASSANDRA-18078.
>
> That ticket is about the removal of MAXWRITETIME function which was added
> in CASSANDRA-17425 and firstly introduced in 5.0-alpha1.
>
> This function was identified to be redundant in favor of CASSANDRA-8877
> and CASSANDRA-18060.
>
> The idea of the removal was welcomed and the patch was prepared doing so
> but it was never delivered and the question what to do with it, in
> connection with 5.0.0, still remains.
>
> The options are:
>
> 1) since 18078 was never released in GA, there is still time to remove it.
> 2) it is too late for the removal hence we would keep it in 5.0.0 and we
> would deprecate it in 5.0.1 and remove it in trunk.
>
> It is worth to say that there is a precedent in 2), in CASSANDRA-17495,
> where it was the very same scenario. A guardrail was introduced in alpha1.
> We decided to release and deprecate in 5.0.1 and remove in trunk. The same
> might be applied here, however we would like to have it confirmed if this
> is indeed the case or we prefer to just go with 1) and be done with it.
>
> Regards
>

Re: Cassandra PMC Chair Rotation, 2024 Edition

[Ekaterina Dimitrova]

Thank you, Josh, and congrats, Dinesh! 🥳

On Thu, 20 Jun 2024 at 19:44, Joseph Lynch  wrote:

> This is exciting news!!
>
> Congratulations Dinesh and thank you for taking on this role!  Also thank
> you to Josh for taking the role this year!
>
> -Joey
>
> On Thu, Jun 20, 2024 at 12:39 PM Rahul Xavier Singh <
> rahul.xavier.si...@gmail.com> wrote:
>
>> Congrats Dinesh!
>>
>> On Thu, Jun 20, 2024 at 12:27 PM Francisco Guerrero 
>> wrote:
>>
>>> Thanks Josh for your contributions to the project as PMC Chair.
>>> Congratulations Dinesh!
>>>
>>> On 2024/06/20 16:25:26 David Capwell wrote:
>>> > Congrats!
>>> >
>>> > > On Jun 20, 2024, at 9:10 AM, Melissa Logan 
>>> wrote:
>>> > >
>>> > > Josh, thank you for your time as chair + congrats Dinesh!
>>> > >
>>> > > On Thu, Jun 20, 2024 at 9:08 AM Abe Ratnofsky >> a...@aber.io>> wrote:
>>> > >> Congrats Dinesh! Thank you Josh!
>>> > >>
>>> > >>> On Jun 20, 2024, at 11:53 AM, Jeremiah Jordan <
>>> jeremiah.jor...@gmail.com > wrote:
>>> > >>>
>>> > >>> Welcome to the Chair role Dinesh!  Congrats!
>>> > >>>
>>> > >>> On Jun 20, 2024 at 10:50:37 AM, Josh McKenzie <
>>> jmcken...@apache.org > wrote:
>>> >  Another PMC Chair baton pass incoming! On behalf of the Apache
>>> Cassandra Project Management Committee (PMC) I would like to welcome and
>>> congratulate our next PMC Chair Dinesh Joshi (djoshi).
>>> > 
>>> >  Dinesh has been a member of the PMC for a few years now and many
>>> of you likely know him from his thoughtful, measured presence on many of
>>> our collective discussions as we've grown and evolved over the past few
>>> years.
>>> > 
>>> >  I appreciate the project trusting me as liaison with the board
>>> over the past year and look forward to supporting Dinesh in the role in the
>>> future.
>>> > 
>>> >  Repeating Mick (repeating Paulo's) words from last year: The
>>> chair is an administrative position that interfaces with the Apache
>>> Software Foundation Board, by submitting regular reports about project
>>> status and health. Read more about the PMC chair role on Apache projects:
>>> >  - https://www.apache.org/foundation/how-it-works.html#pmc
>>> >  - https://www.apache.org/foundation/how-it-works.html#pmc-chair
>>> >  -
>>> https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers
>>> > 
>>> >  The PMC as a whole is the entity that oversees and leads the
>>> project and any PMC member can be approached as a representative of the
>>> committee. A list of Apache Cassandra PMC members can be found on:
>>> https://cassandra.apache.org/_/community.html
>>> > >>
>>> >
>>> >
>>>
>>

Suggestions for CASSANDRA-18078

[Štefan Miklošovič]

List,

we need your opinions about CASSANDRA-18078.

That ticket is about the removal of MAXWRITETIME function which was added
in CASSANDRA-17425 and firstly introduced in 5.0-alpha1.

This function was identified to be redundant in favor of CASSANDRA-8877 and
CASSANDRA-18060.

The idea of the removal was welcomed and the patch was prepared doing so
but it was never delivered and the question what to do with it, in
connection with 5.0.0, still remains.

The options are:

1) since 18078 was never released in GA, there is still time to remove it.
2) it is too late for the removal hence we would keep it in 5.0.0 and we
would deprecate it in 5.0.1 and remove it in trunk.

It is worth to say that there is a precedent in 2), in CASSANDRA-17495,
where it was the very same scenario. A guardrail was introduced in alpha1.
We decided to release and deprecate in 5.0.1 and remove in trunk. The same
might be applied here, however we would like to have it confirmed if this
is indeed the case or we prefer to just go with 1) and be done with it.

Regards

Re: Cassandra PMC Chair Rotation, 2024 Edition

[Joseph Lynch]

This is exciting news!!

Congratulations Dinesh and thank you for taking on this role!  Also thank
you to Josh for taking the role this year!

-Joey

On Thu, Jun 20, 2024 at 12:39 PM Rahul Xavier Singh <
rahul.xavier.si...@gmail.com> wrote:

> Congrats Dinesh!
>
> On Thu, Jun 20, 2024 at 12:27 PM Francisco Guerrero 
> wrote:
>
>> Thanks Josh for your contributions to the project as PMC Chair.
>> Congratulations Dinesh!
>>
>> On 2024/06/20 16:25:26 David Capwell wrote:
>> > Congrats!
>> >
>> > > On Jun 20, 2024, at 9:10 AM, Melissa Logan 
>> wrote:
>> > >
>> > > Josh, thank you for your time as chair + congrats Dinesh!
>> > >
>> > > On Thu, Jun 20, 2024 at 9:08 AM Abe Ratnofsky > a...@aber.io>> wrote:
>> > >> Congrats Dinesh! Thank you Josh!
>> > >>
>> > >>> On Jun 20, 2024, at 11:53 AM, Jeremiah Jordan <
>> jeremiah.jor...@gmail.com > wrote:
>> > >>>
>> > >>> Welcome to the Chair role Dinesh!  Congrats!
>> > >>>
>> > >>> On Jun 20, 2024 at 10:50:37 AM, Josh McKenzie > > wrote:
>> >  Another PMC Chair baton pass incoming! On behalf of the Apache
>> Cassandra Project Management Committee (PMC) I would like to welcome and
>> congratulate our next PMC Chair Dinesh Joshi (djoshi).
>> > 
>> >  Dinesh has been a member of the PMC for a few years now and many
>> of you likely know him from his thoughtful, measured presence on many of
>> our collective discussions as we've grown and evolved over the past few
>> years.
>> > 
>> >  I appreciate the project trusting me as liaison with the board
>> over the past year and look forward to supporting Dinesh in the role in the
>> future.
>> > 
>> >  Repeating Mick (repeating Paulo's) words from last year: The chair
>> is an administrative position that interfaces with the Apache Software
>> Foundation Board, by submitting regular reports about project status and
>> health. Read more about the PMC chair role on Apache projects:
>> >  - https://www.apache.org/foundation/how-it-works.html#pmc
>> >  - https://www.apache.org/foundation/how-it-works.html#pmc-chair
>> >  -
>> https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers
>> > 
>> >  The PMC as a whole is the entity that oversees and leads the
>> project and any PMC member can be approached as a representative of the
>> committee. A list of Apache Cassandra PMC members can be found on:
>> https://cassandra.apache.org/_/community.html
>> > >>
>> >
>> >
>>
>

Re: Cassandra PMC Chair Rotation, 2024 Edition

[Rahul Xavier Singh]

Congrats Dinesh!

On Thu, Jun 20, 2024 at 12:27 PM Francisco Guerrero 
wrote:

> Thanks Josh for your contributions to the project as PMC Chair.
> Congratulations Dinesh!
>
> On 2024/06/20 16:25:26 David Capwell wrote:
> > Congrats!
> >
> > > On Jun 20, 2024, at 9:10 AM, Melissa Logan 
> wrote:
> > >
> > > Josh, thank you for your time as chair + congrats Dinesh!
> > >
> > > On Thu, Jun 20, 2024 at 9:08 AM Abe Ratnofsky  a...@aber.io>> wrote:
> > >> Congrats Dinesh! Thank you Josh!
> > >>
> > >>> On Jun 20, 2024, at 11:53 AM, Jeremiah Jordan <
> jeremiah.jor...@gmail.com > wrote:
> > >>>
> > >>> Welcome to the Chair role Dinesh!  Congrats!
> > >>>
> > >>> On Jun 20, 2024 at 10:50:37 AM, Josh McKenzie  > wrote:
> >  Another PMC Chair baton pass incoming! On behalf of the Apache
> Cassandra Project Management Committee (PMC) I would like to welcome and
> congratulate our next PMC Chair Dinesh Joshi (djoshi).
> > 
> >  Dinesh has been a member of the PMC for a few years now and many of
> you likely know him from his thoughtful, measured presence on many of our
> collective discussions as we've grown and evolved over the past few years.
> > 
> >  I appreciate the project trusting me as liaison with the board over
> the past year and look forward to supporting Dinesh in the role in the
> future.
> > 
> >  Repeating Mick (repeating Paulo's) words from last year: The chair
> is an administrative position that interfaces with the Apache Software
> Foundation Board, by submitting regular reports about project status and
> health. Read more about the PMC chair role on Apache projects:
> >  - https://www.apache.org/foundation/how-it-works.html#pmc
> >  - https://www.apache.org/foundation/how-it-works.html#pmc-chair
> >  -
> https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers
> > 
> >  The PMC as a whole is the entity that oversees and leads the
> project and any PMC member can be approached as a representative of the
> committee. A list of Apache Cassandra PMC members can be found on:
> https://cassandra.apache.org/_/community.html
> > >>
> >
> >
>

Re: Cassandra PMC Chair Rotation, 2024 Edition

[Francisco Guerrero]

Thanks Josh for your contributions to the project as PMC Chair. Congratulations 
Dinesh!

On 2024/06/20 16:25:26 David Capwell wrote:
> Congrats!
> 
> > On Jun 20, 2024, at 9:10 AM, Melissa Logan  wrote:
> > 
> > Josh, thank you for your time as chair + congrats Dinesh!
> > 
> > On Thu, Jun 20, 2024 at 9:08 AM Abe Ratnofsky  > > wrote:
> >> Congrats Dinesh! Thank you Josh!
> >> 
> >>> On Jun 20, 2024, at 11:53 AM, Jeremiah Jordan  >>> > wrote:
> >>> 
> >>> Welcome to the Chair role Dinesh!  Congrats!
> >>> 
> >>> On Jun 20, 2024 at 10:50:37 AM, Josh McKenzie  >>> > wrote:
>  Another PMC Chair baton pass incoming! On behalf of the Apache Cassandra 
>  Project Management Committee (PMC) I would like to welcome and 
>  congratulate our next PMC Chair Dinesh Joshi (djoshi).
>  
>  Dinesh has been a member of the PMC for a few years now and many of you 
>  likely know him from his thoughtful, measured presence on many of our 
>  collective discussions as we've grown and evolved over the past few 
>  years.
>  
>  I appreciate the project trusting me as liaison with the board over the 
>  past year and look forward to supporting Dinesh in the role in the 
>  future.
>  
>  Repeating Mick (repeating Paulo's) words from last year: The chair is an 
>  administrative position that interfaces with the Apache Software 
>  Foundation Board, by submitting regular reports about project status and 
>  health. Read more about the PMC chair role on Apache projects:
>  - https://www.apache.org/foundation/how-it-works.html#pmc
>  - https://www.apache.org/foundation/how-it-works.html#pmc-chair
>  - https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers
>  
>  The PMC as a whole is the entity that oversees and leads the project and 
>  any PMC member can be approached as a representative of the committee. A 
>  list of Apache Cassandra PMC members can be found on: 
>  https://cassandra.apache.org/_/community.html
> >> 
> 
> 

Re: Cassandra PMC Chair Rotation, 2024 Edition

[David Capwell]

Congrats!

> On Jun 20, 2024, at 9:10 AM, Melissa Logan  wrote:
> 
> Josh, thank you for your time as chair + congrats Dinesh!
> 
> On Thu, Jun 20, 2024 at 9:08 AM Abe Ratnofsky  > wrote:
>> Congrats Dinesh! Thank you Josh!
>> 
>>> On Jun 20, 2024, at 11:53 AM, Jeremiah Jordan >> > wrote:
>>> 
>>> Welcome to the Chair role Dinesh!  Congrats!
>>> 
>>> On Jun 20, 2024 at 10:50:37 AM, Josh McKenzie >> > wrote:
 Another PMC Chair baton pass incoming! On behalf of the Apache Cassandra 
 Project Management Committee (PMC) I would like to welcome and 
 congratulate our next PMC Chair Dinesh Joshi (djoshi).
 
 Dinesh has been a member of the PMC for a few years now and many of you 
 likely know him from his thoughtful, measured presence on many of our 
 collective discussions as we've grown and evolved over the past few years.
 
 I appreciate the project trusting me as liaison with the board over the 
 past year and look forward to supporting Dinesh in the role in the future.
 
 Repeating Mick (repeating Paulo's) words from last year: The chair is an 
 administrative position that interfaces with the Apache Software 
 Foundation Board, by submitting regular reports about project status and 
 health. Read more about the PMC chair role on Apache projects:
 - https://www.apache.org/foundation/how-it-works.html#pmc
 - https://www.apache.org/foundation/how-it-works.html#pmc-chair
 - https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers
 
 The PMC as a whole is the entity that oversees and leads the project and 
 any PMC member can be approached as a representative of the committee. A 
 list of Apache Cassandra PMC members can be found on: 
 https://cassandra.apache.org/_/community.html
>> 

Re: Cassandra PMC Chair Rotation, 2024 Edition

[Melissa Logan]

Josh, thank you for your time as chair + congrats Dinesh!

On Thu, Jun 20, 2024 at 9:08 AM Abe Ratnofsky  wrote:

> Congrats Dinesh! Thank you Josh!
>
> On Jun 20, 2024, at 11:53 AM, Jeremiah Jordan 
> wrote:
>
> Welcome to the Chair role Dinesh!  Congrats!
>
> On Jun 20, 2024 at 10:50:37 AM, Josh McKenzie 
> wrote:
>
>> Another PMC Chair baton pass incoming! On behalf of the Apache Cassandra
>> Project Management Committee (PMC) I would like to welcome and congratulate
>> our next PMC Chair Dinesh Joshi (djoshi).
>>
>> Dinesh has been a member of the PMC for a few years now and many of you
>> likely know him from his thoughtful, measured presence on many of our
>> collective discussions as we've grown and evolved over the past few years.
>>
>> I appreciate the project trusting me as liaison with the board over the
>> past year and look forward to supporting Dinesh in the role in the future.
>>
>> Repeating Mick (repeating Paulo's) words from last year: The chair is an
>> administrative position that interfaces with the Apache Software Foundation
>> Board, by submitting regular reports about project status and health. Read
>> more about the PMC chair role on Apache projects:
>> - https://www.apache.org/foundation/how-it-works.html#pmc
>> - https://www.apache.org/foundation/how-it-works.html#pmc-chair
>> - https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers
>>
>> The PMC as a whole is the entity that oversees and leads the project and
>> any PMC member can be approached as a representative of the committee. A
>> list of Apache Cassandra PMC members can be found on:
>> https://cassandra.apache.org/_/community.html
>>
>
>

Re: Cassandra PMC Chair Rotation, 2024 Edition

[Aaron Ploetz]

Congratulations, Dinesh!

On Thu, Jun 20, 2024 at 10:51 AM Josh McKenzie  wrote:

> Another PMC Chair baton pass incoming! On behalf of the Apache Cassandra
> Project Management Committee (PMC) I would like to welcome and congratulate
> our next PMC Chair Dinesh Joshi (djoshi).
>
> Dinesh has been a member of the PMC for a few years now and many of you
> likely know him from his thoughtful, measured presence on many of our
> collective discussions as we've grown and evolved over the past few years.
>
> I appreciate the project trusting me as liaison with the board over the
> past year and look forward to supporting Dinesh in the role in the future.
>
> Repeating Mick (repeating Paulo's) words from last year: The chair is an
> administrative position that interfaces with the Apache Software Foundation
> Board, by submitting regular reports about project status and health. Read
> more about the PMC chair role on Apache projects:
> - https://www.apache.org/foundation/how-it-works.html#pmc
> - https://www.apache.org/foundation/how-it-works.html#pmc-chair
> - https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers
>
> The PMC as a whole is the entity that oversees and leads the project and
> any PMC member can be approached as a representative of the committee. A
> list of Apache Cassandra PMC members can be found on:
> https://cassandra.apache.org/_/community.html
>

Re: Cassandra PMC Chair Rotation, 2024 Edition

[Abe Ratnofsky]

Congrats Dinesh! Thank you Josh!

> On Jun 20, 2024, at 11:53 AM, Jeremiah Jordan  
> wrote:
> 
> Welcome to the Chair role Dinesh!  Congrats!
> 
> On Jun 20, 2024 at 10:50:37 AM, Josh McKenzie  > wrote:
>> Another PMC Chair baton pass incoming! On behalf of the Apache Cassandra 
>> Project Management Committee (PMC) I would like to welcome and congratulate 
>> our next PMC Chair Dinesh Joshi (djoshi).
>> 
>> Dinesh has been a member of the PMC for a few years now and many of you 
>> likely know him from his thoughtful, measured presence on many of our 
>> collective discussions as we've grown and evolved over the past few years.
>> 
>> I appreciate the project trusting me as liaison with the board over the past 
>> year and look forward to supporting Dinesh in the role in the future.
>> 
>> Repeating Mick (repeating Paulo's) words from last year: The chair is an 
>> administrative position that interfaces with the Apache Software Foundation 
>> Board, by submitting regular reports about project status and health. Read 
>> more about the PMC chair role on Apache projects:
>> - https://www.apache.org/foundation/how-it-works.html#pmc
>> - https://www.apache.org/foundation/how-it-works.html#pmc-chair
>> - https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers
>> 
>> The PMC as a whole is the entity that oversees and leads the project and any 
>> PMC member can be approached as a representative of the committee. A list of 
>> Apache Cassandra PMC members can be found on: 
>> https://cassandra.apache.org/_/community.html

Re: [EXTERNAL] Re: [DISCUSS] Adding experimental vtables and rules around them

[Josh McKenzie]

> I like it as it makes this apart of its name, but is sad that we must break 
> compatibility once we mark it stable (as we move the keyspace).  
+1 to this exact set of sentiments. The next logical question to me is "should 
we alias the old system_experimental* table name to the new stable table name 
for vtables once they graduate to support backwards compatibility", but I think 
I fall on the "no" side there.

On Fri, May 31, 2024, at 5:15 PM, J. D. Jordan wrote:
> 
> We have already agreed in the past that having experimental features, behind 
> feature flags, in stable releases is a good thing for keeping those features 
> up to date, for getting feedback from end users, and many others.
> The question here is about how we ensure that end users are aware something 
> is experimental, because the person who installed C* and enabled the feature 
> flag is likely not the same person who is using the feature.
> 
>> On May 31, 2024, at 3:23 PM, German Eichberger via dev 
>>  wrote:
>> 
>> Hi,
>> 
>> To sum where everyone is coming from: We would like to have features in a 
>> stable version of Cassandra which are experimental and are subject to 
>> non-backward compatible change. This indicates to me that the feature is not 
>> finished and should likely not be included in a stable release.  What 
>> benefit are we looking for by including it into a stable release as opposed 
>> to rolling it to the next release.
>> 
>> Thanks,
>> German
>> 
>> 
>> *From:* Maxim Muzafarov 
>> *Sent:* Wednesday, May 29, 2024 1:09 PM
>> *To:* dev@cassandra.apache.org 
>> *Subject:* [EXTERNAL] Re: [DISCUSS] Adding experimental vtables and rules 
>> around them
>>  
>> Hello everyone,
>> 
>> I like the idea of highlighting some of the experimental virtual
>> tables whose model might be changed in future releases.
>> 
>> As another option, we could add an @Experimetal annotation (or another
>> name) and a configuration parameter
>> experimental_virtula_tables_enabled (default is false). This, in turn,
>> means if a virtual table is experimental, it won't be registered in a
>> virtual keyspace unless the corresponding configuration parameter is
>> enabled. This also means that a user must implicitly enable an
>> experimental API, and prevent us from spamming the log with warnings.
>> All of this does not preclude us from specifying the experimental
>> state of some virtual tables in the documentation.
>> 
>> On Wed, 29 May 2024 at 21:18, Abe Ratnofsky  wrote:
>> >
>> > I agree that ClientWarning is the best way to indicate the risk of using 
>> > an experimental feature directly to the user. Presenting information in 
>> > the client application's logs directly means that the person who wrote the 
>> > query is most likely to see the warning, rather than an operator who sees 
>> > cluster logs.
>> >
>> > I don't think it's necessary to attach a ClientWarning to every single 
>> > client response; a ClientWarning analog to NoSpamLogger would be useful 
>> > for this ("warn a client at most once per day").
>> >
>> > This would also be useful for warning on usage of deprecated features.
>> >
>> > > On May 29, 2024, at 3:01 PM, David Capwell  wrote:
>> > >
>> > > We agreed a long time ago that all new features are disabled by default, 
>> > > but I wanted to try to flesh out what we “should” do with something that 
>> > > might still be experimental and subject to breaking changes; I would 
>> > > prefer we keep this thread specific to vtables as the UX is different 
>> > > for different types of things…
>> > >
>> > > So, lets say we are adding a set of vtables but we are not 100% sure 
>> > > what the schema should be and we learn after the release that changes 
>> > > should be made, but that would end up breaking the table… we currently 
>> > > define everything as “don’t break this” so if we publish a table that 
>> > > isn’t 100% baked we are kinda stuck with it for a very very long time… I 
>> > > would like to define a way to expose vtables that are subject to change 
>> > > (breaking schema changes) across different release and rules around them 
>> > > (only in minor?  Maybe even in patch?).
>> > >
>> > > Lets try to use a concrete example so everyone is on the same page.
>> > >
>> > > Accord is disabled by default (it is a new feature), so the vtables to 
>> > > expose internals would be expected to be undefined and not present on 
>> > > the instance.
>> > >
>> > > When accord is enabled (accord.enabled = true) we add a set of vtables:
>> > >
>> > > Epochs - shows what epochs are known to accord
>> > > Cache - shows how the internal caches are performing
>> > > Etc.
>> > >
>> > > Using epochs as an example it currently only shows a single column: the 
>> > > long epoch
>> > >
>> > > CREATE VIRTUAL TABLE system_accord.epochs (epoch bigint PRIMARY KEY);
>> > >
>> > > Lets say we find that this table isn’t enough and we really need to 
>> > > scope it to each of the “stores” (threads for processing accord tasks)
>> > >
>>

Re: Cassandra PMC Chair Rotation, 2024 Edition

[Jeremiah Jordan]

 Welcome to the Chair role Dinesh!  Congrats!

On Jun 20, 2024 at 10:50:37 AM, Josh McKenzie  wrote:

> Another PMC Chair baton pass incoming! On behalf of the Apache Cassandra
> Project Management Committee (PMC) I would like to welcome and congratulate
> our next PMC Chair Dinesh Joshi (djoshi).
>
> Dinesh has been a member of the PMC for a few years now and many of you
> likely know him from his thoughtful, measured presence on many of our
> collective discussions as we've grown and evolved over the past few years.
>
> I appreciate the project trusting me as liaison with the board over the
> past year and look forward to supporting Dinesh in the role in the future.
>
> Repeating Mick (repeating Paulo's) words from last year: The chair is an
> administrative position that interfaces with the Apache Software Foundation
> Board, by submitting regular reports about project status and health. Read
> more about the PMC chair role on Apache projects:
> - https://www.apache.org/foundation/how-it-works.html#pmc
> - https://www.apache.org/foundation/how-it-works.html#pmc-chair
> - https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers
>
> The PMC as a whole is the entity that oversees and leads the project and
> any PMC member can be approached as a representative of the committee. A
> list of Apache Cassandra PMC members can be found on:
> https://cassandra.apache.org/_/community.html
>

Cassandra PMC Chair Rotation, 2024 Edition

[Josh McKenzie]

Another PMC Chair baton pass incoming! On behalf of the Apache Cassandra 
Project Management Committee (PMC) I would like to welcome and congratulate our 
next PMC Chair Dinesh Joshi (djoshi).

Dinesh has been a member of the PMC for a few years now and many of you likely 
know him from his thoughtful, measured presence on many of our collective 
discussions as we've grown and evolved over the past few years.

I appreciate the project trusting me as liaison with the board over the past 
year and look forward to supporting Dinesh in the role in the future.

Repeating Mick (repeating Paulo's) words from last year: The chair is an 
administrative position that interfaces with the Apache Software Foundation 
Board, by submitting regular reports about project status and health. Read more 
about the PMC chair role on Apache projects:
- https://www.apache.org/foundation/how-it-works.html#pmc
- https://www.apache.org/foundation/how-it-works.html#pmc-chair
- https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers

The PMC as a whole is the entity that oversees and leads the project and any 
PMC member can be approached as a representative of the committee. A list of 
Apache Cassandra PMC members can be found on: 
https://cassandra.apache.org/_/community.html

[RESULT][VOTE] CEP-24 Password validation / generation

[Štefan Miklošovič]

The vote has passed with 5 binding +1s, 1 non-binding +1 and no vetoes.