Consistency is used to provide consistency guarantees for read operations.
ABSOLUTE consistency may be specified to guarantee that
current values are read. EVENTUAL consistency means
that the values read may be very slightly out of date.
ABSOLUTE consistency results in higher cost, consuming
twice the number of read units for the same data relative to
EVENTUAL consistency, and should only be used when
required.
It is possible to set a default Consistency for a NoSQLClient
instance by providing it in the initial configuration as
consistency. In JSON configuration file, you may use string
values such as "EVENTUAL" or "ABSOLUTE". If no consistency is specified
for an operation and there is no default value,
EVENTUAL is used.
Consistency can be specified in the options(opt) argument for all
read operations.
Consistency is used to provide consistency guarantees for read operations.
ABSOLUTE consistency may be specified to guarantee that current values are read. EVENTUAL consistency means that the values read may be very slightly out of date. ABSOLUTE consistency results in higher cost, consuming twice the number of read units for the same data relative to EVENTUAL consistency, and should only be used when required.
It is possible to set a default Consistency for a NoSQLClient instance by providing it in the initial configuration as consistency. In JSON configuration file, you may use string values such as "EVENTUAL" or "ABSOLUTE". If no consistency is specified for an operation and there is no default value, EVENTUAL is used.
Consistency can be specified in the options(opt) argument for all read operations.