You can store decision management-related records in a Cassandra database-based Decision Data Store data set that is provided in Pega Platform. Horizontally scalable and supported by decision data nodes, decision data stores take data from different sources and make it available for real-time and batch processing. To use Cassandra to its full potential, use Decision Data Store data sets to manage large and active data sets that are a source of data for Visual Business Director reporting, delayed adaptive learning, and so on.
- In Dev Studio, click .
- In the Label field, enter the data set label.
- From the Type list, select Decision Data Store.
- Provide the ruleset, Applies To class, and ruleset version of the data set.
- Click Create and open.
- Define at least one data set key by performing the following actions:
- On the Decision Data Store tab, click Add key.
- Place the cursor in the Property field and press the Down Arrow key.
- Select a property that you want to use as a key. Keys uniquely identify each record in the Decision Data Store data set. The first key in the list is used to create partitions and to distribute data across multiple decision data nodes.
- To improve update times, add exposed properties by performing the following
- In the Advanced section, click the Expand icon.
- Place the cursor in the Exposed fields field and press the Down Arrow key.
- Select a property that you want to expose. The exposed property is added as a separate column in the Cassandra table. This construction provides for faster update times in cases when you want to update a single property only, without the need to update the full record.
- Optional: For page list properties only, if you want to create a list of property values each time the property is updated instead of overwriting the previous property value with the latest one, select the Optimize for appending check box.
- Click Save.
- Migrating data between Decision Data Store data sets
You can migrate data between two sibling Decision Data Store data sets. By using this option, you can transfer records between sibling data sets that are part of different rulesets or sibling data sets that part of different versions of the same ruleset and do not share a data schema (for example, as a result of having a different set of exposed properties). With this option, you can quickly and efficiently migrate data between related rulesets and re-use it in different applications. Additionally, no data is lost when you migrate data between