The version of the driver in a tuple format
The version of the driver in a string format
Spcifies how many replicas must respond for an operation to be considered a success. By default, ONE is used for all operations.
Only requires that one replica receives the write or the coordinator stores a hint to replay later. Valid only for writes.
Only one replica needs to respond to consider the operation a success
Two replicas must respond to consider the operation a success
Three replicas must respond to consider the operation a success
ceil(RF/2) replicas must respond to consider the operation a success
All replicas must respond to consider the operation a success
Requires a quorum of replicas in the local datacenter
Requires a quorum of replicas in each datacenter
For conditional inserts/updates that utilize Cassandra’s lightweight transactions, this requires consensus among all replicas for the modified data.
Sends a request only to replicas in the local datacenter and waits for one response.
There were not enough live replicas to satisfy the requested consistency level, so the coordinator node immediately failed the request without forwarding it to any replicas.
The requested ConsistencyLevel
The number of replicas that needed to be live to complete the operation
The number of replicas that were actually alive
Replicas failed to respond to the coordinator node before timing out.
The requested ConsistencyLevel
The number of required replica responses
The number of replicas that responded before the coordinator timed out the operation
A subclass of Timeout for read operations.
This indicates that the replicas failed to respond to the coordinator node before the configured timeout. This timeout is configured in cassandra.yaml with the read_request_timeout_in_ms and range_request_timeout_in_ms options.
A boolean indicating whether the requested data was retrieved by the coordinator from any replicas before it timed out the operation
A subclass of Timeout for write operations.
This indicates that the replicas failed to respond to the coordinator node before the configured timeout. This timeout is configured in cassandra.yaml with the write_request_timeout_in_ms option.
An attempt was made to create a keyspace or table that already exists.
The name of the keyspace that already exists, or, if an attempt was made to create a new table, the keyspace that the table is in.
The name of the table that already exists, or, if an attempt was make to create a keyspace, None.
A query was made that was invalid for some reason, such as trying to set the keyspace for a connection to a nonexistent keyspace.
The current user is not authorized to perfom the requested operation.