The way a data set is configured to represent data depends on the data set type.

Database Table Type

Define the keys.

• The Database Table section displays the database table name the class is mapped to.
• In the Selectable Keys section, add as many keys entries as necessary, and map each key to a property.
• In the Partitioning key section, select the property used to split the data into as many equal segments as possible across DNodes.
  • To ensure a balanced distribution, select a property that is suitable for partitioning. For example, assuming a table containing customer information, country information is a suitable property for partitioning since it contains enough shared distinct values, but email address is not as it typically has as many distinct values as customer entries.
  • Another consideration is the correlation between amount of segments (the grouped distinct values delivered by the property) and number of DNodes. The ideal distribution is considered to be as many segments as DNodes.

Decision Data Store Type

Define the keys.

• The keys that you specify in a data set define the data records managed in the Cassandra internal storage. Add as many keys entries as necessary and map each key to a property.
• The first property in the list of keys is the partitioning key used to distribute data across different decision nodes. To keep the decision nodes balanced, make sure you use a partitioning key property with many distinct values.
• Changing keys in an existing data set is not supported. You have to create another instance.

Visual Business Director Type

No configuration required. The data set instance is automatically configured with the Visual Business Director server location as defined by the Visual Business Director connection.

About Data Set rules