| Class and Description |
|---|
| com.datastax.driver.dse.auth.DseAuthProvider
in favor of
DseGSSAPIAuthProvider
Please look at DseGSSAPIAuthProvider documentation for configuration |
| com.datastax.driver.core.policies.IdempotenceAwareRetryPolicy
As of version 3.1.0, the driver doesn't retry non-idempotent statements for write timeouts or unexpected
errors anymore. It is no longer necessary to wrap your retry policies in this policy.
|
| com.datastax.driver.core.JdkSSLOptions
Use
RemoteEndpointAwareJdkSSLOptions instead. |
| com.datastax.driver.dse.LoggingIdempotenceAwareRetryPolicy
As of release 1.1.0, dse driver now depends on driver-core 3.1.0, which doesn't retry non-idempotent
statements for write timeouts or unexpected errors anymore.
|
| com.datastax.driver.core.NettySSLOptions
Use
RemoteEndpointAwareNettySSLOptions instead. |
| Method and Description |
|---|
| com.datastax.driver.core.querybuilder.BuiltStatement.escapeId(String)
preserved for backward compatibility, use
Metadata.quoteIfNecessary(String) instead. |
| com.datastax.driver.core.Host.getDseWorkload()
This method returns only the first workload reported by the host;
use
Host.getDseWorkloads() instead. |
| com.datastax.driver.mapping.Mapper.Option.getType()
This method is public for backward compatibility only. It should not be accessible since it leaks
a package-private type.
|
| com.datastax.driver.core.Host.isDseGraphEnabled()
As of DSE 5.1, users should determine whether
this host has the graph workload enabled by inspecting the contents of
Host.getDseWorkloads() instead. Note that this method will throw UnsupportedOperationException if the
system tables do not contain a "graph" column. |
| com.datastax.driver.mapping.Mapper.mapAliased(ResultSet)
you no longer need to specify whether a result set is aliased, it will be detected automatically. Use
Mapper.map(ResultSet) instead of this method. |
| com.datastax.driver.core.SSLOptions.newSSLHandler(SocketChannel) |
Copyright © 2012–2018. All rights reserved.