[RELEASE] Java driver 3.3.2 and DSE driver 1.4.2

[Olivier Michallat]

We've just published two patch releases to address a case sensitivity issue detected in the previous versions (JAVA-1666). In addition, we included beta support for an upcoming Cassandra 4 ticket (JAVA-1196 / CASSANDRA-10786), and a few minor improvements.

Changelog for 3.3.2 and DSE 1.4.2:

- [bug] JAVA-1666: Fix keyspace export when a UDT has case-sensitive field names.

- [improvement] JAVA-1196: Include hash of result set metadata in prepared statement id.

- [improvement] JAVA-1670: Support user-provided JMX ports for CCMBridge.

- [improvement] JAVA-1661: Avoid String.toLowerCase if possible in Metadata.

- [improvement] JAVA-1659: Expose low-level flusher tuning options.

- [improvement] JAVA-1660: Support netty-transport-native-epoll in OSGi container.

The drivers are available from the usual locations:

<dependency>

  <groupId>com.datastax.cassandra</groupId>

  <artifactId>cassandra-driver-core</artifactId>

  <version>3.3.2</version>

</dependency>

<dependency>

  <groupId>com.datastax.dse</groupId>

  <artifactId>dse-java-driver-core</artifactId>

  <version>1.4.2</version>

</dependency>

http://downloads.datastax.com/java-driver/

--

The Java driver team

[Pavani T]

Hi all,

I am creating secondary indexes on cassandra table which contains almost 1 cr data.It takes a lot of time so i need to forcefully stop it.And in one server it takes above 3300% cpu ..very low in other servers.I don't know why it takes that much cpu in only one server.

Thanks and  Regards

Pavs

[Henry Hottelet]

Olivier,

I have been testing with the cassandra-driver-core version 3.3.2, and recently upgraded.  It runs just fine standalone, however when I containerize with Docker, and run inside a Docker container, I see this problem.

I know that previous versions of the cassandra-driver-core have been able to establish transport connections inside Docker, however, there were manifestations of improper closing of connections at improper times, due to prematurely exiting open connection streams.  I believe I had done the right thing, by upgrading to the latest of the cassandra-driver-core, however, that has diminished any hope of supporting Docker or Kubernetes, due to this NoHostAvailableException, and TransportException.

Will this latest dse-java-driver-core release help fix the following error, how does it help, and to what degree does it replace or augment the cassandra-driver-core.  Do I have to start replacing API calls for the cassandra-driver-core with dse-java-driver-core?  If so, do you have examples?  

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:9042] Cannot connect))

at com.datastax.driver.core.ControlConnection.reconnectInternal(ControlConnection.java:232) ~[cassandra-driver-core-3.3.2.jar!/:na]

at com.datastax.driver.core.ControlConnection.connect(ControlConnection.java:79) ~[cassandra-driver-core-3.3.2.jar!/:na]

at com.datastax.driver.core.Cluster$Manager.negotiateProtocolVersionAndConnect(Cluster.java:1600) ~[cassandra-driver-core-3.3.2.jar!/:na]

at com.datastax.driver.core.Cluster$Manager.init(Cluster.java:1518) ~[cassandra-driver-core-3.3.2.jar!/:na]

at com.datastax.driver.core.Cluster.init(Cluster.java:159) ~[cassandra-driver-core-3.3.2.jar!/:na]

at com.datastax.driver.core.Cluster.connectAsync(Cluster.java:330) ~[cassandra-driver-core-3.3.2.jar!/:na]

at com.datastax.driver.core.Cluster.connect(Cluster.java:280) ~[cassandra-driver-core-3.3.2.jar!/:na]

at guru.springframework.cassandra.SessionUtil.querySchema(SessionUtil.java:251) ~[classes!/:0.0.1-SNAPSHOT]

at guru.springframework.controllers.RestaurantController.getRestaurants(RestaurantController.java:270) [classes!/:0.0.1-SNAPSHOT]

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_111]

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_111]

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_111]

at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_111]

at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:205) [spring-web-4.3.8.RELEASE.jar!/:4.3.8.RELEASE]