Alexandre Dutra

<p>The Java driver team is pleased to announce that version 3.2.0 of the DataStax Java driver for Apache Cassandra® has just been released.</p>

<p>We would like to stress that this release has been made possible thanks to a strong and vibrant community involvement. Our team and our company are thankful to all of you that contributed, directly or indirectly, to make our driver even better, with a special shout-out to 3 Github users:&nbsp;<a href="https://github.com/avivcarmis">@avivcarmis</a>,&nbsp;<a href="https://github.com/wimtie">@wimtie</a>&nbsp;and&nbsp;<a href="https://github.com/gnoremac">@gnoremac</a>.</p>

<p>In this post, we will focus on the most significant changes brought by this new release; you can also consult the full&nbsp;<a href="http://docs.datastax.com/en/developer/java-driver/3.2/changelog/">changelog</a>&nbsp;and our&nbsp;<a href="http://docs.datastax.com/en/developer/java-driver/3.2/upgrade_guide/#3-2-0">upgrade guide</a>&nbsp;for details about how to migrate existing applications.</p>

<p>&nbsp;</p>

<h2 id="perf">Performance and Usability Enhancements</h2>

<p>This release is the first one to provide&nbsp;<a href="https://datastax-oss.atlassian.net/browse/JAVA-1328">full compatibility</a>&nbsp;with recent Guava versions up to 21.0 inclusive. By default, the driver now uses version 19.0, but any version from 16.0.1 to 21.0 can be used.</p>

<p>According to our internal benchmarks, this version is also noticeably faster than any previous version in the 3.x series thanks to a few performance improvements, among which the&nbsp;<a href="https://datastax-oss.atlassian.net/browse/JAVA-1308">performance boost</a>&nbsp;in a&nbsp;<a href="http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/core/CodecRegistry.html">core component</a>&nbsp;of the driver. Users are strongly encouraged to migrate to 3.2.0 as soon as possible to benefit from these.</p>

<h2 id="ssl">Enhanced SSL options</h2>

<p>The current&nbsp;<a href="http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/core/SSLOptions.html"><code>SSLOptions</code></a>&nbsp;interface does not allow implementors to perform hostname verification. Thanks to&nbsp;<a href="https://datastax-oss.atlassian.net/browse/JAVA-1364">JAVA-1364</a>, this is now possible, using the newly-introduced&nbsp;<a href="http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/core/RemoteEndpointAwareSSLOptions.html"><code>RemoteEndpointAwareSSLOptions</code></a>&nbsp;sub-interface, that exposes a&nbsp;<a href="http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/core/RemoteEndpointAwareSSLOptions.html#newSSLHandler-io.netty.channel.socket.SocketChannel-java.net.InetSocketAddress-">new method</a>&nbsp;giving implementors access to the remote endpoint address.</p>

<p>This new sub-interface comes with two new concrete implementations:&nbsp;<a href="http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/core/RemoteEndpointAwareJdkSSLOptions.html"><code>RemoteEndpointAwareJdkSSLOptions</code></a>&nbsp;and&nbsp;<a href="http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/core/RemoteEndpointAwareNettySSLOptions.html"><code>RemoteEndpointAwareNettySSLOptions</code></a>. Note that the old&nbsp;<code>SSLOptions</code>&nbsp;interface and its direct implementations are now deprecated. Read more about SSL configuration in our&nbsp;<a href="http://docs.datastax.com/en/developer/java-driver/3.2/manual/ssl/#driver-configuration">online documentation</a>.</p>

<h2 id="mapper">Mapper Configuration</h2>

<p>This release brings substantial enhancements to the driver's&nbsp;<a href="http://docs.datastax.com/en/developer/java-driver/3.2/manual/object_mapper">object mapper</a>; thanks to&nbsp;<a href="https://datastax-oss.atlassian.net/browse/JAVA-1310">JAVA-1310</a>&nbsp;and&nbsp;<a href="https://datastax-oss.atlassian.net/browse/JAVA-1316">JAVA-1316</a>, users can now customize certain aspects of the mapping process itself by defining&nbsp;<em>strategies</em>.</p>

<p>For example, by default the mapper tries to map all the properties found in your Java data model. You might want to take an "opt-in" approach instead and only map the ones that are explicitly annotated with&nbsp;<a href="http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/mapping/annotations/Column.html"><code>@Column</code></a>&nbsp;or&nbsp;<a href="http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/mapping/annotations/Field.html"><code>@Field</code></a>; this is now possible thanks to a&nbsp;<a href="http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/mapping/PropertyTransienceStrategy.html">dedicated strategy</a>. Similarly, you might want to tell the mapper to ignore certain parent classes in your class hierarchy; this is also made possible by&nbsp;<a href="http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/mapping/HierarchyScanStrategy.html">another strategy</a>.</p>

<p>Another common need is to customize the way Cassandra column names are inferred. Out of the box, Java property names are simply lowercased: a&nbsp;<code>userName</code>&nbsp;Java property is mapped to the&nbsp;<code>username</code>&nbsp;column. It is now possible to map it to something else instead, e.g.&nbsp;<code>user_name</code>&nbsp;or&nbsp;<code>USERNAME</code>, by simply configuring the&nbsp;<a href="http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/mapping/NamingStrategy.html">relevant strategy</a>.</p>

<p>Strategies can be supplied through a new class,&nbsp;<a href="http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/mapping/MappingConfiguration.html"><code>MappingConfiguration</code></a>. Read more about the object mapper configuration in our&nbsp;<a href="http://docs.datastax.com/en/developer/java-driver/3.2/manual/object_mapper/using#mapping-configuration">online documentation</a>.</p>

<h2 id="duration">Support for the&nbsp;<code>duration</code>&nbsp;type</h2>

<p>This release also brings&nbsp;<a href="https://datastax-oss.atlassian.net/browse/JAVA-1397">full support</a>&nbsp;for the new CQL&nbsp;<code>duration</code>&nbsp;type. This type has been&nbsp;<a href="https://issues.apache.org/jira/browse/CASSANDRA-11873">introduced</a>&nbsp;in Apache Cassandra® 3.10, and although its primary purpose is to be used in CQL statements to specify either&nbsp;<a href="https://issues.apache.org/jira/browse/CASSANDRA-11936">restrictions</a>&nbsp;– e.g.&nbsp;<code>WHERE time &lt; now() + 2h</code>&nbsp;– or&nbsp;<a href="https://issues.apache.org/jira/browse/CASSANDRA-11871">aggregations</a>&nbsp;– e.g.&nbsp;<code>GROUP BY floor(time, 2h)</code>&nbsp;–, it can also be used as a regular CQL type. The driver now supports such a usage through the new&nbsp;<a href="http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/core/Duration.html"><code>Duration</code></a>&nbsp;class (however, there are no dedicated methods for it in the&nbsp;<a href="http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/core/Row.html"><code>Row</code></a>&nbsp;interface nor in the&nbsp;<a href="http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/core/BoundStatement.html"><code>BoundStatement</code></a>&nbsp;class; users are expected to set and retrieve&nbsp;<code>Duration</code>&nbsp;instances through the generic&nbsp;<a href="http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/core/GettableByIndexData.html#get-int-java.lang.Class-"><code>get()</code></a>&nbsp;and&nbsp;<a href="http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/core/SettableByIndexData.html#set-int-V-java.lang.Class-"><code>set()</code></a>&nbsp;methods).</p>

<h2 id="getting-the-driver">Getting the driver</h2>

<p>As always, the driver is available from&nbsp;<a href="http://docs.datastax.com/en/developer/java-driver/3.2/#getting-the-driver">Maven</a>&nbsp;and from our&nbsp;<a href="http://downloads.datastax.com/java-driver/cassandra-java-driver-3.2.0.tar.gz">downloads server</a>.</p>

<p>We're also running a&nbsp;<a href="http://goo.gl/forms/qwUE6qnL7U">platform and runtime survey</a>&nbsp;to improve our testing infrastructure. Your feedback would be most appreciated.</p>


DataStax Java Driver: 3.2.0 released!

Alexandre Dutra

Discover more

Share

Share

More Company

DataStax Acquires Langflow to Accelerate Generative AI Development

The Top 5 DataStax Stories from 2023

2023 Recap: Data = AI

DataStax Astra DB Nabs Three Prestigious 2023 TrustRadius “Best of” Awards, Dominates the Vector Databases Category

One-stop Data API for Production GenAI