DataStax Java Driver for Apache Cassandra User Mailing List

Greetings! Today we've released new versions of both the 4.x and 3.x Java driver. This release

I was just looking at this very ticket today in fact. I hope to have some follow-up information on

After discussing this and reading the doc entry again, we're confirming that it is a typo in the

Switching to QUORUM will make it worse, not better. Which version of the driver are you using?

Greetings! Today we've released new versions of both the 4.x and 3.x Java driver. The primary

Hello Cedrick, Thanks a lot for your response & support. I'll try to implement the second

Greetings all! Today we've released new versions of both the 4.x and 3.x Java drivers. 4.14.0

Question also asked at : https://stackoverflow.com/questions/70691127/cassandra-read-performance-slow

Hi, As you suggested try the 4.x java driver, I have observed following things with this driver. Case

Thanks Madhavan for your response. On Tue, Nov 30, 2021 at 10:12 PM Madhavan Sridharan <madhavan.

Absolutely, yes I'd love to contribute a PR! Created https://datastax-oss.atlassian.net/browse/

Thank you, Alexandre Dutra, especially for JAVA-2949! We wanted to upgrade to 4.x but without this

Thanks Alexandre and Madhavan for your responses. Regards Manish On Wed, Jul 7, 2021 at 9:55 PM

Yes, I knew you could use a URL, but that really doesn't solve the underlying issue. I would

Hi, We just released two new versions of the 4.x Java driver: 4.11.2 and 4.12.0. 4.11.2 is a patch

Hi, First of all, some context: if you are looking for atomicity guarantees, you should know that

Upon more reading, it might be because the retry policy doesn't kick in if the query isn't

Hi Francisco, in our query handler we have many strategies to define overload conditions and then we

Hi, We just released a new bugfix version of the 4.x Java driver: 4.11.1. The most important change

Hi Driver Community, We are getting below error in our new relic , based on below thread its due to

Hi Driver Community, We are getting below error in our new relic , based on below thread its due to

Hello, I was inspecting the bytes-sent and bytes-received metrics and was pretty surprised. It looks

Hi, We just released a new minor version of the 4.x Java driver: 4.11.0. The most important change is

Hi, We just released a new minor version of the legacy 3.x driver: 3.11.0. The most important change

Hi， Can anyone review my root cause analysis and the pull request ? 1. root cause: https://datastax-

Hi, The Java driver team is pleased to announce that driver 4.10.0 was released last week. This minor

My question can be found here: https://stackoverflow.com/questions/65527651/how-to-create-a-long-

Hi- I've finally had the chance to use the 4.x series driver after being a longtime user of the 3

To be fair, the whole effort wasn't lost, it is just a surprise that a reduction in dependencies

I can see it could be tricky because there's dual packaging, also some optional features even in