Unified_Changes_Clusters Table¶
The Unified_Changes_Clusters table contains a history of changes to cluster graphs, relative to the previous Stitch run.
The Unified_Changes_Clusters table is automatically added to the Stitch QA database as a passthrough table when it is generated using the “Stitch QA” database template.
Note
Thirty days of history are stored by defaut for the Unified_Changes_Clusters and Unified_Changes_PKS tables. This number of days is configurable.
Use with Stitch QA¶
Use the Unified_Changes_Clusters table as part of the Stitch QA process to compare the previous state of clusters to the current state and understand why a primary key was added, deleted, or updated.
Column reference¶
The Unified_Changes_Clusters table contains the following columns:
Column Name |
Data type |
Description |
---|---|---|
amperity_id |
String |
The unique identifier that is assigned to clusters of customer records that all represent the same individual. The Amperity ID does not replace primary and foreign keys, but exists alongside them within unified profiles. Note The Amperity ID is a universally unique identifier (UUID) that is represented by 36 characters spread across five groups separated by hyphens: 8-4-4-4-12. For example: 123e4567-e89b-12d3-a456-426614174000
|
change_type |
String |
The type of change that occurred within the Stitch job. Possible values include:
Also in: Unified_Changes_PKS |
job_id |
String |
The job ID for database table generation. For example: Also in: Unified_Changes_PKS |
timestamp |
Datetime |
The timestamp that is associated with Also in: Unified_Changes_PKS |