Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Decision Data Store tables

Updated on July 5, 2022

The Decision Data Store service stores large volumes of data. Decision management applications, which require high throughput and low-latency access to data, need this data.

Decision Data Store Table records in the Data-Admin-DDS-Table class represent tables that Pega Platform creates in a backing database, such as Cassandra, when you configure Decision Data Store data sets as data sources in data flows.

Most fields on the Decision Data Store Table form are read-only and you can only configure them when you create a Decision Data Store data set. However, you can modify the consistency level of a table.

The Decision Data Store Table form contains the following fields and controls:

Table details

Details of the Decision Data Store Table instance.

FieldDescription
Table nameName of a table. Unique name in a table group, up to 48 characters long. Table reflects structured data with well defined column family.
Table groupName of a table group that has common tables. Unique name among table groups, up to 48 characters long. A table group is a top-level database object that holds multiple tables. It also controls table replication across cluster nodes in backing database technology.
Consistency levelMinimum number of nodes in the cluster that must acknowledge a read or write operation before the cluster considers the operation successful. You can assign different consistency levels to different table groups. Possible consistency level options:
Eventual
Reads that you perform immediately after writes might return old data. This option is a good choice when performance is paramount.
Strong
Ensures that a data read immediately after a write represents the latest write. To benefit from strong consistency, both the reads and writes must use this setting.
Allow TTLDefines whether the table allows limiting data lifetime.

Partition key

A set of columns that form the partition key. The partition key is a part of the primary key. The backing database uses the partition key to distribute data across nodes. The primary key identifies each unique item in the table and must consist of at least one column. To balance nodes, ensure partition keys have many distinct values.

FieldDescription
Column nameName of a column. Unique name in column family of the table, up to 48 characters long.
TypeType of column. See Column types.

Sort key

A set of columns that form the sort key. The sort key is a part of the primary key. These columns sort data retrieved from a table within a partition in the order that the sort key defines.

FieldDescription
Column nameName of a column. Unique name within column family of the table, up to 48 characters long.
TypeType of column. See Column types.
OrderOrder of the records in a table. Possible options:
  • Ascending
  • Descending

The column type and the underlying implementation of the data store determine the sorting of column values.

Columns

Table columns that are not part of the primary key.

FieldDescription
Column typeName of a column. Unique name in column family of the table, up to 48 characters long.
TypeType of column. See Column types.

Configuration

Additional configuration of the table, defined by key-value entries.

FieldDescription
KeyName of the configuration option in a textual form.
ValueValue for a configuration option in a textual form.

Column types

List of types that can be used when defining a column.

TypeDescription
TextUTF-8 encoded string.
BlobArbitrary bytes (no validation).
Integer32-bit signed integer.
DecimalVariable-precision decimal.
Double64-bit IEEE-754 floating point.
BooleanTrue or false.
TimestampDate and time with millisecond precision, encoded as 8 bytes since the epoch.
DateA date with no corresponding time value.
TimeA 64-bit signed integer representing the number of nanoseconds since midnight.
UUIDA universally unique identifier in standard UUID format.
Long64-bit signed long.
List of StringsA collection of non-unique strings where elements are ordered according to their position in the list. Strings are encoded with UTF-8. (Partition key and Sort key do not allow lists of strings.)
Map of StringsA sorted set of key-value pairs, which creates String (key) to String (value) mapping. Keys are unique, and the map is sorted by its keys. Strings are encoded with UTF-8. (Partition key and Sort key do not allow maps of strings.)
  • Managing Decision Data Store tables

    You can review the Decision Data Store tables in your system to check the entities that Pega Platform created in the backing database and how they map to the higher-level Decision Data Store data sets.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us