Re: Which cassandra client for Python should we use (in the context of Python 3.12) ?

[Bret McGuire]

   To add some additional information to what's already on this thread:
PYTHON-1378 is actively being looked into.  An initial look has suggested a
likely cause; it's very likely this was an oversight stemming from the move
to cibuildwheel.  Assuming I can confirm that a fix will then be provided.
All of that work will be managed on PYTHON-1378.

   Regarding the question about asyncore vs. asyncio: as Jarek correctly
pointed out we have PYTHON-1375 to represent the work of moving to
asyncio.  I'll also mention that we've begun defining what will be included
in the next Python driver release.  Let's call it 3.30.0, although (as
always) that's subject to change.  This release is currently slated to
include three major changes:

   * Stabilize asyncio reactor and make it the default (PYTHON-1375
)
   * Officially get off nose and move to pytest (PYTHON-1297
)
   * Extend vector support to variable length types (PYTHON-1369
)

   As mentioned above everything is subject to change but as of this
writing the current plan is that PYTHON-1375 will be included in the next
release.  This can be tracked via the "Fix version" on the various tickets
above (yup, we already have a 3.30.0 release in JIRA).  You can also follow
along on the Python driver mailing list
; I'll
likely be starting a more detailed discussion on some of these points there
soon.

   Thanks!

  - Bret -


On Wed, Feb 21, 2024 at 7:58 AM Jarek Potiuk  wrote:

> This is cool - thanks Jeff for this explanation, that helps us in making
> informed decisions. Really appreciate it!
>
> Very encouraging for the future :) - I think then, if the donation is
> on-going, choosing a cassandra-driver (which I understand will become
> ASF-owned) is definitely a preference for us.
>
> And no - we do not have to release it now. We can definitely wait - we can
> just exclude Python 3.12 support until the .whl has libev support (I hope
> my issue will be handled soon by Datastax :). Then we can re-enable Python
> 3.12 support and add instructions to our users to make sure libev is
> included on Python 3.12. So it does not block us now, and we have
> clear vision on the way forward.
>
> BTW. I looked at the links - they were mostly about Java Driver and
> mention Python Driver as the next logical step (agree) - is there anything
> happening currently with it ? There is a doc link that I have no access to,
> but would be great to know when it might happen? I am just eager to see it
> happen.
>
> J.
>
> On Wed, Feb 21, 2024 at 12:53 PM Jeff Jirsa  wrote:
>
>>
>>
>> On 2024/02/21 09:26:53 Jarek Potiuk wrote:
>> > Hello dear Cassandra community,
>> >
>> > I am a fellow PMC member of Apache Airflow and recently we started to
>> look
>> > at the Cassandra provider of ours in the context of Python 3.12
>> migration
>> > and the integration raised my interest.
>> >
>> > TL;DR; I am quite confused, which client should we use to be
>> future-proof
>> > and I would appreciate the advice of the community on it, also I would
>> like
>> > to understand why there is no community-managed client, as seems that
>> with
>> > the current approach, any Python project (including ASF ones are pretty
>> > much forced to use 3rd-party managed way to use Cassandra, which I find
>> > rather strange.
>> >
>> > Context:
>> >
>> > So far in Apache Airflow we were using
>> > https://github.com/datastax/python-driver/ to connect to Cassandra, but
>> > when we worked on Python 3.12 compatibility.  While looking at it, I
>> > discovered something strange
>> >
>>
>> Mid-donated to the foundation:
>>
>> CEP:
>> https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-8%3A+Datastax+Drivers+Donation
>>
>> [Private@]:
>> https://lists.apache.org/thread/gor4b5l1hc4yokmcmpnhkfvg52w7rpp0
>>
>> Status in board report:
>> https://apache.org/foundation/records/minutes/2023/board_minutes_2023_08_16.txt
>>
>> The Scylla version is a fork WITH ADDITIONS that work with implementation
>> details of Scylladb not present in Apache Cassandra.
>>
>> Preference use "Datastax" driver under donation if at all possible, and
>> get it fixed as rapidly as is practical, but given that Scylla has already
>> fixed the issue in theirs and it's an apache licensed fork of the same
>> code, if you have to ship something to remain functional, that seems like a
>> reasonable fallback.
>>
>>
>>
>>
>>
>>

Re: [DISCUSS] Cassandra 5.0 support for RHEL 7

[Bret McGuire]

   FWIW there isn't any direct relationship between the change in platform
support with 3.29.0 and the vector changes.  3.29.0 included a fix for
PYTHON-1371 which was intended to warn users who might be using variable
length subtypes in vectors.  We're aiming to provide a robust fix for that
issue in PYTHON-1369 but that won't be until the next release... and there
was a desire not to hold up 5.0 work while waiting for that fix.

   This release also followed the Python drivers policy of officially
supporting all Python runtimes that aren't EOL at time of release; that's
what jd was referring to in his earlier comment.  At the time 3.29.0 was
released this covered Python 3.8 through 3.12 so that's what got official
support.

   jd can correct anything I got wrong in there, specifically around the
details of incorporating the new version into cqlsh, but that's the gist of
it.

   - Bret -

On Mon, Mar 11, 2024 at 5:06 PM Brad  wrote:

> Is it different for Java?  How do you get Java 11 on RHEL 7?
>
> On Mon, Mar 11, 2024 at 5:58 PM David Capwell  wrote:
>
>> Is it not possible to install and run python 3.8 on RHEL 7?
>>
>>
>> You have a few options, none really good.
>>
>> 1) build from source
>> 2) a RPM from outside of RHEL; this means you don’t have support and must
>> trust a different third party (not managed by python or RedHat)
>> 3) you use SCL which means every time you want to touch CQLSH you have to
>> remember to enable it (as its per-bash session)
>>
>> These 3 options don’t really work for most deployments
>>
>>
>> On Mar 11, 2024, at 1:12 PM, Brad  wrote:
>>
>> RHEL 7 will reach the end of maintenance on June 30th, 2024 (extended
>> lifecycle support is an option).
>>
>> Is it not possible to install and run python 3.8 on RHEL 7?  I assume
>> that would be necessary to run Java 11 on RHEL 7 with Cassandra 5.0.  It
>> would be a burden for contributors to test with an obsolete version of
>> python -- you can't 'brew install python@3.6' for example.
>>
>> % brew install python@3.6
>> Warning: No available formula with the name "python@3.6"
>>
>> % brew install python@3.7
>> Error: python@3.7 has been disabled because it is deprecated upstream!
>>
>>
>> On Mon, Mar 11, 2024 at 3:38 PM Caleb Rackliffe 
>> wrote:
>>
>>> I can try this out on trunk. Will report back...
>>>
>>> On Mon, Mar 11, 2024 at 2:23 PM J. D. Jordan 
>>> wrote:
>>>
 The Python driver dropped official support for older EOL Python
 versions because they are EOL and no longer tested by the newer driver CI.
 I don’t think there are actually any changes yet that it won’t work in 3.6
 still?  Maybe someone with Python 3.6 installed can change the if and see?
 I think we have some cqlsh tests in dtest?  As long as we as a project run
 those on RHEL 7, I would be comfortable with adding that back to being
 supported. Though maybe just in the rpm package?

 -Jeremiah

 On Mar 11, 2024, at 1:33 PM, Josh McKenzie 
 wrote:

 
 Looks like we bumped from 3.6 requirement to 3.7 in CASSANDRA-18960
  as well -
 similar thing. Vector support in python, though that patch took it from
 "return a simple blob" to "return something the python driver knows about,
 but apparently not variable types so we'll need to upgrade again."

 The version of the Python driver that is used by cqlsh (3.25.0) doesn't
 entirely support the new vector data type introduced by CASSANDRA-18504
 . While we can
 perfectly write data, read vectors are presented as blobs:


 As far as I can tell, support for vector types in cqlsh is the sole
 reason we've bumped to 3.7 and 3.8 to support that python driver. That
 correct Andres / Brandon?

 On Mon, Mar 11, 2024, at 1:22 PM, Caleb Rackliffe wrote:

 The vector issues itself was a simple error message change:
 https://github.com/datastax/python-driver/commit/e90c0f5d71f4cac94ed80ed72c8789c0818e11d0

 Was there something else in 3.29.0 that actually necessitated the move
 to a floor of Python 3.8? Do we generally change runtime requirements in
 minor releases for the driver?

 On Mon, Mar 11, 2024 at 12:12 PM Brandon Williams 
 wrote:

 Given that 3.6 has been EOL for 2+ years[1], I don't think it makes
 sense to add support for it back.

 Kind Regards,
 Brandon

 [1] https://devguide.python.org/versions/

 On Mon, Mar 11, 2024 at 12:08 PM David Capwell 
 wrote:
 >
 > Originally we had planned to support RHEL 7 but in testing 5.0 we
 found out that cqlsh no longer works on RHEL 7[1].  This was changed in
 CASSANDRA-19245 which upgraded python-driver from 3.28.0 to 3.29.0. For
 some reason this minor version upgrade also dropped support for python 3.6
 which is the supported python version 

[DISCUSS] Modeling JIRA fix version for subprojects

[Bret McGuire]

   Greetings all!  For those I haven't met yet I'm Bret and I'm working
mainly on the newly-donated Java driver.  As part of that effort we've hit
upon an issue that we felt needed some additional discussion... and so you
now have an email from me. :)

   Our JIRA instance currently has a single field named "Fix Version/s" to
indicate the Cassandra version which will contain a fix for the
corresponding ticket; the field is populated with some (most? all?)
versions of the server.  The Java driver has a need for something similar,
but in our case we'd like for the options to correspond to Java driver
releases rather than Cassandra server releases.  To be clear there is no
explicit correlation between Java driver releases and any specific server
version or versions.

   How should we model this requirement?  We considered a few options:

* Use the "Fix Version/s" field for both Cassandra and Java driver
versions; basically just add the Java driver versions to what we already
have.  There will be some overlap which could cause some confusion; the
most recent Java driver release was 4.18.0 which looks vaguely similar to,
say, 4.1.x.  Everybody can figure it out but the overlap might make that
more perplexing than we'd like.
* Add Java driver versions but use some sort of prefix specific to the
driver.  So instead of "4.18.0" we might have "java driver 4.18.0".
* Add a new field, perhaps "Java Driver Fix Version/s".  This field is only
used for Java driver tickets and is populated with known driver versions
(e.g. "4.18.0")

   Note that whatever choice is made here would presumably apply to *any*
subproject which maintains its own versioning scheme.

   The general consensus of the conversation was that the third option (a
"Java Driver Fix Version/s" field) was the cleanest option but it seemed
worthwhile raising this to the group as a whole.

   Thanks all!

  - Bret -

Re: [DISCUSS] ccm as a subproject

[Bret McGuire]

   Speaking only for myself I _love_ this idea.  The various drivers use
ccm extensively in their integration test suites so having this tool
in-house and actively looked after would be very beneficial for our work.

   - Bret -

On Wed, May 15, 2024 at 9:23 AM Josh McKenzie  wrote:

> Right now ccm isn't formally a subproject of Cassandra or under governance
> of the ASF. Given it's an integral components of our CI as well as for
> local testing for many devs, and we now have more experience w/our muscle
> on IP clearance and ingesting / absorbing subprojects where we can't track
> down every single contributor to get an ICLA, seems like it might be worth
> revisiting the topic of donation of ccm to Apache.
>
> For what it's worth, Sylvain originally and then DataStax after transfer
> have both been incredible and receptive stewards of the projects and repos,
> so this isn't about any response to any behavior on their part.
> Structurally, however, it'd be better for the health of the project(s)
> long-term to have ccm promoted in. As far as I know there was strong
> receptivity to that donation in the past but the IP clearance was the
> primary hurdle.
>
> Anyone have any thoughts for or against?
>
> https://github.com/riptano/ccm
>
>

Re: [DISCUSS] ccm as a subproject

[Bret McGuire]

   Very much agreed Paulo; I was musing on the idea of adding Docker
support to ccm recently as well.  We'd want to preserve the current ability
to work with releases (and Github branches) but I very much like the idea
of adding Docker support as a new feature.

On Wed, May 15, 2024 at 3:56 PM Paulo Motta  wrote:

> As much as I'd like to remove the dependency on ccm I think we'll stick
> with it for a bit, so +1 on moving under the project umbrella.
>
> In the long term it would be nice to modernize integration test suites to
> use containers instead of processes for more flexibility and fewer
> dependencies for local development. Perhaps an incremental way to do that
> would be to add a docker backend to ccm.
>
> On Wed, May 15, 2024 at 4:25 PM Bret McGuire 
> wrote:
>
>>Speaking only for myself I _love_ this idea.  The various drivers use
>> ccm extensively in their integration test suites so having this tool
>> in-house and actively looked after would be very beneficial for our work.
>>
>>- Bret -
>>
>> On Wed, May 15, 2024 at 9:23 AM Josh McKenzie 
>> wrote:
>>
>>> Right now ccm isn't formally a subproject of Cassandra or under
>>> governance of the ASF. Given it's an integral components of our CI as well
>>> as for local testing for many devs, and we now have more experience w/our
>>> muscle on IP clearance and ingesting / absorbing subprojects where we can't
>>> track down every single contributor to get an ICLA, seems like it might be
>>> worth revisiting the topic of donation of ccm to Apache.
>>>
>>> For what it's worth, Sylvain originally and then DataStax after transfer
>>> have both been incredible and receptive stewards of the projects and repos,
>>> so this isn't about any response to any behavior on their part.
>>> Structurally, however, it'd be better for the health of the project(s)
>>> long-term to have ccm promoted in. As far as I know there was strong
>>> receptivity to that donation in the past but the IP clearance was the
>>> primary hurdle.
>>>
>>> Anyone have any thoughts for or against?
>>>
>>> https://github.com/riptano/ccm
>>>
>>>

[VOTE] Release Apache Cassandra Java Driver 4.18.1

[Bret McGuire]

Greetings all!  This is my first stab at this so apologies in advance if I
get something wrong.

I’m proposing the test build of Cassandra Java Driver 4.18.1 for release.

sha1: cbdde2878786fa6c4077a21352cbe738875f2106

Git: 
https://github.com/apache/cassandra-java-driver/tree/4.18.1

Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1330

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

   Thanks!

  - Bret -

Re: [VOTE] Release Apache Cassandra Java Driver 4.18.1

[Bret McGuire]

   Greetings.  I'm cancelling this vote on the 4.18.1 driver release.  We've 
hit some issues with the Nexus staging repositories that have to be resolved 
before we can proceed.  I'll post a follow-up here when everything has been 
resolved and we're ready to proceed with the vote on this release.

   Thanks all, and apologies for the confusion!

  - Bret -

On 2024/05/20 18:14:02 Bret McGuire wrote:
> Greetings all!  This is my first stab at this so apologies in advance if I
> get something wrong.
> 
> I’m proposing the test build of Cassandra Java Driver 4.18.1 for release.
> 
> sha1: cbdde2878786fa6c4077a21352cbe738875f2106
> 
> Git: <https://github.com/apache/cassandra-java-driver/tree/4.18.0>
> https://github.com/apache/cassandra-java-driver/tree/4.18.1
> 
> Maven Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-1330
> 
> The vote will be open for 72 hours (longer if needed). Everyone who has
> tested the build is invited to vote. Votes by PMC members are considered
> binding. A vote passes if there are at least three binding +1s and no -1's.
> 
>Thanks!
> 
>   - Bret -
> 

[VOTE] Release Apache Cassandra Java Driver 4.18.1 (2nd attempt)

[Bret McGuire]

   Greetings all!  We're going to give this another go.

   Apologies for the confusion that sprang out of our last attempt.  It
appears that the Nexus staging repository for the 4.18.1 release was
accidentally released shortly after it was created.  As a result Maven
artifacts for this release are already out in the wild
,
so this vote will be a little unusual.  We'll be voting normally, but if
the vote is successful we'll simply leave the Maven artifacts exactly where
they are.  If the vote is unsuccessful these artifacts will be removed from
Maven Central and we'll try again with 4.18.2.

   Big thanks to mck and driftx for their help in untangling these issues.

   With all of that said let's get to it.  I’m proposing the test build of
Cassandra Java Driver 4.18.1 for release.

sha1: cbdde2878786fa6c4077a21352cbe738875f2106

Git:  
https://github.com/apache/cassandra-java-driver/tree/4.18.1

Maven Artifacts:
As
discussed above


   The Source release and Binary convenience artifacts are available here:

https://dist.apache.org/repos/dist/dev/cassandra/cassandra-java-driver/4.18.1/


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

   One additional note: this is my first time doing a release of the Java
driver so if you're so inclined you can find my PGP key information in the
KEYS  file.


   Thanks all!


   - Bret -

Re: [VOTE] Release Apache Cassandra Java Driver 4.18.1 (2nd attempt)

[Bret McGuire]

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

Vote passes with five votes (four binding).

Thanks all!

  - Bret -

On Fri, May 24, 2024 at 3:01 PM Benjamin Lerer  wrote:

> +1
>
> Le jeu. 23 mai 2024, 21:30, Brandon Williams  a écrit :
>
>> +1
>>
>> Kind Regards,
>> Brandon
>>
>> On Tue, May 21, 2024 at 5:59 PM Bret McGuire 
>> wrote:
>> >
>> >Greetings all!  We're going to give this another go.
>> >
>> >Apologies for the confusion that sprang out of our last attempt.  It
>> appears that the Nexus staging repository for the 4.18.1 release was
>> accidentally released shortly after it was created.  As a result Maven
>> artifacts for this release are already out in the wild, so this vote will
>> be a little unusual.  We'll be voting normally, but if the vote is
>> successful we'll simply leave the Maven artifacts exactly where they are.
>> If the vote is unsuccessful these artifacts will be removed from Maven
>> Central and we'll try again with 4.18.2.
>> >
>> >Big thanks to mck and driftx for their help in untangling these
>> issues.
>> >
>> >With all of that said let's get to it.  I’m proposing the test build
>> of Cassandra Java Driver 4.18.1 for release.
>> >
>> > sha1: cbdde2878786fa6c4077a21352cbe738875f2106
>> >
>> > Git: https://github.com/apache/cassandra-java-driver/tree/4.18.1
>> >
>> > Maven Artifacts: As discussed above
>> >
>> >
>> >The Source release and Binary convenience artifacts are available
>> here:
>> >
>> >
>> https://dist.apache.org/repos/dist/dev/cassandra/cassandra-java-driver/4.18.1/
>> >
>> >
>> >The vote will be open for 72 hours (longer if needed). Everyone who
>> has tested the build is invited to vote. Votes by PMC members are
>> considered binding. A vote passes if there are at least three binding +1s
>> and no -1's.
>> >
>> >One additional note: this is my first time doing a release of the
>> Java driver so if you're so inclined you can find my PGP key information in
>> the KEYS file.
>> >
>> >
>> >Thanks all!
>> >
>> >
>> >- Bret -
>>
>

[DISCUSS] Request for feedback re: new large features to (potentially) be added to the Apache Cassandra drivers still maintained by DataStax

[Bret McGuire]

   Greetings all!  As we get closer and closer to the release of Apache
Cassandra 5.0 the drivers team at DataStax would like to solicit feedback
from the Cassandra community about what major features users would like to
see across the various actively maintained drivers.  We’re considering
focusing on one of the following:

* Robust support for vectors across all drivers [1]
* Robust support for protocol version 5 across all drivers [2]

   To be clear, we’re discussing adding these features to the drivers that
are actively maintained by DataStax.  CEP-8

discusses
the set of drivers to be donated by DataStax to The Apache Software
Foundation (ASF).  Of these the Java driver has already been donated and
the Ruby and PHP drivers are in maintenance mode, so for this conversation
we’re talking about adding a new feature to the Python, node.js, C/C++ and
C# drivers.  We’re also happy to work with the ASF to keep these changes in
sync with similar functionality in the Java driver.  Finally, we’ll look
into extending support to gocql once it has been donated to the ASF.

   I’ve setup a poll here

so
please let us know which feature above you’d like to see in a Cassandra
driver near you!

   - Bret -


[1] Vectors are currently only supported by the Java, Python and node.js
drivers.  For each of these drivers only float subtypes are supported.
[2] Complete support for the v5 protocol is currently only provided by the
Java driver

Re: [DISCUSS] Request for feedback re: new large features to (potentially) be added to the Apache Cassandra drivers still maintained by DataStax

[Bret McGuire]

   Hey Carlos, thanks for the question!  I'm going to let this poll go
through the end of today, probably actually through the weekend to give
everybody a chance to respond.  After that I will absolutely be posting the
results to this list!

   - Bret -

On Wed, Jul 17, 2024 at 9:05 AM Rolo, Carlos via dev <
dev@cassandra.apache.org> wrote:

> Hello!
>
> Thanks for this! Would you release the results of the poll? That would be
> helpful since we are going to contribute to GoCQL once the donation is in
> place.
>
> Cheers,
>
> Carlos
> ------
> *From:* Bret McGuire 
> *Sent:* 17 July 2024 00:05
> *To:* dev@cassandra.apache.org 
> *Subject:* [DISCUSS] Request for feedback re: new large features to
> (potentially) be added to the Apache Cassandra drivers still maintained by
> DataStax
>
> *EXTERNAL EMAIL - USE CAUTION when clicking links or attachments *
>
>
>Greetings all!  As we get closer and closer to the release of Apache
> Cassandra 5.0 the drivers team at DataStax would like to solicit feedback
> from the Cassandra community about what major features users would like to
> see across the various actively maintained drivers.  We’re considering
> focusing on one of the following:
>
> * Robust support for vectors across all drivers [1]
> * Robust support for protocol version 5 across all drivers [2]
>
>To be clear, we’re discussing adding these features to the drivers that
> are actively maintained by DataStax.  CEP-8
> <https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-8%3A+DataStax+Drivers+Donation>
>  discusses
> the set of drivers to be donated by DataStax to The Apache Software
> Foundation (ASF).  Of these the Java driver has already been donated and
> the Ruby and PHP drivers are in maintenance mode, so for this conversation
> we’re talking about adding a new feature to the Python, node.js, C/C++ and
> C# drivers.  We’re also happy to work with the ASF to keep these changes in
> sync with similar functionality in the Java driver.  Finally, we’ll look
> into extending support to gocql once it has been donated to the ASF.
>
>I’ve setup a poll here
> <https://docs.google.com/forms/d/1oGAxGPfd8Vn9FuJi7RANauPqRc_DkMTnzLOeyCF6Jac/viewform?edit_requested=true>
>  so
> please let us know which feature above you’d like to see in a Cassandra
> driver near you!
>
>- Bret -
>
>
> [1] Vectors are currently only supported by the Java, Python and node.js
> drivers.  For each of these drivers only float subtypes are supported.
> [2] Complete support for the v5 protocol is currently only provided by the
> Java driver
>

Re: [DISCUSS] Request for feedback re: new large features to (potentially) be added to the Apache Cassandra drivers still maintained by DataStax

[Bret McGuire]

   To follow up with this: now that the weekend is over I'm closing the
poll.  The vote count was relatively small (16 votes total) and the
breakdown goes as follows:

* 12 (75%) - Robust support for protocol version 5 across all drivers
* 3 (18.8%) - Robust support for vectors across all drivers
* 1 (6.3%) - No strong preference

   Thanks to everyone who voted!

- Bret -

On Fri, Jul 19, 2024 at 10:48 AM Bret McGuire 
wrote:

>Hey Carlos, thanks for the question!  I'm going to let this poll go
> through the end of today, probably actually through the weekend to give
> everybody a chance to respond.  After that I will absolutely be posting the
> results to this list!
>
>- Bret -
>
> On Wed, Jul 17, 2024 at 9:05 AM Rolo, Carlos via dev <
> dev@cassandra.apache.org> wrote:
>
>> Hello!
>>
>> Thanks for this! Would you release the results of the poll? That would be
>> helpful since we are going to contribute to GoCQL once the donation is in
>> place.
>>
>> Cheers,
>>
>> Carlos
>> --
>> *From:* Bret McGuire 
>> *Sent:* 17 July 2024 00:05
>> *To:* dev@cassandra.apache.org 
>> *Subject:* [DISCUSS] Request for feedback re: new large features to
>> (potentially) be added to the Apache Cassandra drivers still maintained by
>> DataStax
>>
>> *EXTERNAL EMAIL - USE CAUTION when clicking links or attachments *
>>
>>
>>Greetings all!  As we get closer and closer to the release of Apache
>> Cassandra 5.0 the drivers team at DataStax would like to solicit feedback
>> from the Cassandra community about what major features users would like to
>> see across the various actively maintained drivers.  We’re considering
>> focusing on one of the following:
>>
>> * Robust support for vectors across all drivers [1]
>> * Robust support for protocol version 5 across all drivers [2]
>>
>>To be clear, we’re discussing adding these features to the drivers
>> that are actively maintained by DataStax.  CEP-8
>> <https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-8%3A+DataStax+Drivers+Donation>
>>  discusses
>> the set of drivers to be donated by DataStax to The Apache Software
>> Foundation (ASF).  Of these the Java driver has already been donated and
>> the Ruby and PHP drivers are in maintenance mode, so for this conversation
>> we’re talking about adding a new feature to the Python, node.js, C/C++ and
>> C# drivers.  We’re also happy to work with the ASF to keep these changes in
>> sync with similar functionality in the Java driver.  Finally, we’ll look
>> into extending support to gocql once it has been donated to the ASF.
>>
>>I’ve setup a poll here
>> <https://docs.google.com/forms/d/1oGAxGPfd8Vn9FuJi7RANauPqRc_DkMTnzLOeyCF6Jac/viewform?edit_requested=true>
>>  so
>> please let us know which feature above you’d like to see in a Cassandra
>> driver near you!
>>
>>- Bret -
>>
>>
>> [1] Vectors are currently only supported by the Java, Python and node.js
>> drivers.  For each of these drivers only float subtypes are supported.
>> [2] Complete support for the v5 protocol is currently only provided by
>> the Java driver
>>
>

[RELEASE] Apache Cassandra Gocql Driver 1.7.0 released

[Bret McGuire]

The Cassandra team is pleased to announce the release of Cassandra Gocql

Driver version 1.7.0.

The Source release is available here:

https://dist.apache.org/repos/dist/release/cassandra/cassandra-gocql-driver/1.7.0/

The changelog for this release can be found at:

https://github.com/apache/cassandra-gocql-driver/blob/trunk/CHANGELOG.md#170---2024-09-23

Note: this is the first release since the donation of gocql to the Apache
Software Foundation (ASF).  Package names have remained the same for this
release; this will be addressed in future work.  We’ve made changes to
clearly identify this driver as an ASF driver and to bump the minimum Go
version we test against (in accordance with existing gocql standards) but
otherwise this release should behave identically to the prior gocql release.

Thanks all!

[RELEASE] Apache Cassandra Java Driver 4.18.1 released

[Bret McGuire]

The Cassandra team is pleased to announce the release of Cassandra Java

Driver version 4.18.1.  This release occurred on May 28th, 2024 but this
release announcement was missed.  A notice like this one should be included
for future releases but I wanted to include an announcement for 4.18.1 as
well for sake of completeness.

The Source release and Binary convenience artifacts are available here:

https://dist.apache.org/repos/dist/release/cassandra/cassandra-java-driver/4.18.1
/

The Maven artifacts can be found at:

https://repository.apache.org/content/groups/public/org/apache/cassandra/

These will be mirrored to other repositories.

The changelog for this release can be found at:

https://github.com/apache/cassandra-java-driver/tree/4.x/changelog#4181

Thanks all!

[VOTE] Release Apache Cassandra Gocql Driver 1.7.0

[Bret McGuire]

   Greetings all!

   I’m proposing the Cassandra Gocql Driver 1.7.0 for release.

sha1: 953e0df999cabb3f5eef714df9921c00e9f632c2
git: https://github.com/apache/cassandra-gocql-driver/tree/v1.7.0-rc1

   The Source release is available here:
https://dist.apache.org/repos/dist/dev/cassandra/cassandra-gocql-driver/1.7.0/

   This is the first release of the Gocql Driver since its donation.
Developers will include this driver in their projects by specifying a
commit hash or tag in go.mod rather than via the inclusion of binary
artifacts so we’ve avoided the creation of binary artifacts completely.  To
avoid any premature access to this release before the vote is complete
we’ve temporarily used the tag “v1.7.0-rc1” to clearly indicate that this
tag points to a release candidate.  Once the vote passes this tag will be
updated to “v1.7.0”.

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

   Thanks all!

  - Bret -

Re: [VOTE] Release Apache Cassandra Gocql Driver 1.7.0

[Bret McGuire]

   Vote passes with six +1 votes (3 binding).

   Thanks all!

  - Bret -

On Mon, Sep 30, 2024 at 10:19 AM João Reis  wrote:

> +1 (nb)
>
> Bret McGuire  escreveu (quinta, 26/09/2024 à(s)
> 21:46):
>
>>Greetings all!
>>
>>I’m proposing the Cassandra Gocql Driver 1.7.0 for release.
>>
>> sha1: 953e0df999cabb3f5eef714df9921c00e9f632c2
>> git: https://github.com/apache/cassandra-gocql-driver/tree/v1.7.0-rc1
>>
>>The Source release is available here:
>>
>> https://dist.apache.org/repos/dist/dev/cassandra/cassandra-gocql-driver/1.7.0/
>>
>>This is the first release of the Gocql Driver since its donation.
>> Developers will include this driver in their projects by specifying a
>> commit hash or tag in go.mod rather than via the inclusion of binary
>> artifacts so we’ve avoided the creation of binary artifacts completely.  To
>> avoid any premature access to this release before the vote is complete
>> we’ve temporarily used the tag “v1.7.0-rc1” to clearly indicate that this
>> tag points to a release candidate.  Once the vote passes this tag will be
>> updated to “v1.7.0”.
>>
>>The vote will be open for 72 hours (longer if needed). Everyone who
>> has tested the build is invited to vote. Votes by PMC members are
>> considered binding. A vote passes if there are at least three binding +1s
>> and no -1's.
>>
>>Thanks all!
>>
>>   - Bret -
>>
>

[VOTE] Release Apache Cassandra Java Driver 3.12.0

[Bret McGuire]

Greetings all!

   I’m proposing the Cassandra Java Driver 3.12.0 for release.

sha1: dd437b2a973dbccb415a612c4c997659edffd638

git: https://github.com/apache/cassandra-java-driver/tree/3.x

Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1353

   The Source release is available here:

https://dist.apache.org/repos/dist/dev/cassandra/cassandra-java-driver/3.12.0/

   This is the first release of the 3.x Java driver since its donation.
This release is nearly identical to the last DataStax release (3.11.5
).
The full changelog can be found at
https://github.com/apache/cassandra-java-driver/tree/3.x/changelog#3120

   The vote will be open for 120 hours (longer if needed) due to the
upcoming weekend. Everyone who has tested the build is invited to vote.
Votes by PMC members are considered binding. A vote passes if there are at
least three binding +1s and no -1's.

   Thanks!


- Bret -

[VOTE] Release Apache Cassandra Java Driver 4.19.0

[Bret McGuire]

   Greetings all!  I’m proposing the test build of Cassandra Java Driver
4.19.0 for release.

sha1: 46444eaabdbd23e9231123198536d070e99aca27

Git:  
https://github.com/apache/cassandra-java-driver/tree/4.19.0

Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1364/

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

   Thanks!

[RELEASE] Apache Cassandra Java Driver 4.19.0 released

[Bret McGuire]

The Cassandra team is pleased to announce the release of Cassandra Java

Driver version 4.19.0.  This release includes a large number of bug fixes
and improvements representing the work of many contributors.  Thanks to
everyone who made this release possible!


The Source release and Binary convenience artifacts are available here:

https://dlcdn.apache.org/cassandra/cassandra-java-driver/4.19.0/


The Maven artifacts can be found at:

https://repo.maven.apache.org/maven2/org/apache/cassandra/ /

These will be mirrored to other repositories.

The changelog for this release can be found at:

https://github.com/apache/cassandra-java-driver/tree/4.x/changelog#4190

Thanks all!

[RELEASE] Apache Cassandra Java Driver 3.12.1 released

[Bret McGuire]

The Cassandra team is pleased to announce the release of Cassandra Java

Driver version 3.12.1.  This is the first release of the 3.x Java driver to
contain new functionality since its donation to the Apache Software
Foundation.

The Source release and Binary convenience artifacts are available here:
https://dlcdn.apache.org/cassandra/cassandra-java-driver/3.12.1/


The Maven artifacts can be found at:
https://repository.apache.org/content/groups/public/org/apache/cassandra/
under names of the form "cassandra-driver-*" (as distinct from
"java-driver-*" which is used for the 4.x releases).  This release will be
mirrored to other repositories and should now be available from Maven
Central.

The changelog for this release can be found at:
https://github.com/apache/cassandra-java-driver/tree/3.x/changelog#3121


Thanks all!

Re: [VOTE] Release Apache Cassandra Java Driver 3.12.1

[Bret McGuire]

With four +1 votes (3 binding) and zero -1 votes the vote passes.
Thanks all!

- Bret -

On Thu, Jan 23, 2025 at 11:42 AM Maxim Muzafarov  wrote:

> +1 (nb)
>
> On Thu, 23 Jan 2025 at 16:35, Josh McKenzie  wrote:
> >
> > +1
> >
> > On Thu, Jan 23, 2025, at 9:58 AM, Štefan Miklošovič wrote:
> >
> > +1
> >
> > On Sat, Jan 18, 2025 at 10:54 PM Bret McGuire 
> wrote:
> >
> > Greetings all!
> >
> >
> >I’m proposing the Cassandra Java Driver 3.12.1 for release.
> >
> >
> > sha1: 873e6f764a499bd9c5a42cafa53dc77184711eea
> >
> > git: https://github.com/apache/cassandra-java-driver/tree/3.12.1
> >
> > Maven Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-1355
> >
> >
> >The Source release is available here:
> >
> >
> https://dist.apache.org/repos/dist/dev/cassandra/cassandra-java-driver/3.12.1/
> >
> >
> >This is the first release of new functionality for the 3.x Java
> driver since its donation.  Our recent 3.12.0 release was intended to
> provide an ASF-branded baseline for the 3.x Java driver while this release
> is intended to get any changes that might have been waiting in the 3.x
> branch out into the wild.  The full changelog can be found at
> https://github.com/apache/cassandra-java-driver/tree/3.12.1/changelog#3121
> >
> >
> >The vote will be open for 120 hours (longer if needed) due to the
> upcoming holiday weekend. Everyone who has tested the build is invited to
> vote. Votes by PMC members are considered binding. A vote passes if there
> are at least three binding +1s and no -1's.
> >
> >
> >Thanks!
>

[VOTE] Release Apache Cassandra Java Driver 3.12.1

[Bret McGuire]

Greetings all!

   I’m proposing the Cassandra Java Driver 3.12.1 for release.

sha1: 873e6f764a499bd9c5a42cafa53dc77184711eea

git: https://github.com/apache/cassandra-java-driver/tree/3.12.1

Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1355

   The Source release is available here:

https://dist.apache.org/repos/dist/dev/cassandra/cassandra-java-driver/3.12.1/

   This is the first release of new functionality for the 3.x Java driver
since its donation.  Our recent 3.12.0 release was intended to provide an
ASF-branded baseline for the 3.x Java driver while this release is intended
to get any changes that might have been waiting in the 3.x branch out into
the wild.  The full changelog can be found at
https://github.com/apache/cassandra-java-driver/tree/3.12.1/changelog#3121

   The vote will be open for 120 hours (longer if needed) due to the
upcoming holiday weekend. Everyone who has tested the build is invited to
vote. Votes by PMC members are considered binding. A vote passes if there
are at least three binding +1s and no -1's.

   Thanks!

[RELEASE] Apache Cassandra Java Driver 3.12.0 released

[Bret McGuire]

The Cassandra team is pleased to announce the release of Cassandra Java

Driver version 3.12.0.  This is the first release of the 3.x Java driver
since its donation to the Apache Software Foundation.

The Source release and Binary convenience artifacts are available here:
https://dlcdn.apache.org/cassandra/cassandra-java-driver/3.12.0/


The Maven artifacts can be found at:
https://repository.apache.org/content/groups/public/org/apache/cassandra/
under names of the form "cassandra-driver-*" (as distinct from
"java-driver-*" which is used for the 4.x releases).  This release will be
mirrored to other repositories and should now be available from Maven
Central.

The changelog for this release can be found at:
https://github.com/apache/cassandra-java-driver/tree/3.x/changelog#3120


Thanks all!

Re: [VOTE] Release Apache Cassandra Java Driver 3.12.0 (2nd attempt)

[Bret McGuire]

  With six +1 votes (3 binding) and zero -1 votes the vote passes.  Thanks
all!

- Bret -

On Thu, Jan 9, 2025 at 2:12 PM Alexandre DUTRA  wrote:

> +1 (nb)
>
>
> Le jeu. 9 janv. 2025 à 17:21, Sylwester Lachiewicz 
> a écrit :
>
>> +1(nb)
>>
>> czw., 9 sty 2025, 17:13 użytkownik Josh McKenzie 
>> napisał:
>>
>>> +1
>>>
>>> On Wed, Jan 8, 2025, at 11:59 PM, Tolbert, Andy wrote:
>>>
>>> +1 (nb)
>>>
>>> On Wed, Jan 8, 2025 at 8:22 PM Chris Lohfink 
>>> wrote:
>>>
>>> +1
>>>
>>> On Wed, Jan 8, 2025 at 4:14 PM Bret McGuire 
>>> wrote:
>>>
>>> Greetings all!
>>>
>>>I’m proposing the Cassandra Java Driver 3.12.0 for release.  This
>>> represents a second attempt at releasing this version; an earlier attempt
>>> failed due to a staging issue.
>>>
>>> sha1: 1a96d27130ea43ed5762c4f7b7cc182eb24f8952
>>>
>>> git: *https://github.com/apache/cassandra-java-driver/tree/3.x*
>>> <https://github.com/apache/cassandra-java-driver/tree/3.x>
>>>
>>> Maven Artifacts:
>>> https://repository.apache.org/content/repositories/orgapachecassandra-1354
>>>
>>>The Source release is available here:
>>>
>>> *https://dist.apache.org/repos/dist/dev/cassandra/cassandra-java-driver/3.12.0/
>>> <https://dist.apache.org/repos/dist/dev/cassandra/cassandra-java-driver/3.12.0/>*
>>>
>>>To recap: this is the first release of the 3.x Java driver since its
>>> donation.  This release is nearly identical to the last DataStax release (
>>> *3.11.5*
>>> <https://github.com/apache/cassandra-java-driver/releases/tag/3.11.5>).
>>> The full changelog can be found at
>>> *https://github.com/apache/cassandra-java-driver/tree/3.x/changelog#3120*
>>> <https://github.com/apache/cassandra-java-driver/tree/3.x/changelog#3120>
>>>
>>>The vote will be open for 72 hours (longer if needed).  Everyone who
>>> has tested the build is invited to vote. Votes by PMC members are
>>> considered binding. A vote passes if there are at least three binding +1s
>>> and no -1's.
>>>
>>>Thanks!
>>>
>>>
>>> - Bret -
>>>
>>>
>>>

Re: [VOTE] Release Apache Cassandra Java Driver 3.12.0

[Bret McGuire]

   Heads up for everyone: I am cancelling this vote due to an issue with
how I staged the artifacts in Nexus.  I'll be putting up a new request for
a vote shortly.

On Fri, Jan 3, 2025 at 2:54 PM Bret McGuire  wrote:

> Greetings all!
>
>I’m proposing the Cassandra Java Driver 3.12.0 for release.
>
> sha1: dd437b2a973dbccb415a612c4c997659edffd638
>
> git: https://github.com/apache/cassandra-java-driver/tree/3.x
>
> Maven Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-1353
>
>The Source release is available here:
>
>
> https://dist.apache.org/repos/dist/dev/cassandra/cassandra-java-driver/3.12.0/
>
>This is the first release of the 3.x Java driver since its donation.
> This release is nearly identical to the last DataStax release (3.11.5
> <https://github.com/apache/cassandra-java-driver/releases/tag/3.11.5>).
> The full changelog can be found at
> https://github.com/apache/cassandra-java-driver/tree/3.x/changelog#3120
>
>The vote will be open for 120 hours (longer if needed) due to the
> upcoming weekend. Everyone who has tested the build is invited to vote.
> Votes by PMC members are considered binding. A vote passes if there are at
> least three binding +1s and no -1's.
>
>Thanks!
>
>
> - Bret -
>
>

[VOTE] Release Apache Cassandra Java Driver 3.12.0 (2nd attempt)

[Bret McGuire]

Greetings all!

   I’m proposing the Cassandra Java Driver 3.12.0 for release.  This
represents a second attempt at releasing this version; an earlier attempt
failed due to a staging issue.

sha1: 1a96d27130ea43ed5762c4f7b7cc182eb24f8952

git: https://github.com/apache/cassandra-java-driver/tree/3.x

Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1354

   The Source release is available here:

https://dist.apache.org/repos/dist/dev/cassandra/cassandra-java-driver/3.12.0/

   To recap: this is the first release of the 3.x Java driver since its
donation.  This release is nearly identical to the last DataStax release (
3.11.5 ).
The full changelog can be found at
https://github.com/apache/cassandra-java-driver/tree/3.x/changelog#3120

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

   Thanks!


- Bret -

Re: [VOTE] Release Apache Cassandra Java Driver 4.19.0

[Bret McGuire]

With four +1 votes (3 binding) and zero -1 votes the vote passes.
Thanks all!

On Tue, Feb 11, 2025 at 8:02 AM Josh McKenzie  wrote:

> +1
>
> On Mon, Feb 10, 2025, at 6:34 PM, Nate McCall wrote:
>
> +1
> Verified sigs and artifact coordinates.
>
> On Tue, Feb 11, 2025 at 12:30 PM Brandon Williams 
> wrote:
>
> +1
>
> Checked sha/sig, maven artifacts, built on j8.
>
> Kind Regards,
> Brandon
>
> On Thu, Feb 6, 2025 at 4:34 PM Bret McGuire 
> wrote:
> >
> >Greetings all!  I’m proposing the test build of Cassandra Java Driver
> 4.19.0 for release.
> >
> >
> > sha1: 46444eaabdbd23e9231123198536d070e99aca27
> >
> > Git: https://github.com/apache/cassandra-java-driver/tree/4.19.0
> >
> > Maven Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-1364/
> >
> >
> >The vote will be open for 120 hours (longer if needed). Everyone who
> has tested the build is invited to vote. Votes by PMC members are
> considered binding. A vote passes if there are at least three binding +1s
> and no -1's.
> >
> >
> >Thanks!
>
>

Re: Welcome Bret McGuire as Cassandra PMC Member!

[Bret McGuire]

  Thank you everyone for the kind words!

   - Bret -

On Sat, May 17, 2025 at 11:44 PM Patrick McFadin  wrote:

> Welcome Bret and congratulations!
>
> On Sat, May 17, 2025 at 10:46 AM Jaydeep Chovatia <
> chovatia.jayd...@gmail.com> wrote:
>
>> Congratulations!
>>
>> Jaydeep
>>
>> On May 16, 2025, at 6:47 PM, guo Maxwell  wrote:
>>
>> 
>> Congrats!!
>>
>> Jon Haddad  于2025年5月17日周六 08:10写道：
>>
>>> Congrats!!
>>>
>>>
>>> On Fri, May 16, 2025 at 4:13 PM Alexandre DUTRA 
>>> wrote:
>>>
>>>> Great news, and so well deserved! Congratulations Bret!
>>>>
>>>> Le ven. 16 mai 2025 à 19:00, Jeremiah Jordan  a
>>>> écrit :
>>>>
>>>>> Congrats Bret!
>>>>>
>>>>> On May 16, 2025 at 4:00:12 PM, Mick Semb Wever  wrote:
>>>>>
>>>>>>
>>>>>> The Project Management Committee (PMC) for Apache Cassandra is
>>>>>> delighted to announce that Bret McGuire has joined the PMC!  Thank
>>>>>> you Bret for all your contributions to the project over the years,
>>>>>> especially with so many of the drivers.
>>>>>>
>>>>>> The PMC - Project Management Committee - manages and guides the
>>>>>> direction of the project, and is responsible for inviting new committers 
>>>>>> and
>>>>>>  PMC members to steward the longevity of the project.  See
>>>>>> https://community.apache.org/pmc/responsibilities.html if you're
>>>>>> interested in learning more about the rights and responsibilities of
>>>>>> PMC members.
>>>>>>
>>>>>> Please join us in welcoming Bret McGuire to his new role in our
>>>>>> project!
>>>>>>
>>>>>> Mick, on behalf of the Apache Cassandra PMC
>>>>>>
>>>>>