ReadConsistency

Specifies how many replicas must respond to a read request before returning data to the client application.

all | quorum | one | all | each_quorum | quorum | local_quorum | one | two | three | local_one | serial | local_serial

If set to all, data is returned to the application after all replicas have responded. This setting provides the highest consistency and lowest availability.

(Cassandra 2.x only) If set to each_quorum, data is returned after a quorum of replicas in each data center of the cluster has responded.

If set to quorum, data is returned after a quorum of replicas has responded from any data center.

If set to local_quorum, data is returned after a quorum of replicas in the same data center as the coordinator node has responded. This setting voids latency of inter-data center communication.

If set to one, data is returned from the closest replica. This setting provides the highest availability, but increases the likelihood of stale data being read.

If set to two, data is returned from two of the closest replicas.

If set to three, data is returned from three of the closest replicas.

If set to local_one, data is returned from the closest replica in the local data center.

If set to serial, the data is read without proposing a new addition or update. Uncommitted transactions are committed as part of the read.

If set to local_serial, the data within a data center is read without proposing a new addition or update. Uncommitted transactions within the data center are committed as part of the read.

setReadConsistency

quorum

String