Chris Splinter

<h1>What's New With Drivers for DSE 6</h1>

<p>The last major <a href="https://www.datastax.com/products/datastax-studio-and-development-tools#DataStax-Studio">DataStax Enterprise</a> ( DSE ) release was <a href="https://www.datastax.com/2016/06/introducing-datastax-enterprise-5-0">really really big</a>, and after it we had to look in the mirror and ask ourselves: How can we continue to raise this bar? The answer? <a href="https://www.datastax.com/products/datastax-enterprise-6">DSE 6</a>.</p>

<p>With this most recent major DSE release, we took what was already the best distribution of Apache Cassandra™ and made it faster, more resilient, and more intuitive to operate. For a breakdown of these server-side improvements <em>a la carte</em>, head on over to the <a href="https://www.datastax.com/2018/04/datastax-enterprise-6-the-distributed-cloud-database-designed-for-hybrid-cloud">DataStax Enterprise 6 blog post</a>.&nbsp; In this DataStax Drivers blog post, we will give you the client-side scoop on what’s been added to facilitate interacting with DSE 6.</p>

<h1>DSE Graph Fluent API Batches</h1>

<p><a href="https://academy.datastax.com/download-drivers">DataStax Drivers</a> now offer the ability to execute DSE Graph statements in batches. To accomplish this, they leverage CQL Batch under the covers and these DSE Graph Fluent API batches are subject to the same <a href="https://docs.datastax.com/en/dse/6.0/cql/cql/cql_using/useBatch.html">considerations</a>. It’s advised to limit these to vertices and edges that share the same partition key or involve very little unique partitions to reduce coordinator burden and the number of DSE nodes involved. The design was bound to an ease-of-use commitment ( see <a href="https://github.com/csplinter/datastax-drivers-examples/blob/master/dse-graph-batches/java/BatchFluentAPI/src/main/java/BatchFluentAPIExample.java">Java Example</a>, <a href="https://github.com/csplinter/datastax-drivers-examples/blob/master/dse-graph-batches/python/batch_fluent_api_example.py">Python Example</a> ).</p>

<h1>DSE Graph Fluent API - C# and Node.js</h1>

<p>We are very proud to also announce that DSE Graph Fluent API support has extended to more of the DataStax Drivers-supported languages. This continues to build on the momentum that Java and Python started and now this same programmatic style of writing and executing DSE Graph queries through the DataStax Drivers can be accomplished through the C# and Node.js DataStax Drivers. Check out the <a href="https://academy.datastax.com/content/c-fluent-api-dse-graph-released">C# blog post</a> and <a href="https://docs.datastax.com/en/developer/nodejs-dse-graph/latest/">Node.js documentation</a> for more detail.</p>

<h1>Driver Metadata</h1>

<h2>NodeSync Information in Table Metadata</h2>

<p>Goodbye Repair, Hello DSE NodeSync. Repair in Apache Cassandra™ is the process of making sure that the data on disk across your cluster is in sync. Though this may sound simple, we know that operating and monitoring this action in previous DSE versions was a burden. With DSE 6, this burden is gone and NodeSync now does this for you automatically.</p>

<p>The DataStax Drivers allow you to view NodeSync information via the table metadata. See this <a href="https://github.com/csplinter/datastax-drivers-examples/blob/master/nodesync/README.md">example</a> showing how to verify that NodeSync is enabled on a given table and enjoy the peace of mind that comes with knowing that the data you are receiving in your applications is correct and uniform across your underlying servers.</p>

<h2>Ports Added to Host Metadata</h2>

<p>To facilitate the development of applications that need to connect to both native storage and JMX ports, we added these to the Host class metadata. Happy coding.</p>

<h1>Continuous Paging</h1>

<p>For those who soaked up DSE 5.1, the concept of <a href="https://www.datastax.com/dev/blog/dse-continuous-paging-tuning-and-support-guide">Continuous Paging</a> may sound familiar. If you have not yet reaped the benefits via DSE Analytics, then give it some thought in DSE 6, because we have made this feature even sturdier and more efficient.</p>

<p>At a high level, the performance gains produced by this feature are sourced from the fact that we are continuously preparing result pages on the server side in response to a query. This removes the inefficient chitter chatter from client to server that occurs with normal paging when requesting the next pages of results.</p>

<p>With DSE 6 we’ve improved the communication mechanism in the paging solution such that the driver specifies a number of pages of rows with the initial request and then requests more as it consumes them. Tangibly, this allows Continuous Paging queries to be safely made alongside other queries over the same driver connection without disrupting the connection when the server is producing results faster than the client can handle.</p>

<p>The shiny new <a href="https://www.datastax.com/2018/05/introducing-datastax-bulk-loader">DataStax Bulk Loader</a> also sports the improved performance profile that Continuous Paging delivers. I suggest giving that a look if you are loading or unloading data in large quantities.</p>

<h1>Prepared Statement Robustness</h1>

<p>Recent DataStax Drivers releases have made strides in making prepared statements more durable.</p>

<p>If you have multiple clients connected to the same host, we fixed a case where the driver metadata could become invalid if the underlying schema had been altered (ie, a column has been added or dropped). If you had been working around the issue <a href="https://docs.datastax.com/en/developer/java-driver/3.3/manual/statements/prepared/#avoid-preparing-select-queries">documented here</a> by not preparing your SELECT* statements, you can now remove that workaround if you upgrade to the latest version of DSE and the DataStax Drivers. See this <a href="https://github.com/csplinter/datastax-drivers-examples/blob/master/prepared-statements/README.md">example</a> to hammer this home.</p>

<h1>Keyspace Per Query Support</h1>

<p>To wrap up, we addressed the situation when your queries and keyspaces are independent of one another. In the most recent driver versions, you can now supply the keyspace as an option for your statements, rather than resorting to having separate sessions per keyspace or some other hackery. These <a href="https://github.com/csplinter/datastax-drivers-examples/blob/master/keyspace-per-query/README.md">examples</a> illustrate this usability improvement.</p>

<h1>Additional Search Conditionals</h1>

<p>The integration of DSE Search was further tightened in DSE 5.1 with the ability to control search indexes through CQL. This journey continues with DSE 6 as native CQL queries can now leverage search indexes for a wider array of CQL query functionality and indexing support. The DataStax Drivers remain in lock step with the DSE server side functionality and the new search conditionals can be found in the Java Driver Query Builder ( see <a href="https://github.com/csplinter/datastax-drivers-examples/blob/master/query-builder-search-conditionals/README.md">example</a> ).</p>

<h1>Get Started Now</h1>

<p>You can <a href="https://academy.datastax.com/download-drivers">download</a> the new <a href="https://academy.datastax.com/download-drivers">DSE 6 drivers</a> now and check out our <a href="https://docs.datastax.com/en/developer/driver-matrix/doc/common/driverMatrix.html">online documentation</a> for help and guidance.</p>


What’s New With Drivers for DSE 6

Chris SplinterProduct Management

Discover more

Share

More Company

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

DataStax Has Achieved ISO 27001 Certification

Keeping the Momentum Rolling with Google Cloud

My Internship Journey: A Dive into AI

NoSQL and Vector DB
for Generative AI,
Instantly, At Scale