Click or drag to resize

MetadataSyncOptions Class

See the api reference for WithMetadataSyncOptions(MetadataSyncOptions) for an explanation of the Metadata synchronization feature. See the api reference for the properties of this class in order to know what the default values are.
Inheritance Hierarchy
SystemObject
  CassandraMetadataSyncOptions

Namespace:  Cassandra
Assembly:  Cassandra (in Cassandra.dll) Version: 3.11.0
Syntax
C#
public class MetadataSyncOptions

The MetadataSyncOptions type exposes the following members.

Constructors
  NameDescription
Public methodMetadataSyncOptions
Initializes a new instance of the MetadataSyncOptions class
Top
Properties
  NameDescription
Public propertyMaxTotalRefreshSchemaDelay
Use SetMaxTotalRefreshSchemaDelay(Int64) to set this value. The default value is
10000
. Also check the api reference for SetMaxTotalRefreshSchemaDelay(Int64) for a more thorough explanation.
Public propertyMetadataSyncEnabled
Use SetMetadataSyncEnabled(Boolean) to set this value. The default value is
true
. Also check the api reference for WithMetadataSyncOptions(MetadataSyncOptions) for a more thorough explanation.
Public propertyRefreshSchemaDelayIncrement
Use SetRefreshSchemaDelayIncrement(Int64) to set this value. The default value is
1000
. Also check the api reference for SetRefreshSchemaDelayIncrement(Int64) for a more thorough explanation.
Top
Methods
  NameDescription
Public methodSetMaxTotalRefreshSchemaDelay

The default value is

10000
.

The driver will never wait more than maxTotalRefreshSchemaDelay milliseconds until a schema or topology refresh event is processed even if events keep being scheduled for processing.

Public methodSetMetadataSyncEnabled

The default value is

true
.

Enables or disables the Metadata synchronization feature of the driver. See the api reference for WithMetadataSyncOptions(MetadataSyncOptions) for a more thorough explanation.

Public methodSetRefreshSchemaDelayIncrement

The default value is

1000
.

The driver will wait refreshSchemaDelayIncrement milliseconds until it processes a schema or topology refresh event. If another event gets scheduled to be processed within this interval, then the driver will cancel the first execution and will wait another refreshSchemaDelayIncrement milliseconds until it processes both events. As long as events keep coming in, then the driver will keep postponing the execution up until MaxTotalRefreshSchemaDelay milliseconds have passed since the first unprocessed event was scheduled.

Top
See Also