Re: [VOTE] CEP-8 Datastax Drivers Donation

+1 (long time coming!) On Wed, Jun 14, 2023 at 3:51 AM Jorge Bay Gondra wrote: > +1 nb > > On Wed, Jun 14, 2023 at 9:13 AM Sam Tunnicliffe wrote: > >> +1 >> >> On 13 Jun 2023, at 15:14, Jeremy Hanna >> wrote: >> >> Calling for a vote on CEP-8 [1]. >> >> To clarify the intent, as Benjamin said

Re: Welcome Adam Holmberg as Cassandra committer

: Joseph Lynch > Sent: Tuesday, August 17, 2021 7:44 AM > To: dev@cassandra.apache.org > Subject: Re: Welcome Adam Holmberg as Cassandra committer > > Congratulations Adam! > > On Tue, Aug 17, 2021 at 10:25 AM Jordan West wrote: > > > > Congrats Adam! > &g

Re: Are we ready for 4.0.0 (GA) ?

od progress on stability of ci-cassandra.a.o with > the introduction of cpu docker limits imposed, and better monitoring of the > agents so we can ensure we get the saturation and load we want. Dockerising > the cqlshlib tests is also in progress. > > The alternative to a 4.0.0 GA release is a 4.0-rc2 release. > Should the next release be: 4.0.0 (GA) or 4.0-rc2 ? > -- Adam Holmberg e. adam.holmb...@datastax.com w. www.datastax.com

Cassandra 4.0 Status 2021-04-01

t us know on the thread if I have missed anything that needs attention. I encourage anyone to respond to these reports calling attention to any localized things that could use it. As always thanks to everyone for the continued hard work on the project. -- Adam Holmberg e. adam.holmb...@datastax.com w. www.datastax.com

Cassandra 4.0 Status 2021-03-25

Greetings. Here’s your look at Cassandra 4.0 release status for the week -- this one with 300% more exclamation points! Seven days since last update. Jira board with 4.0 scope: https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1661 High level numbers by release ph

Cassandra 4.0 Status 2021-03-18

355&quickFilter=1661&quickFilter=1694 Please let us know on the thread if I have missed anything that needs attention. I encourage anyone to respond to these reports calling attention to any localized things that could use it. As always thanks to everyone for the continued hard work on the pr

Cassandra 4.0 Status 2021-03-11

=1694 Please let us know on the thread if I have missed anything that needs attention. I encourage anyone to respond to these reports calling attention to any localized things that could use it. As always thanks to everyone for the continued hard work on the project. -- Adam Holmberg e. adam.holmb...@datastax.com w. www.datastax.com

Cassandra 4.0 Status 2021-03-04

ion to any localized things that could use it. As always thanks to everyone for the continued hard work on the project. -- Adam Holmberg e. adam.holmb...@datastax.com w. www.datastax.com

Cassandra 4.0 Status 2021-02-25

ilter=1694 Please let us know on the thread if I have missed anything that needs attention. I encourage anyone to respond to these reports calling attention to any localized things that could use it. As always thanks to everyone for the continued hard work on the project. -- Adam Hol

Cassandra 4.0 Status 2021-02-18

could use it. As always thanks to everyone for the continued hard work on the project. -- Adam Holmberg e. adam.holmb...@datastax.com w. www.datastax.com

Cassandra 4.0 Status 2021-02-11

ttention. I encourage anyone to respond to these reports calling attention to any localized things that could use it. As always thanks to everyone for the continued hard work on the project. -- Adam Holmberg e. adam.holmb...@datastax.com w. www.datastax.com

Cassandra 4.0 Status 2021-02-03

always thanks to everyone for the continued hard work on the project. -- Adam Holmberg e. adam.holmb...@datastax.com w. www.datastax.com

Re: [DISCUSS] When to stop supporting Python 2

supports python 2 > whenever > > > it's convenient. > > > > > > Angelo has the right idea that rather than trying to finesse a > > deprecation > > > cycle into 4.0 at this late date, a better migration path can be > provided > > > by

Cassandra 4.0 Status 2021-01-27

to these reports calling attention to any localized things that could use it. As always thanks to everyone for the continued hard work on the project. -- Adam Holmberg e. adam.holmb...@datastax.com w. www.datastax.com

Re: [DISCUSS] When to stop supporting Python 2

if we are going in the direction that drops > > python2 support in 4.0 and retains the python2 compatible code. In 4.x or > > 5.0? > > > > On Mon, Jan 25, 2021 at 9:24 AM Ekaterina Dimitrova < > e.dimitr...@gmail.com > > > > > wrote: > > > > > I supp

[DISCUSS] When to stop supporting Python 2

multiple runtimes, and we wouldn't be concerned with fixing python2-specific issues that may arise on the EOL runtime [3]. I look forward to the discussion. -- Adam Holmberg e. adam.holmb...@datastax.com w. www.datastax.com [1] https://issues.apache.org/jira/browse/CASSANDRA-10190 [2] htt

Cassandra 4.0 Status 2020-01-19

e thread if I have missed anything that needs attention. I encourage anyone to respond to these reports calling attention to any localized things that could use it. As always thanks to everyone for the continued hard work on the project. -- Adam Holmberg e. adam.holmb...@datastax.com w. www.datastax.com

Cassandra 4.0 Status 2020-12-14

ter=1694 Please let us know on the thread if I have missed anything that needs attention. I encourage anyone to respond to these reports calling attention to any localized things that could use it. As always thanks to everyone for the continued hard work on the project. -Adam Holmberg

Re: Cassandra 4.0 Status 2020-12-07

gt; attention to any localized things that could use it. > > As always thanks to everyone for the continued work on the project. > > -Jon Meredith > > - > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > > -- Adam Holmberg e. adam.holmb...@datastax.com w. www.datastax.com

Re: cassandra--dtest: module 'pytest' has no attribute 'config'

e 'config' > > > > $ cat pytest.ini > > [pytest] > > cassandra_dir= /home/aeljami/workspace/git/cstar/cassandra > > python_files = refresh_test.py > > junit_suite_name = Cassandra dtests > > log_print = True > > log_level = INFO > > log_format = %(asctime)s,%(msecs)d %(name)s %(levelname)s %(message)s > > timeout = 900 > > > > Any idea please ? > > Thanks > -- Adam Holmberg e. adam.holmb...@datastax.com w. www.datastax.com

Cassandra 4.0 Status 2020-11-16

e/RapidBoard.jspa?rapidView=355&quickFilter=1661&quickFilter=1694 Please let us know on the thread if I have missed anything that needs attention. I encourage anyone to respond to these reports calling attention to any localized things that could use it. As always thanks to everyone for the continued work on the project. -Adam Holmberg

Re: Committing `CASSANDRA-13701 Lower default num_tokens` and the dtest slowdown…

open analysis. A ticket[1] has been created for analysis and further follow-up. We welcome any concrete ideas people already have in mind. Kind regards, Adam Holmberg [1] https://issues.apache.org/jira/browse/CASSANDRA-16079 On Mon, Aug 24, 2020 at 12:17 PM Mick Semb Wever wrote: > I beli

Re: DataStax Driver Donation to Apache Cassandra Project

> >that came in as a top level project. From the peanut gallery, it > seems like > >that has been less than ideal a couple of times in the past > coordinating > >releases, trademarks and such with separate project management. > > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > > For additional commands, e-mail: dev-h...@cassandra.apache.org > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > > -- Adam Holmberg e. adam.holmb...@datastax.com w. www.datastax.com

DataStax Driver Donation to Apache Cassandra Project

The developers who maintain the DataStax drivers would like to start a conversation about donating these drivers to the Apache Cassandra project. Since we're actively working on the C* 4.0 support and integration in the drivers right now, we don't plan on executing on this until after C* 4.0 releas

Re: V5 as a protocol beta version in 3.11

upon release. Adam Holmberg On Tue, Nov 7, 2017 at 10:57 AM, J. D. Jordan wrote: > Again. V5 beta in 3.11 was always meant to stop working when future things > happened to V5 in the drivers and in C*. I see no problem with leaving the > beta V5, which is an opt in thing to try out,

Cassandra Wiki Edit Permissions for user AdamHolmberg

I'm seeking wiki edit permissions for my user on https://wiki.apache.org/cassandra/: "AdamHolmberg" Regards, Adam Holmberg

Re: JIRA Label for Client-Impacting Changes/Decisions

8:15:43 PM, Tyler Hobbs (ty...@datastax.com) > > wrote: > > > > I'm personally in favor of using a label. Besides myself, Sylvain, > > Benjamin, and Aleksey are probably the most likely to be keeping track of > > this. Any objections or alternatives from you guys? >

JIRA Label for Client-Impacting Changes/Decisions

As a Cassandra driver developer, I'm looking for a good way to keep track of client-impacting changes and decisions in Cassandra. I'm aware of super tasks like CASSANDRA-8043 (native v4), and others (schema migration

PerRowSecondaryIndex Multiple Load

ybe I'm thinking about things wrong. Any input would be appreciated. Regards, Adam Holmberg