[RELEASE] Apache Cassandra Java Driver 4.18.1 released

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

[RELEASE] Apache Cassandra Java Driver 4.18.0 released

The Cassandra team is pleased to announce the release of Cassandra Java Driver version 4.18.0 The Source release and Binary convenience artifacts are available here: https://dist.apache.org/repos/dist/release/cassandra/cassandra-java-driver/4.18.0/ The Maven artifacts can be found at: https

How to access list with nested maps with Cassandra Java Driver

I am having trouble with getting a list including maps with |Cassandra Java Driver|. For below version: |List>myList =state.getList(5,TypeTokens.mapOf(Integer.class,Integer.class));| The error is like: |InvalidRequest:Errorfrom server:code=2200[Invalidquery]message="Java

Re: Cassandra java driver linux encoding issue

What is the value returned from Charset.defaultCharset() on both systems? On Wed, May 16, 2018 at 5:00 AM rami dabbah wrote: > Hi, > > I am trying to query text filed from Cassandra using java driver see code > below. In windows it is working fine but in linux i am getting ?? > instead of Ch

Cassandra java driver linux encoding issue

Hi, I am trying to query text filed from Cassandra using java driver see code below. In windows it is working fine but in linux i am getting ?? instead of Chines characteres Code: ResultSet shopsRS = this.cassandraDAO.getshopsFromScanRawByScanId(cassandraSession,"scan_raw",scanid); Stri

Re: ServerError: An unexpected error occurred server side; in cassandra java driver

There should be a corresponding error and stacktrace in your cassandra logs on 10.0.230.25. Please find that and post it, if you can. On Thu, Sep 1, 2016 at 7:23 AM, Siddharth Verma < verma.siddha...@snapdeal.com> wrote: > Debugged the issue a little. > AbstractFuture.get() throws java.util..con

Re: ServerError: An unexpected error occurred server side; in cassandra java driver

Debugged the issue a little. AbstractFuture.get() throws java.util..concurrent.ExecutionException in, Uninterruptables.getUninterruptibly interrupted gets set to true, which does Thread.interrupt() thus in DefaultResultSetFuture (ResultSet)Uninterruptibles.getUninterruptibly(this) throws exception.

Re: ServerError: An unexpected error occurred server side; in cassandra java driver

Correction : java driver version : 3.1.0

Re: ServerError: An unexpected error occurred server side; in cassandra java driver

Update : I page on the ResultSet explicitly in the program( *boundStatement.setPagingState(PagingState.fromString(currentPageInfo));*) When i put a *limit 10* after select statement, there is no error, with the token range set i provided it However, without that, there is this error, on second toke

Re: ServerError: An unexpected error occurred server side; in cassandra java driver

2016 at 21:19 Siddharth Verma > wrote: > >> Hi, >> Could someone help me out with the following exception in cassandra java >> driver. >> Why did it occur? >> MyClass program is paging on the result set. >> >> com.datastax.driver.core.exceptions

Re: ServerError: An unexpected error occurred server side; in cassandra java driver

Siddharth Verma wrote: > Hi, > Could someone help me out with the following exception in cassandra java > driver. > Why did it occur? > MyClass program is paging on the result set. > > com.datastax.driver.core.exceptions.ServerError: An unexpected error > occurred server s

ServerError: An unexpected error occurred server side; in cassandra java driver

Hi, Could someone help me out with the following exception in cassandra java driver. Why did it occur? MyClass program is paging on the result set. com.datastax.driver.core.exceptions.ServerError: An unexpected error occurred server side on /10.0.230.25:9042: java.lang.AssertionError

Re: Cassandra Java Driver

Trying to connect to C* v3.1.1 cluster. It works nice with cqlsh /$ cqlsh// //Connected to Test Cluster at 127.0.0.1:9042.// //[cqlsh 5.0.1 | Cassandra 3.1.1 | CQL spec 3.3.1 | Native protocol v4]/ But doesn't work with /cassandra-driver-core/. I use next mvn deps: /// //com.datastax.cassan

Re: Cassandra Java Driver

No...It doesn't work for C* 2.2.4 too..( On 12/30/2015 04:48 PM, DuyHai Doan wrote: Check protocol version when you create your Cluster object on the client side Le 30 déc. 2015 13:33, "ssiv...@gmail.com " mailto:ssiv...@gmail.com>> a écrit : I've just tried

Re: Cassandra Java Driver

Sorry, setting protocol version to V4 doesn't work for C* 3.1.1. I sure, for C* 2.2.4 it will work...Will check On 12/30/2015 04:48 PM, DuyHai Doan wrote: Check protocol version when you create your Cluster object on the client side Le 30 déc. 2015 13:33, "ssiv...@gmail.com

Re: Cassandra Java Driver

I set it to ProtocolVersion.V4 (the highest). On 12/30/2015 04:48 PM, DuyHai Doan wrote: Check protocol version when you create your Cluster object on the client side Le 30 déc. 2015 13:33, "ssiv...@gmail.com " mailto:ssiv...@gmail.com>> a écrit : I've just t

Re: Cassandra Java Driver

Check protocol version when you create your Cluster object on the client side Le 30 déc. 2015 13:33, "ssiv...@gmail.com" a écrit : > I've just tried to use cassandra-driver-core-3.0.0_rc1 and > cassandra-driver-core-3.0.0_beta1 with C* 2.2.4 (cassandra-all-2.2.4). And > neither of them can connec

Re: Cassandra Java Driver

I've just tried to use cassandra-driver-core-3.0.0_rc1 and cassandra-driver-core-3.0.0_beta1 with C* 2.2.4 (cassandra-all-2.2.4). And neither of them can connect to the local cluster. But cassandra-driver-core-2.1.9. Am I doing wrong? Happy New Year! On 12/28/2015 04:08 PM, Alexandre Dutra

Re: Cassandra Java Driver

FYI, Java driver 3.0.0-rc1 has just been released . On Sat, Dec 26, 2015 at 11:15 AM Brice Dutheil wrote: > Not yet. The latestest DSE (4.8.3) is shipped with a patched version of > Cassandra 2.11. >

Re: Cassandra Java Driver

Not yet. The latestest DSE (4.8.3) is shipped with a patched version of Cassandra 2.11. You can find this information on their website. 4.8 Release note : https://docs.datastax.com/en/datastax_enterprise/4.8/datastax_enterprise/RNdse.html >From this page in the menu you can navigate and unroll the

Re: Cassandra Java Driver

Is DSE shipping with 3.x ? Thanks and Regards Noorul On Fri, Dec 25, 2015 at 9:07 PM, Alexandre Dutra wrote: > Hi Jean, > > You should use 3.0.0-beta1. > > TL;DR > > DataStax Java driver series 2.2.x has been discontinued in favor of series > 3.x; we explained why in this mail to the Java driver

Re: Cassandra Java Driver

Thank you very much Alexandre. That is very helpful. Merry Christmas!!! On 25 Dec 2015, at 16:38, Alexandre Dutra mailto:alexandre.du...@datastax.com>> wrote: Hi Jean, You should use 3.0.0-beta1. TL;DR DataStax Java driver series 2.2.x has been discontinued in favor of series 3.x; we explai

Re: Cassandra Java Driver

Hi Jean, You should use 3.0.0-beta1. TL;DR DataStax Java driver series 2.2.x has been discontinued in favor of series 3.x; we explained why in this mail to the Java driver mailing list . We do not advise

Cassandra Java Driver

Hi, Which Java Driver is suited for Cassandra 2.2.x. ? I see datastax 3.0.0 beta1 and datastax 2.2.0 rc3... Are they suited for production? Is there anything better? Thanks for your comments and replies? Jean

Re: Datastax Cassandra Java Driver executeAsynch question.

Hi Bogdan, This question would be better on the specific driver's mailing list. Assuming you are using the Java driver the mailing list is [1]. As for your question look into PoolingOptions [2] that you pass when configuring the Cluster instance. [1]: https://groups.google.com/a/lists.datastax.co

Datastax Cassandra Java Driver executeAsynch question.

Hello all, In my implementation of the FutureCallBack<> interface in the onSuccess method, I put Thread.currentThread.getName(). What I saw was that there is a ThreadPool... That is all fine, but seems to me that the pool does not have that many threads. About 10 from my observations - I did no