Decision Data Store tables
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.
| Field | Description |
| Table name | Name of a table. Unique name in a table group, up to 48 characters long. Table reflects structured data with well defined column family. |
| Table group | Name 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 level | Minimum 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:
|
| Allow TTL | Defines 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.
| Field | Description |
| Column name | Name of a column. Unique name in column family of the table, up to 48 characters long. |
| Type | Type 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.
| Field | Description |
| Column name | Name of a column. Unique name within column family of the table, up to 48 characters long. |
| Type | Type of column. See Column types. |
| Order | Order of the records in a table. Possible options:
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.
| Field | Description |
| Column type | Name of a column. Unique name in column family of the table, up to 48 characters long. |
| Type | Type of column. See Column types. |
Configuration
Additional configuration of the table, defined by key-value entries.
| Field | Description |
| Key | Name of the configuration option in a textual form. |
| Value | Value for a configuration option in a textual form. |
Column types
List of types that can be used when defining a column.
| Type | Description |
| Text | UTF-8 encoded string. |
| Blob | Arbitrary bytes (no validation). |
| Integer | 32-bit signed integer. |
| Decimal | Variable-precision decimal. |
| Double | 64-bit IEEE-754 floating point. |
| Boolean | True or false. |
| Timestamp | Date and time with millisecond precision, encoded as 8 bytes since the epoch. |
| Date | A date with no corresponding time value. |
| Time | A 64-bit signed integer representing the number of nanoseconds since midnight. |
| UUID | A universally unique identifier in standard UUID format. |
| Long | 64-bit signed long. |
| List of Strings | A 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 Strings | A 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.
Previous topic Tracing Decision Data Store operations Next topic Managing Decision Data Store tables