Builder Methods

You should not modify this object directly as change made to the returned object may not be used by the cluster build. Instead, you should use the other methods of this Builder

Use this method when a custom authentication scheme is in place. You shouldn't call both this method and {@code withCredentials}' on the same Builder instance as one will supersede the other

This should be used if the Cassandra cluster has been configured to use the PasswordAuthenticator. If the the default * AllowAllAuthenticator is used instead, using this method has no effect.

Adds Execution Profiles to the Cluster instance.

Execution profiles are like configuration presets, multiple methods of the driver accept an execution profile name which is like telling the driver which settings to use for that particular request. This makes it easier to change settings like ConsistencyLevel and ReadTimeoutMillis on a per request basis.

Note that subsequent calls to this method will override the previously provided profiles.

To add execution profiles you can use WithProfile(String, ActionIExecutionProfileBuilder):

Cluster.Builder()
        .WithExecutionProfiles(options => options
            .WithProfile("profile1", profileBuilder => profileBuilder
                .WithReadTimeoutMillis(10000)
                .WithConsistencyLevel(ConsistencyLevel.LocalQuorum)))
        .Build()

If no load balancing policy is set through this method, Policies.DefaultLoadBalancingPolicy will be used instead.

Limits the maximum protocol version used to connect to the nodes

When it is not set, the protocol version used is negotiated between the driver and the Cassandra cluster upon establishing the first connection.

Useful when connecting to a cluster that contains nodes with different major/minor versions of Cassandra. For example, preparing for a rolling upgrade of the Cluster.

Limits the maximum protocol version used to connect to the nodes

When it is not set, the protocol version used is negotiated between the driver and the Cassandra cluster upon establishing the first connection.

Useful when connecting to a cluster that contains nodes with different major/minor versions of Cassandra. For example, preparing for a rolling upgrade of the Cluster.

DDL queries introduce schema changes that need to be propagated to all nodes in the cluster. Once they have settled on a common version, we say that they are in agreement.

If not set through this method, the default value (10 seconds) will be used.

If not set through this method, the default value options will be used (metadata synchronization is enabled by default). The api reference of MetadataSyncOptions specifies what is the default for each option.

In case you disable Metadata synchronization, please ensure you invoke RefreshSchemaAsync(String, String) in order to keep the token metadata up to date otherwise you will not be getting everything you can out of token aware routing, i.e. TokenAwarePolicy, which is enabled by the default.

Disabling this feature has the following impact:

• Token metadata will not be computed and stored. This means that token aware routing (TokenAwarePolicy, enabled by default) will only work correctly if you keep the token metadata up to date using the RefreshSchemaAsync(String, String) method. If you wish to go this route of manually refreshing the metadata then it's recommended to refresh only the keyspaces that this application will use, by passing the
  Copy

  keyspace

  parameter.
• Keyspace metadata will not be cached by the driver. Every time you call methods like GetTable(String, String), GetKeyspace(String) and other similar methods of the Metadata class, the driver will query that data on demand and will not cache it.
• The driver will not handle
  Copy

  SCHEMA_CHANGED

  responses. This means that when you execute schema changing statements through the driver, it will not update the schema or topology metadata automatically before returning.

When this option is set, SELECT, UPDATE, DELETE, and BATCH statements on COMPACT STORAGE tables function in "compatibility" mode which allows seeing these tables as if they were "regular" CQL tables.

This option only affects interactions with tables using COMPACT STORAGE and it is only supported by C* 3.0.16+, 3.11.2+, 4.0+ and DSE 6.0+.

This will cause that synchronous operations like Execute(String) to throw a TimeoutException after the specified number of milliseconds.

20,000

If no reconnection policy is set through this method, Policies.DefaultReconnectionPolicy will be used instead.

When the retry policy is not set with this method, the DefaultRetryPolicy will be used instead.

Use a IExtendedRetryPolicy implementation to cover all error scenarios.

If no speculative execution policy is set through this method, DefaultSpeculativeExecutionPolicy will be used instead.

This feature is only available with protocol version 3 or above of the native protocol. With earlier versions, timestamps are always generated server-side, and setting a generator through this method will have no effect.

If no generator is set through this method, the driver will default to client-side timestamps by using AtomicMonotonicTimestampGenerator.