Instance Constructors

1.  new AdvancedConfig(connection: ConnectionConfig = AdvancedConfig.Default.connection, reconnectOnInit: Boolean = AdvancedConfig.Default.reconnectOnInit, reconnectionPolicy: ReconnectionPolicyConfig = AdvancedConfig.Default.reconnectionPolicy, retryPolicy: RetryPolicyConfig = AdvancedConfig.Default.retryPolicy, speculativeExecutionPolicy: SpeculativeExecutionPolicyConfig = AdvancedConfig.Default.speculativeExecutionPolicy, authProvider: Option[AuthProviderConfig] = AdvancedConfig.Default.authProvider, timestampGenerator: TimestampGeneratorConfig = AdvancedConfig.Default.timestampGenerator, requestTracker: RequestTrackerConfig = AdvancedConfig.Default.requestTracker, throttler: ThrottlerConfig = AdvancedConfig.Default.throttler, nodeStateListener: NodeStateListenerConfig = AdvancedConfig.Default.nodeStateListener, schemaChangeListener: SchemaChangeListenerConfig = AdvancedConfig.Default.schemaChangeListener, addressTranslator: AddressTranslatorConfig = AdvancedConfig.Default.addressTranslator, resolveContactPoints: Boolean = AdvancedConfig.Default.resolveContactPoints, protocol: ProtocolConfig = AdvancedConfig.Default.protocol, request: AdvancedRequestConfig = AdvancedConfig.Default.request, metrics: MetricsConfig = AdvancedConfig.Default.metrics, heartbeat: HeartbeatConfig = AdvancedConfig.Default.heartbeat, socket: SocketConfig = AdvancedConfig.Default.socket, metadata: MetadataConfig = AdvancedConfig.Default.metadata, controlConnection: ControlConnectionConfig = AdvancedConfig.Default.controlConnection, preparedStatements: PreparedStatementsConfig = AdvancedConfig.Default.preparedStatements, netty: NettyConfig = AdvancedConfig.Default.netty, coalescer: CoalescerConfig = AdvancedConfig.Default.coalescer)
   connection

   Configures query connection.

   reconnectOnInit

   Whether to schedule reconnection attempts if all contact points are unreachable on the first initialization attempt. If this is true, the driver will retry according to the reconnection policy. The SessionBuilder.build() call -- or the future returned by SessionBuilder.buildAsync() -- won't complete until a contact point has been reached. If this is false and no contact points are available, the driver will fail.

   reconnectionPolicy

   The policy that controls how often the driver tries to re-establish connections to down nodes.

   retryPolicy

   The policy that controls if the driver retries requests that have failed on one node.

   speculativeExecutionPolicy

   The policy that controls if the driver pre-emptively tries other nodes if a node takes too long to respond.

   authProvider

   if None no authentication will occur.

   timestampGenerator

   The generator that assigns a microsecond timestamp to each request.

   requestTracker

   A session-wide component that tracks the outcome of requests. By default com.datastax.oss.driver.internal.core.trackerNoopRequestTracker is used.

   throttler

   A session-wide component that controls the rate at which requests are executed. By default PassThroughRequestThrottler is used.

   nodeStateListener

   A session-wide component that listens for node state changes. By default com.datastax.oss.driver.internal.core.metadata.NoopNodeStateListener is used.

   schemaChangeListener

   A session-wide component that listens for node state changes. By default com.datastax.oss.driver.internal.core.metadata.schema.NoopSchemaChangeListener is used.

   addressTranslator

   The address translator to use to convert the addresses sent by Cassandra nodes into ones that the driver uses to connect. By default com.datastax.oss.driver.internal.core.addresstranslation.PassThroughAddressTranslator is used.

   resolveContactPoints

   Whether to resolve the addresses passed to Basic.contactPoints. If this is true, addresses are created with InetSocketAddress(String, int): the host name will be resolved the first time, and the driver will use the resolved IP address for all subsequent connection attempts. If this is false, addresses are created with InetSocketAddress.createUnresolved(): the host name will be resolved again every time the driver opens a new connection. This is useful for containerized environments where DNS records are more likely to change over time (note that the JVM and OS have their own DNS caching mechanisms, so you might need additional configuration beyond the driver).

   protocol

   The native protocol to use which defines the format of the binary messages between driver and Cassandra.

   request

   Request configuration.

   metrics

   Metrics configuration. Disabled by default.

   heartbeat

   Heartbeat configuration to check if node is alive.

   socket

   Socket configuration.

   metadata

   Metadata about the Cassandra cluster.

   controlConnection

   Configures dedicated administrative connection.

   preparedStatements

   Prepared statements configuration.

   netty

   Netty configuration which is used internally by driver.

   coalescer

   The component that coalesces writes on the connections.