Carol should not create reprocess merge for SQL Only tenants
Description
Issue Component(s) on Oct 31, 2023, 1:48:29 AM: DATA_MODEL | MAINTENANCE
Issue Component(s) on Oct 31, 2023, 1:48:19 AM: SQL_PIPELINES | DATA_PROCESSING
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?):
Today Carol is creating the reprocess merge tasks when the tenant or ORG is SQL Only or when the data model does not have a mapping and cleansing rule associated.
Since the mapping and cleansing rule will be terminated on 12/31/2023, we should focus on not creating the reprocess merge tasks when the tenant or ORG is SQL Only.
Slack thread: https://totvslabs.slack.com/archives/C0330CSV2/p1698420876754829?thread_ts=1698249550.482279&cid=C0330CSV2
06 - ACCEPTANCE CRITERIA:
- When the tenant or ORG is SQL Only, Carol should not create the task reprocess merge records when the Data Model changes the merge rules.
Activity
Details
Priority
Highest
This issue was automatically transitioned to DONE after being deployed to production on Github.
https://github.com/totvslabs/mdm/releases/tag/v4.88.0
No associated issue on JIRA TOTVS BRAZIL.
This issue was automatically transitioned to WAITING DEPLOY, as its linked QA regression issue has just reached WAITING DEPLOY status (PR was just merged into master branch in Github).
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to TESTED & MERGED, as its PR was just merged into develop branch in Github. PR Approved by rfschroeder,douglascoimbra.
@Robson Thanael Poffo ,
@Geny Isam Hamud Herrera , @Douglas Coimbra Lopes , @Renan Schroeder
This issue was planned to be delivered until 2023-12-11. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2023-11-20, 2023-12-11
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
Github user douglascoimbra has just approved a PR (added as Shard Assignee in this Jira issue).
fix: https://totvslabs.atlassian.net/browse/CAPL-4961#icft=CAPL-4961 - Do not execute merges on DataModel when tenant is SQL Processing Only
SQL process only False: Mapping reprocessing records with merge:
EXACT MERGE CREATED
Syncing data with the staging table
Old Mapping processing for new users
SQL ONly False SQL processing ONly User register
MERGE GENERATED FOR BOTH CASES
SQL ONly Tenant Running SQL processing Running
Merge not created
USER Creation through SQL processing:
Merge is still being created
This issue was automatically transitioned to QA REVIEW, as its PR was just approved in Github.
This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.
fix: https://totvslabs.atlassian.net/browse/CAPL-4961#icft=CAPL-4961 - Do not execute merges on DataModel when tenant is SQL Processing Only
@Robson Thanael Poffo ,
@Geny Isam Hamud Herrera ,
This issue was planned to be delivered until 2023-11-20. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2023-11-20
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.