PRDE - Story default text according to the team DoR (Definition of Ready)

01 - PERSON OF CONTACT (PERSON THAT CAN ANSWER QUESTIONS ABOUT THE PROBLEM):
02 - PROBLEM (WHAT'S THE CURRENT PROBLEM SCENARIO OR PAIN TO BE RESOLVED?):

We are not investing on our old consolidation flow. The old consolidation flow is the one that uses Batch Dataflow process to rebuild the parquet files.

03 - GOAL (DESCRIBE THE PROPOSED SOLUTION):

To avoid using the consolidation flow, we can redefine the mdmID when importing the data from parquet to bigquery (the dataload flow) and calculate the mdmID again for the imported data.

We should keep all other data as they are, including the counter.

Adjusted Flow: [https://app.diagrams.net/#G1x8g20kW0rUK8PpDyE16xAimsaFVGE2aX#

|https://app.diagrams.net/#G1x8g20kW0rUK8PpDyE16xAimsaFVGE2aX#%7B%22pageId%22%3A%22A6-Zbxc90aw5eNSou2SU%22%7D]

Tab: PX-07

04 - WHO CAN USE THIS FEATURE (USER ROLES): tenantAdmin, OrgAdmin
06 - ACCEPTANCE CRITERIA:

• Provision flow covering the regeneration of mdmID for customer tenants (not Unified tenant).
  • Not unified tenant does not have CDS data, so we can’t provision it again.
• The process that copy data from D-1 to Carol, after a schema change that required a table recreation should also generate again the mdmID for the reimported data.

Update:
The mdmId regeneration need to be done only for staging tables.