Resolved Issues

Enhancement added to customize Cassandra consistency level

Inconsistent results were seen when the Cassandra database was queried from the Connect-Cassandra integration connector ruleset. During the queries, data is collected from different systems and loaded into the Cassandra database. If there is a distributed architecture, there is a risk that not all replicas will receive all the insert/updates at the time of the data load for any number of reasons (node down, node overwhelmed, network, etc.).With the default of consistency level 1, the Pega Cassandra query may hit a node that is missing the data requested. However, consistency level 2 forces Cassandra to read matching data from two nodes and in the background will perform a read repair on the node that is missing data. In order to enable the setting of a preferred consistency level for all connectors and for all operations, a new single DSS setting has been introduced: RS: Pega-BigData purpose:connector/Cassandra/consistency available values: " ALL ANY EACH_QUORUM LOCAL_ONE LOCAL_QUORUM LOCAL_SERIAL ONE QUORUM SERIAL THREE TWO"