[RELEASE] Apache Cassandra Java Driver 4.18.0 released

[Mick Semb Wever]

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://repository.apache.org/content/groups/public/org/apache/cassandra/
These will be mirrored to other repositories.

Note: this is the first release post-donation of the Java Driver.  The
maven coordinates have changed from com.datastax.oss to
org.apache.cassandra, while all package names remain the same.  Migration
of docs and download links on the website are still in progress.


Enjoy!

How to access list with nested maps with Cassandra Java Driver

[Andreas R.]

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 
source compilation failed: Line 3: TypeTokens cannot be resolved"|


And for version like below:

|List>myList =state.getList(5,Map.class);|

The error is like:

|InvalidRequest:Errorfrom server:code=2200[Invalidquery]message="Java 
source compilation failed: Line 3: Type mismatch: cannot convert from 
List to List>|


|state| is a UDT defined as:

|CREATE TYPE count_min_udt(n int,m int,p bigint,hash_a list 
,hash_b list ,values list>>);|


Am I using them wrong? I'd appreciate some help.

Thanks, Andreas

Re: Cassandra java driver linux encoding issue

[Eric Stevens]

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 Chines characteres
>
>
> Code:
>
> ResultSet shopsRS =
> this.cassandraDAO.getshopsFromScanRawByScanId(cassandraSession,"scan_raw",scanid);
> String record = null;
> for (Row row : shopsRS){
> try {
> pProtocol.addEvent(new
> BaseEvent(BaseEvent.LEVEL_ERROR,"Charset.defaultCharset():"+Charset.defaultCharset()));
> record =row.getString("raw_data");
> Helper.verifyEncoding(record);
> String updated_record =
> Helper.addAttributeToJsonString(pProtocol,row.getString("raw_data"),CommonVars.AUX_DATA,CommonVars.AUX_DATA_BATCH_ID,batchId);
> Helper.verifyEncoding(updated_record);
> producer.sendMessage( updated_record);
> counter++;
> } catch (IOException e) {
> pProtocol.addEvent(new BaseEvent(BaseEvent.LEVEL_ERROR,"Could not send
> Message: "));
> e.printStackTrace();
> }
>
>
>
> example text:
>
> "details_product_name":"佛罗伦萨万豪AC酒店(AC Hotel Firenze)|"
>
>
> --
> Rami Dabbah
> 
> Java Professional.
>

Cassandra java driver linux encoding issue

[rami dabbah]

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);
String record = null;
for (Row row : shopsRS){
try {
pProtocol.addEvent(new
BaseEvent(BaseEvent.LEVEL_ERROR,"Charset.defaultCharset():"+Charset.defaultCharset()));
record =row.getString("raw_data");
Helper.verifyEncoding(record);
String updated_record =
Helper.addAttributeToJsonString(pProtocol,row.getString("raw_data"),CommonVars.AUX_DATA,CommonVars.AUX_DATA_BATCH_ID,batchId);
Helper.verifyEncoding(updated_record);
producer.sendMessage( updated_record);
counter++;
} catch (IOException e) {
pProtocol.addEvent(new BaseEvent(BaseEvent.LEVEL_ERROR,"Could not send
Message: "));
e.printStackTrace();
}



example text:

"details_product_name":"佛罗伦萨万豪AC酒店(AC Hotel Firenze)|"


-- 
Rami Dabbah

Java Professional.

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

[Tyler Hobbs]

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..concurrent.ExecutionException
> in, Uninterruptables.getUninterruptibly interrupted gets set to true,
> which does Thread.interrupt()
> thus in DefaultResultSetFuture 
> (ResultSet)Uninterruptibles.getUninterruptibly(this)
> throws exception.
>
> If someone who might have faced a similar issue could provide his/her
> views.
>
> Thanks
> Siddharth
>



-- 
Tyler Hobbs
DataStax 

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

[Siddharth Verma]

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.

If someone who might have faced a similar issue could provide his/her views.

Thanks
Siddharth

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

[Siddharth Verma]

Correction : java driver version : 3.1.0

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

[Siddharth Verma]

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 token range set.

Thanks
Siddharth

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

[Siddharth Verma]

Hi Ben
1. cassandra 3.6
2. driver 3.2
3. Statement : select * from my_ks.my_table1 where token(pk1) >= ? and
token(pk1) https://play.google.com/store/apps/details?id=com.snapdeal.main_source=mobileAppLp_campaign=android>
[image:
A]
<https://itunes.apple.com/in/app/snapdeal-mobile-shopping/id721124909?ls=1=8_source=mobileAppLp_campaign=ios>
[image:
W]
<http://www.windowsphone.com/en-in/store/app/snapdeal/ee17fccf-40d0-4a59-80a3-04da47a5553f>

On Thu, Sep 1, 2016 at 4:56 PM, Ben Slater <ben.sla...@instaclustr.com>
wrote:

> Hi Siddarth,
>
> It would probably help people provide and answer if you let everyone some
> more details like:
> - cassandra version and driver version you are using
> - query that is being executed when the error occurs
> - schema of the table that is being queried
>
> Cheers
> Ben
>
> On Thu, 1 Sep 2016 at 21:19 Siddharth Verma <verma.siddha...@snapdeal.com>
> 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 side on /10.0.230.25:9042: java.lang.AssertionError:
>> [DecoratedKey(3529259302770464040, 53444c373134303435333030),min(
>> 2177391360409801028)]
>> at com.datastax.driver.core.exceptions.ServerError.copy(
>> ServerError.java:63)
>> at com.datastax.driver.core.exceptions.ServerError.copy(
>> ServerError.java:25)
>> at com.datastax.driver.core.DriverThrowables.propagateCause(
>> DriverThrowables.java:37)
>> at com.datastax.driver.core.DefaultResultSetFuture.
>> getUninterruptibly(DefaultResultSetFuture.java:245)
>> at com.datastax.driver.core.AbstractSession.execute(
>> AbstractSession.java:64)
>> at com.personal.trial.MyClass.fetchLoop(MyClass.java:63)
>> at com.personal.trial.MyClass.run(MyClass.java:85)
>> Caused by: com.datastax.driver.core.exceptions.ServerError: An
>> unexpected error occurred server side on /10.0.230.25:9042:
>> java.lang.AssertionError: [DecoratedKey(3529259302770464040,
>> 53444c373134303435333030),min(2177391360409801028)]
>> at com.datastax.driver.core.Responses$Error.asException(
>> Responses.java:108)
>> at com.datastax.driver.core.RequestHandler$
>> SpeculativeExecution.onSet(RequestHandler.java:500)
>> at com.datastax.driver.core.Connection$Dispatcher.
>> channelRead0(Connection.java:1012)
>> at com.datastax.driver.core.Connection$Dispatcher.
>> channelRead0(Connection.java:935)
>> at io.netty.channel.SimpleChannelInboundHandler.channelRead(
>> SimpleChannelInboundHandler.java:105)
>> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(
>> AbstractChannelHandlerContext.java:342)
>> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(
>> AbstractChannelHandlerContext.java:328)
>> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(
>> AbstractChannelHandlerContext.java:321)
>> at io.netty.handler.timeout.IdleStateHandler.channelRead(
>> IdleStateHandler.java:266)
>> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(
>> AbstractChannelHandlerContext.java:342)
>> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(
>> AbstractChannelHandlerContext.java:328)
>> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(
>> AbstractChannelHandlerContext.java:321)
>> at io.netty.handler.codec.MessageToMessageDecoder.channelRead(
>> MessageToMessageDecoder.java:102)
>> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(
>> AbstractChannelHandlerContext.java:342)
>> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(
>> AbstractChannelHandlerContext.java:328)
>> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(
>> AbstractChannelHandlerContext.java:321)
>> at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(
>> ByteToMessageDecoder.java:293)
>> at io.netty.handler.codec.ByteToMessageDecoder.channelRead(
>> ByteToMessageDecoder.java:267)
>> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(
>> AbstractChannelHandlerContext.java:342)
>> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(
>> AbstractChannelHandlerContext.java:328)
>> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(
>> AbstractChannelHandlerContext.java:321)
>> at io.netty.channel.DefaultChann

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

[Ben Slater]

Hi Siddarth,

It would probably help people provide and answer if you let everyone some
more details like:
- cassandra version and driver version you are using
- query that is being executed when the error occurs
- schema of the table that is being queried

Cheers
Ben

On Thu, 1 Sep 2016 at 21:19 Siddharth Verma <verma.siddha...@snapdeal.com>
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 side on /10.0.230.25:9042: java.lang.AssertionError:
> [DecoratedKey(3529259302770464040,
> 53444c373134303435333030),min(2177391360409801028)]
> at
> com.datastax.driver.core.exceptions.ServerError.copy(ServerError.java:63)
> at
> com.datastax.driver.core.exceptions.ServerError.copy(ServerError.java:25)
> at
> com.datastax.driver.core.DriverThrowables.propagateCause(DriverThrowables.java:37)
> at
> com.datastax.driver.core.DefaultResultSetFuture.getUninterruptibly(DefaultResultSetFuture.java:245)
> at
> com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:64)
> at com.personal.trial.MyClass.fetchLoop(MyClass.java:63)
> at com.personal.trial.MyClass.run(MyClass.java:85)
> Caused by: com.datastax.driver.core.exceptions.ServerError: An unexpected
> error occurred server side on /10.0.230.25:9042:
> java.lang.AssertionError: [DecoratedKey(3529259302770464040,
> 53444c373134303435333030),min(2177391360409801028)]
> at
> com.datastax.driver.core.Responses$Error.asException(Responses.java:108)
> at
> com.datastax.driver.core.RequestHandler$SpeculativeExecution.onSet(RequestHandler.java:500)
> at
> com.datastax.driver.core.Connection$Dispatcher.channelRead0(Connection.java:1012)
> at
> com.datastax.driver.core.Connection$Dispatcher.channelRead0(Connection.java:935)
> at
> io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:328)
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:321)
> at
> io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:266)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:328)
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:321)
> at
> io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:328)
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:321)
> at
> io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:293)
> at
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:267)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:328)
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:321)
> at
> io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1280)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:328)
> at
> io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:890)
> at
> io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:564)
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:505)
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:419)
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:391)
> at
&g

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

[Siddharth Verma]

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:
[DecoratedKey(3529259302770464040,
53444c373134303435333030),min(2177391360409801028)]
at
com.datastax.driver.core.exceptions.ServerError.copy(ServerError.java:63)
at
com.datastax.driver.core.exceptions.ServerError.copy(ServerError.java:25)
at
com.datastax.driver.core.DriverThrowables.propagateCause(DriverThrowables.java:37)
at
com.datastax.driver.core.DefaultResultSetFuture.getUninterruptibly(DefaultResultSetFuture.java:245)
at
com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:64)
at com.personal.trial.MyClass.fetchLoop(MyClass.java:63)
at com.personal.trial.MyClass.run(MyClass.java:85)
Caused by: com.datastax.driver.core.exceptions.ServerError: An unexpected
error occurred server side on /10.0.230.25:9042: java.lang.AssertionError:
[DecoratedKey(3529259302770464040,
53444c373134303435333030),min(2177391360409801028)]
at
com.datastax.driver.core.Responses$Error.asException(Responses.java:108)
at
com.datastax.driver.core.RequestHandler$SpeculativeExecution.onSet(RequestHandler.java:500)
at
com.datastax.driver.core.Connection$Dispatcher.channelRead0(Connection.java:1012)
at
com.datastax.driver.core.Connection$Dispatcher.channelRead0(Connection.java:935)
at
io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:328)
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:321)
at
io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:266)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:328)
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:321)
at
io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:328)
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:321)
at
io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:293)
at
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:267)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:328)
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:321)
at
io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1280)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:328)
at
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:890)
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)
at
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:564)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:505)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:419)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:391)
at
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
at java.lang.Thread.run(Thread.java:745)

Thanks
Siddharth

Re: Cassandra Java Driver

[ssiv...@gmail.com]

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.cassandra//
//cassandra-driver-core//
//3.0.0-rc1//

//

//org.apache.cassandra//
//cassandra-all//
//3.1.1//
///

And connect in the next code:

/Cluster.Builder builder = Cluster.builder()
.withProtocolVersion(ProtocolVersion.V4)
.withPort(9042)
.addContactPoint("127.0.0.1");

cluster = builder.build();
Metadata metadata = cluster.getMetadata();/

And it doesn't work. I get the exception:
/com.datastax.driver.core.exceptions.NoHostAvailableException: All 
host(s) tried for query failed (tried: /127.0.0.1:9042 
(com.datastax.driver.core.exceptions.TransportException: [/127.0.0.1] 
Cannot connect))//
//at 
com.datastax.driver.core.ControlConnection.reconnectInternal(ControlConnection.java:231)//
//at 
com.datastax.driver.core.ControlConnection.connect(ControlConnection.java:77)//

//at com.datastax.driver.core.Cluster$Manager.init(Cluster.java:1382)//
//at com.datastax.driver.core.Cluster.getMetadata(Cluster.java:393)/

Everything is ok for C* 2.2.4 when I use
/
$ cqlsh
Connected to Test Cluster at 127.0.0.1:9042.
[cqlsh 5.0.1 | Cassandra 2.2.4 | CQL spec 3.3.1 | Native protocol v4]/

///
//com.datastax.cassandra//
//cassandra-driver-core//
//2.1.9//

//

//org.apache.cassandra//
//cassandra-all//
//3.1.1//
///

/Cluster.Builder builder = Cluster.builder()
.withPort(9042)
.addContactPoint("127.0.0.1");


/C* java driver isn't ready to use?/

/
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 " 
> 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 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 wrote:

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.
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
menu /Product Guide/ > /Datastax Enterprise/ it should
contain DSE versions.

And there's always other sources like the blog.

Cassandra 3.x should be shipped with DSE 5.x early next year.


HTH

-- Brice

On Sat, Dec 26, 2015 at 3:46 AM, Noorul Islam Kamal Malmiyoda
> wrote:

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
mailing list. We do
> not advise users to use this series.
>
> So the most recent driver version compatible with all
versions of Cassandra,
> including 2.2 and 3.x, is now 3.0.0-beta1, although
3.0.0-rc1 will be
> released very soon.
>
> In spite of its "beta" label, version 3.0.0-beta1 has
been thoroughly tested
> against all versions of Cassandra and is definitely
production-ready... as
> long as the Cassandra version in use is also
production-ready. Note however
> that Cassandra 2.2 and 3.0 are quite recent and most
companies AFAICT do not
> consider them yet as production-ready.
>
> Hope that helps,
>
> Alexandre
>
>
> On Tue, Dec 22, 2015 at 4:40 PM Jean Tremblay
> > 

Re: Cassandra Java Driver

[DuyHai Doan]

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 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 wrote:
>
> 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.
>> 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 menu *Product
>> Guide* > *Datastax Enterprise* it should contain DSE versions.
>>
>> And there's always other sources like the blog.
>>
>> Cassandra 3.x should be shipped with DSE 5.x early next year.
>>
>>
>> HTH
>>
>> -- Brice
>>
>> On Sat, Dec 26, 2015 at 3:46 AM, Noorul Islam Kamal Malmiyoda <
>> noo...@noorul.com> wrote:
>>
>>> 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 mailing list. We
>>> do
>>> > not advise users to use this series.
>>> >
>>> > So the most recent driver version compatible with all versions of
>>> Cassandra,
>>> > including 2.2 and 3.x, is now 3.0.0-beta1, although 3.0.0-rc1 will be
>>> > released very soon.
>>> >
>>> > In spite of its "beta" label, version 3.0.0-beta1 has been thoroughly
>>> tested
>>> > against all versions of Cassandra and is definitely
>>> production-ready... as
>>> > long as the Cassandra version in use is also production-ready. Note
>>> however
>>> > that Cassandra 2.2 and 3.0 are quite recent and most companies AFAICT
>>> do not
>>> > consider them yet as production-ready.
>>> >
>>> > Hope that helps,
>>> >
>>> > Alexandre
>>> >
>>> >
>>> > On Tue, Dec 22, 2015 at 4:40 PM Jean Tremblay
>>> >  wrote:
>>> >>
>>> >> 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
>>> >
>>> > --
>>> > Alexandre Dutra
>>> > Driver & Tools Engineer @ DataStax
>>>
>>
>> --
> Alexandre Dutra
> Driver & Tools Engineer @ DataStax
>
>
> --
> Thanks,
> Serj
>
>

Re: Cassandra Java Driver

[ssiv...@gmail.com]

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 wrote:
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.
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 menu
/Product Guide/ > /Datastax Enterprise/ it should contain DSE
versions.

And there's always other sources like the blog.

Cassandra 3.x should be shipped with DSE 5.x early next year.


HTH

-- Brice

On Sat, Dec 26, 2015 at 3:46 AM, Noorul Islam Kamal Malmiyoda
> wrote:

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
mailing list. We do
> not advise users to use this series.
>
> So the most recent driver version compatible with all
versions of Cassandra,
> including 2.2 and 3.x, is now 3.0.0-beta1, although
3.0.0-rc1 will be
> released very soon.
>
> In spite of its "beta" label, version 3.0.0-beta1 has been
thoroughly tested
> against all versions of Cassandra and is definitely
production-ready... as
> long as the Cassandra version in use is also
production-ready. Note however
> that Cassandra 2.2 and 3.0 are quite recent and most
companies AFAICT do not
> consider them yet as production-ready.
>
> Hope that helps,
>
> Alexandre
>
>
> On Tue, Dec 22, 2015 at 4:40 PM Jean Tremblay
> > wrote:
>>
>> 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
>
> --
> Alexandre Dutra
> Driver & Tools Engineer @ DataStax


--
Alexandre Dutra
Driver & Tools Engineer @ DataStax


--
Thanks,
Serj

Re: Cassandra Java Driver

[ssiv...@gmail.com]

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 " 
> 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 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 wrote:

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.
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
menu /Product Guide/ > /Datastax Enterprise/ it should
contain DSE versions.

And there's always other sources like the blog.

Cassandra 3.x should be shipped with DSE 5.x early next year.


HTH

-- Brice

On Sat, Dec 26, 2015 at 3:46 AM, Noorul Islam Kamal Malmiyoda
> wrote:

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
mailing list. We do
> not advise users to use this series.
>
> So the most recent driver version compatible with all
versions of Cassandra,
> including 2.2 and 3.x, is now 3.0.0-beta1, although
3.0.0-rc1 will be
> released very soon.
>
> In spite of its "beta" label, version 3.0.0-beta1 has
been thoroughly tested
> against all versions of Cassandra and is definitely
production-ready... as
> long as the Cassandra version in use is also
production-ready. Note however
> that Cassandra 2.2 and 3.0 are quite recent and most
companies AFAICT do not
> consider them yet as production-ready.
>
> Hope that helps,
>
> Alexandre
>
>
> On Tue, Dec 22, 2015 at 4:40 PM Jean Tremblay
> > wrote:
>>
>> 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
>
> --
> Alexandre Dutra
> Driver & Tools Engineer @ DataStax


-- 
Alexandre Dutra

Driver & Tools Engineer @ DataStax


-- 
Thanks,

Serj



--
Thanks,
Serj

Re: Cassandra Java Driver

[ssiv...@gmail.com]

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 " 
> 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 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 wrote:

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.
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
menu /Product Guide/ > /Datastax Enterprise/ it should
contain DSE versions.

And there's always other sources like the blog.

Cassandra 3.x should be shipped with DSE 5.x early next year.


HTH

-- Brice

On Sat, Dec 26, 2015 at 3:46 AM, Noorul Islam Kamal Malmiyoda
> wrote:

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
mailing list. We do
> not advise users to use this series.
>
> So the most recent driver version compatible with all
versions of Cassandra,
> including 2.2 and 3.x, is now 3.0.0-beta1, although
3.0.0-rc1 will be
> released very soon.
>
> In spite of its "beta" label, version 3.0.0-beta1 has
been thoroughly tested
> against all versions of Cassandra and is definitely
production-ready... as
> long as the Cassandra version in use is also
production-ready. Note however
> that Cassandra 2.2 and 3.0 are quite recent and most
companies AFAICT do not
> consider them yet as production-ready.
>
> Hope that helps,
>
> Alexandre
>
>
> On Tue, Dec 22, 2015 at 4:40 PM Jean Tremblay
> > wrote:
>>
>> 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
>
> --
> Alexandre Dutra
> Driver & Tools Engineer @ DataStax


-- 
Alexandre Dutra

Driver & Tools Engineer @ DataStax


-- 
Thanks,

Serj



--
Thanks,
Serj

Re: Cassandra Java Driver

[ssiv...@gmail.com]

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 " 
> 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 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 wrote:

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.
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
menu /Product Guide/ > /Datastax Enterprise/ it should
contain DSE versions.

And there's always other sources like the blog.

Cassandra 3.x should be shipped with DSE 5.x early next year.


HTH

-- Brice

On Sat, Dec 26, 2015 at 3:46 AM, Noorul Islam Kamal Malmiyoda
> wrote:

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
mailing list. We do
> not advise users to use this series.
>
> So the most recent driver version compatible with all
versions of Cassandra,
> including 2.2 and 3.x, is now 3.0.0-beta1, although
3.0.0-rc1 will be
> released very soon.
>
> In spite of its "beta" label, version 3.0.0-beta1 has
been thoroughly tested
> against all versions of Cassandra and is definitely
production-ready... as
> long as the Cassandra version in use is also
production-ready. Note however
> that Cassandra 2.2 and 3.0 are quite recent and most
companies AFAICT do not
> consider them yet as production-ready.
>
> Hope that helps,
>
> Alexandre
>
>
> On Tue, Dec 22, 2015 at 4:40 PM Jean Tremblay
> > wrote:
>>
>> 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
>
> --
> Alexandre Dutra
> Driver & Tools Engineer @ DataStax


-- 
Alexandre Dutra

Driver & Tools Engineer @ DataStax


-- 
Thanks,

Serj



--
Thanks,
Serj

Re: Cassandra Java Driver

[Alexandre Dutra]

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.
> 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 menu *Product
> Guide* > *Datastax Enterprise* it should contain DSE versions.
>
> And there's always other sources like the blog.
>
> Cassandra 3.x should be shipped with DSE 5.x early next year.
>
>
> HTH
>
> -- Brice
>
> On Sat, Dec 26, 2015 at 3:46 AM, Noorul Islam Kamal Malmiyoda <
> noo...@noorul.com> wrote:
>
>> 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 mailing list. We
>> do
>> > not advise users to use this series.
>> >
>> > So the most recent driver version compatible with all versions of
>> Cassandra,
>> > including 2.2 and 3.x, is now 3.0.0-beta1, although 3.0.0-rc1 will be
>> > released very soon.
>> >
>> > In spite of its "beta" label, version 3.0.0-beta1 has been thoroughly
>> tested
>> > against all versions of Cassandra and is definitely production-ready...
>> as
>> > long as the Cassandra version in use is also production-ready. Note
>> however
>> > that Cassandra 2.2 and 3.0 are quite recent and most companies AFAICT
>> do not
>> > consider them yet as production-ready.
>> >
>> > Hope that helps,
>> >
>> > Alexandre
>> >
>> >
>> > On Tue, Dec 22, 2015 at 4:40 PM Jean Tremblay
>> >  wrote:
>> >>
>> >> 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
>> >
>> > --
>> > Alexandre Dutra
>> > Driver & Tools Engineer @ DataStax
>>
>
> --
Alexandre Dutra
Driver & Tools Engineer @ DataStax

Re: Cassandra Java Driver

[Brice Dutheil]

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 menu *Product
Guide* > *Datastax Enterprise* it should contain DSE versions.

And there's always other sources like the blog.

Cassandra 3.x should be shipped with DSE 5.x early next year.


HTH
-- Brice

On Sat, Dec 26, 2015 at 3:46 AM, Noorul Islam Kamal Malmiyoda <
noo...@noorul.com> wrote:

> 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 mailing list. We do
> > not advise users to use this series.
> >
> > So the most recent driver version compatible with all versions of
> Cassandra,
> > including 2.2 and 3.x, is now 3.0.0-beta1, although 3.0.0-rc1 will be
> > released very soon.
> >
> > In spite of its "beta" label, version 3.0.0-beta1 has been thoroughly
> tested
> > against all versions of Cassandra and is definitely production-ready...
> as
> > long as the Cassandra version in use is also production-ready. Note
> however
> > that Cassandra 2.2 and 3.0 are quite recent and most companies AFAICT do
> not
> > consider them yet as production-ready.
> >
> > Hope that helps,
> >
> > Alexandre
> >
> >
> > On Tue, Dec 22, 2015 at 4:40 PM Jean Tremblay
> >  wrote:
> >>
> >> 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
> >
> > --
> > Alexandre Dutra
> > Driver & Tools Engineer @ DataStax
>

Re: Cassandra Java Driver

[Alexandre Dutra]

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 users to use this series.

So the most recent driver version compatible with all versions of
Cassandra, including 2.2 and 3.x, is now 3.0.0-beta1, although 3.0.0-rc1
will be released very soon.

In spite of its "beta" label, version 3.0.0-beta1 has been thoroughly
tested against all versions of Cassandra and is definitely
production-ready... as long as the Cassandra version in use is also
production-ready. Note however that Cassandra 2.2 and 3.0 are quite recent
and most companies AFAICT do not consider them yet as production-ready.

Hope that helps,

Alexandre


On Tue, Dec 22, 2015 at 4:40 PM Jean Tremblay <
jean.tremb...@zen-innovations.com> wrote:

> 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
>
-- 
Alexandre Dutra
Driver & Tools Engineer @ DataStax

Re: Cassandra Java Driver

[Jean Tremblay]

Thank you very much Alexandre. That is very helpful.

Merry Christmas!!!

On 25 Dec 2015, at 16:38, 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 mailing 
list.
 We do not advise users to use this series.

So the most recent driver version compatible with all versions of Cassandra, 
including 2.2 and 3.x, is now 3.0.0-beta1, although 3.0.0-rc1 will be released 
very soon.

In spite of its "beta" label, version 3.0.0-beta1 has been thoroughly tested 
against all versions of Cassandra and is definitely production-ready... as long 
as the Cassandra version in use is also production-ready. Note however that 
Cassandra 2.2 and 3.0 are quite recent and most companies AFAICT do not 
consider them yet as production-ready.

Hope that helps,

Alexandre


On Tue, Dec 22, 2015 at 4:40 PM Jean Tremblay 
> 
wrote:
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
--
Alexandre Dutra
Driver & Tools Engineer @ DataStax

Re: Cassandra Java Driver

[Noorul Islam Kamal Malmiyoda]

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 mailing list. We do
> not advise users to use this series.
>
> So the most recent driver version compatible with all versions of Cassandra,
> including 2.2 and 3.x, is now 3.0.0-beta1, although 3.0.0-rc1 will be
> released very soon.
>
> In spite of its "beta" label, version 3.0.0-beta1 has been thoroughly tested
> against all versions of Cassandra and is definitely production-ready... as
> long as the Cassandra version in use is also production-ready. Note however
> that Cassandra 2.2 and 3.0 are quite recent and most companies AFAICT do not
> consider them yet as production-ready.
>
> Hope that helps,
>
> Alexandre
>
>
> On Tue, Dec 22, 2015 at 4:40 PM Jean Tremblay
>  wrote:
>>
>> 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
>
> --
> Alexandre Dutra
> Driver & Tools Engineer @ DataStax

Cassandra Java Driver

[Jean Tremblay]

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

Datastax Cassandra Java Driver executeAsynch question.

[Batranut Bogdan]

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 not bother to get the 
exact number. Why? Well because when I query cassandra I have a list of about 
6000 cf keys. I traverse the list and executeAsynch a prepared statement for 
each of these. I have seen that during the execution the driver is waiting for 
free threads to continue if all the threads in the pool are waiting for 
response from C*. 
How can I increase the number of threads that the driver uses to query 
Cassandra?

Re: Datastax Cassandra Java Driver executeAsynch question.

[Alex Popescu]

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.com/forum/#!forum/java-driver-user

[2]:
http://www.datastax.com/drivers/java/2.1/com/datastax/driver/core/PoolingOptions.html

On Mon, Jan 12, 2015 at 9:58 AM, Batranut Bogdan batra...@yahoo.com wrote:

 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 not bother to
 get the exact number. Why? Well because when I query cassandra I have a
 list of about 6000 cf keys. I traverse the list and executeAsynch a
 prepared statement for each of these. I have seen that during the execution
 the driver is waiting for free threads to continue if all the threads in
 the pool are waiting for response from C*.

 How can I increase the number of threads that the driver uses to query
 Cassandra?





-- 

[:-a)

Alex Popescu
Sen. Product Manager @ DataStax
@al3xandru