Materialized IH Summaries - how do they work
Hi
Could you point me in the right direction and help to understand how these IH Summaries work please?
Specifically I need to understand how the Meterialized data sets are updated.
From what I understand, materialized data sets are precalculated and stored in Cassandra DDS?
But when new customer interaction occurs, how this materialized data set is updated then? Do we need to update it declaratively? Or is it updated automatically? How does it work?
Could you advise please?
Thanks
Andy
Accepted Solution
Pegasystems Inc.
US
Materialized IH Summaries are automatically managed for you. On initial materialization (bootstrap stage), the system scans IH to establish the starting point for the aggregation and stores the result in Cassandra. As subsequent IH entries are captured, the data is automatically sent to the aggregation data set to keep the aggregation current and automatically managed.
Softtech
TR
Hi,
Thank you for the information. I want ask a few question for Cassandra process. Can you help me, please?
I have a Materialized IH Summary and how can i learn the my Materialized IH Summary's table name on Cassandra? And; what is this records' default TTL value on Cassandra?
Thanks
Pegasystems Inc.
US
Can I ask why you would like to know the name of the table? This is not meant to be exposed as a table, but as a service within your decisioning canvas. It is a managed object that should not be messed with and its structure can change as the software evolves.
Same for TTL, the lifecyle of summarized data is managed for you based on the definition of the IH Summary.
Softtech
TR
Hi,
Sure, I asked the question, because; I want to learn how the process works all of details. We use external Cassandra.One of time; cassandra team shared of the tables on Cassandra db with us and we noticed that we don't know the name of most tables, why they were created and the content..
We had a problem with Cassandra data size recently. We had to change TTL (from 30 days to 14 days) for inbound and outbound interactions' records. This is one of the main reasons for both my questions. As far as I know; we don't update in Cassandra. We are throwing a new record for each new information that occurs. There will also be updates for the information we use in IH Summary; and this means new records for each customer. If we know the name of the table, we can see the size of the table with CSQL and intervene when necessary. How can I learn this information?
Thanks
Pegasystems Inc.
US
The Summary tables do not have the same footprint as the other tables you are referring to. They are bounded by the size of your customer count, so do not have any TTLs that you need to worry about.