Re: Datastax Java Driver Compatibility Matrix

Thank you, this information is very helpful. On Tue, Apr 19, 2022 at 11:53 AM C. Scott Andreas wrote: > Hi Jai, > > Cassandra 4.0 supports CQLv3, CQLv4, and CQLv5. A driver connecting using > any of these protocols will work. Cassandra 4.0 did not remove support for > CQLv3 which makes adoption

Re: Datastax Java Driver Compatibility Matrix

Hi Jai,Cassandra 4.0 supports CQLv3, CQLv4, and CQLv5. A driver connecting using any of these protocols will work. Cassandra 4.0 did not remove support for CQLv3 which makes adoption easier for a very large portion of the user community.I'd recommend not specifying the protocol version in your c

Re: Datastax Java Driver Compatibility Matrix

Thank you Scott for the information. I am currently using the 3.2 version of Datastax Driver and using the Cluster Builder with Protocol Version V3. Does this mean 3.2 with protocol version v3 can still work with Cassandra4.0 server? Also from the documentation

Re: Datastax Java Driver Compatibility Matrix

The DataStax Java 3.x drivers work very well with Apache Cassandra 4.0. I'd recommend one of the more recent releases in the series, though (e.g., 3.6.x+).I'm not the author of this documentation, but it may refer to the fact that the 3.x Java Driver supports the CQL v4 wire protocol, but not t

Re: Datastax Java Driver Compatibility Matrix

Hello Erick, It looks like the 3.0+ driver is not compatible with the Cassandra 4.0 as per: https://docs.datastax.com/en/driver-matrix/doc/java-drivers.html The documents say it's partially compatible, what does this mean? What will be broken if I continue to use 3.0+ driver with Cassandra 4.0? I

Re: Datastax Java Driver Compatibility Matrix

Thank you On Monday, April 19, 2021, Erick Ramirez wrote: > Is there a Datastax Java Driver >> >> Compatibility matrix available for Cassandra 4.0? >> > > No, there isn't but the same driver versions apply to C* 4.0

Re: Datastax Java Driver Compatibility Matrix

> > Is there a Datastax Java Driver > > Compatibility matrix available for Cassandra 4.0? > No, there isn't but the same driver versions apply to C* 4.0 under the column 3.0+. Thanks for bringing this up as it has pro

Re: Datastax Java Driver compatibility

The drivers are not maintained by the Cassandra project, it's up to each driver maintainer to list their compatibility. On Tue, Jan 22, 2019 at 10:48 AM Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > Thanks for the response Amanda, > > Yes we can go with the latest version but we are

Re: Datastax Java Driver compatibility

Thanks for the response Amanda, Yes we can go with the latest version but we are trying one change at a time, so want to make sure the version compatibility. b/w any plans to update the documentation for the latest versions for apache cassandra? On Tue, Jan 22, 2019 at 10:28 AM Amanda Moran wrot

Re: Datastax Java Driver compatibility

Hi there- I checked with the team here (at DataStax) and this should work. Any reason you need to stick with Java Driver 3.2, there is a 3.6 release. Thanks! Amanda On Tue, Jan 22, 2019 at 8:45 AM Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > Hello, > > I am looking for Datastax

Re: DataStax Java driver QueryBuilder: CREATE table?

Hi Oliver, SchemaBuilder enables building schema DDL statements like CREATE TABLE, KEYSPACE and so on. You can find some examples in the tests

Re: datastax java driver Batch vs BatchStatement

Hi, Query builder's Batch simply sends a QUERY message through the wire where the query string is a CQL batch statement : "BEGIN BATCH ... APPLY BATCH". BatchStatement actually sends a BATCH message

Re: Datastax Java Driver vs Cassandra 2.1.7

I agree. Thanks a lot. On 23 Jun 2015, at 15:31 , Sam Tunnicliffe mailto:s...@beobal.com>> wrote: Although amending the query is a workaround for this (and duplicating the columns in the selection is not something I imagine one would deliberately do), this is still an ugly regression, so I've o

Re: Datastax Java Driver vs Cassandra 2.1.7

Although amending the query is a workaround for this (and duplicating the columns in the selection is not something I imagine one would deliberately do), this is still an ugly regression, so I've opened https://issues.apache.org/jira/browse/CASSANDRA-9636 to fix it. Thanks, Sam On Tue, Jun 23, 20

Re: Datastax Java Driver vs Cassandra 2.1.7

Hi Sam, You have a real good gut feeling. I went to see the query that I used since many months… which was working…. but obviously there is something wrong with it. The problem with it was *simply* that I placed twice the same field in the select. I corrected in my code and now I don’t have the

Re: Datastax Java Driver vs Cassandra 2.1.7

Can you share the query that you're executing when you see the error and the schema of the target table? It could be something related to CASSANDRA-9532. On Tue, Jun 23, 2015 at 10:05 AM, Jean Tremblay < jean.tremb...@zen-innovations.com> wrote: > Hi, > > I’m using Datastax Java Driver V 2.1.6

Re: Datastax Java Driver connection issue

> Just for clarification, why it is necessary to set the server rpc address to > 127.0.0.1? It's not necessary for it to be 127.0.0.1. But it is necessary for the server to be listening for client connections (the rpc_address) on the same interface / IP you are trying to connect to. In your ca

Re: Datastax Java Driver connection issue

Aaron, Just for clarification, why it is necessary to set the server rpc address to 127.0.0.1? On Mon, Apr 22, 2013 at 2:22 AM, aaron morton wrote: > Make sure that the server rpc_address is set to 127.0.0.1 > > Cheers > > - > Aaron Morton > Freelance Cassandra Consultant > New

Re: Datastax Java Driver connection issue

Make sure that the server rpc_address is set to 127.0.0.1 Cheers - Aaron Morton Freelance Cassandra Consultant New Zealand @aaronmorton http://www.thelastpickle.com On 20/04/2013, at 1:47 PM, Techy Teck wrote: > I am also running into this problem. I have already enabled > st

Re: Datastax Java Driver connection issue

I am also running into this problem. I have already enabled *start_native_transport: true* And by this, I am trying to make a connection- private CassandraDatastaxConnection() { try{ cluster = Cluster.builder().addContactPoint("localhost").build(); session = c

Re: Datastax Java Driver connection issue

@Gabriel, @Wright: thanks, such a silly of me. On Fri, Apr 19, 2013 at 6:48 PM, Keith Wright wrote: > Did you enable the binary protocol in Cassandra.yaml? > > Abhijit Chanda wrote: > > > Hi, > > I have downloaded the CQL driver provided by Datastax using > > com.datast

Re: Datastax Java Driver connection issue

Did you enable the binary protocol in Cassandra.yaml? Abhijit Chanda wrote: Hi, I have downloaded the CQL driver provided by Datastax using com.datastax.cassandra cassandra-driver-core 1.0.0-beta2 Then tried a sample program to connect to

Re: Datastax Java Driver connection issue

Have you started the native transport on cassandra nodes? Look into cassandra.yaml file, for native.transport. By default is disabled. Br, Gabi On 4/19/13 4:16 PM, Abhijit Chanda wrote: Hi, I have downloaded the CQL driver provided by Datastax using com.datastax.cassandra cassandra-dri

Re: Datastax java driver

Ok, thanks for clearing that up. On 23 Nov 2012 07:18, "Sylvain Lebresne" wrote: > Currently, I'm not sure you can really reduce those dependencies. But we > do plan on reducing that ultimately. Basically the reason we have anything > thrift related in there is that so far we depends on the full

Re: Datastax java driver

Currently, I'm not sure you can really reduce those dependencies. But we do plan on reducing that ultimately. Basically the reason we have anything thrift related in there is that so far we depends on the full Cassandra jar. However, we'll pull out the classes uses by the native transport in their

Re: Datastax Java Driver

Great! 2012/11/20 michael.figui...@gmail.com > The Apache Cassandra project has traditionally not focused on client side. > Rather than modifying the scope of the project and jeopardizing the current > driver ecosystem we've preferred to open source it this way. Not that this > driver's license

Re: Datastax Java Driver

The Apache Cassandra project has traditionally not focused on client side. Rather than modifying the scope of the project and jeopardizing the current driver ecosystem we've preferred to open source it this way. Not that this driver's license is Apache License 2 and it will remain so, making it eas

Re: Datastax Java Driver

Why is this being released as a separate project, instead of being bundled up with Cassandra? Is it not a part of Cassandra? 2012/11/19 John Sanda > Fantastic! As for the object mapping API, has there been any > discussion/consideration of http://www.hibernate.org/subprojects/ogm.html? > > > On

Re: Datastax Java Driver

We're currently talking with some guys from Hibernate OGM team. This kind of integration is likely to happen on top of this core module. The mapping module that will add soon isn't alike OGM as it'll be a very thin mapping library, covering most use cases with low overhead. Michaël On Mon, Nov 19

Re: Datastax Java Driver

Fantastic! As for the object mapping API, has there been any discussion/consideration of http://www.hibernate.org/subprojects/ogm.html? On Mon, Nov 19, 2012 at 1:50 PM, Sylvain Lebresne wrote: > Everyone, > > We've just open-sourced a new Java driver we have been working on here at > DataStax. T

Re: Datastax Java Driver

Woohoo! Thanks for making this available. --- Brian O'Neill Lead Architect, Software Development Health Market Science The Science of Better Results 2700 Horizon Drive € King of Prussia, PA € 19406 M: 215.588.6024 € @boneill42 € healthmarketscience.com This