Question
Instellars Global Consulting Private Ltd
IN
Last activity: 5 Jul 2024 7:53 EDT
How to identify background rules of dataset dds type TTL functionality
Hi,
i have a requirement to identify the background rules of TTL (time to live ) dataset of type DDS(decision data source) to customize the background logic.
please suggest how to identify those rules? any jobschedular or agent rules pega implemented to work the TTL process in DDS.
Data set configuration in DF
Thanks in advance!!
Datase
Accepted Solution
Updated: 5 Jul 2024 7:53 EDT
Pegasystems Inc.
PL
Hi,
The way TTL feature of the DDS dataset works is a bit different than assumed here:
To achieve the records being removed after specified amount of time, we make use of the Cassandra database feature. In practice we specify the TTL value on the query when we insert the data into the database and the deletion process happens entirely in the database.
This means that we don’t have any logic in the likes of job schedulers on the Pega Platform side. Also, the creation of the query that is being executed is contained entirely in the DDS dataset code.
The above means that this behavior cannot be changed using rules. We can only specify different TTL values that are to be applied.
Of course, knowing the purpose of making theses changes we could get a feature out of this or propose an alternative solution.
Michał
Pegasystems Inc.
GB
@LukaszKarnasiewicz is this something which someone in your byour team could help with?
Accepted Solution
Updated: 5 Jul 2024 7:53 EDT
Pegasystems Inc.
PL
Hi,
The way TTL feature of the DDS dataset works is a bit different than assumed here:
To achieve the records being removed after specified amount of time, we make use of the Cassandra database feature. In practice we specify the TTL value on the query when we insert the data into the database and the deletion process happens entirely in the database.
This means that we don’t have any logic in the likes of job schedulers on the Pega Platform side. Also, the creation of the query that is being executed is contained entirely in the DDS dataset code.
The above means that this behavior cannot be changed using rules. We can only specify different TTL values that are to be applied.
Of course, knowing the purpose of making theses changes we could get a feature out of this or propose an alternative solution.
Michał