As tenant admin I am not able to filter deleted record IDs on Data Subscription

Description

PRDE - Bug 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 ISSUE?):

I am not able to filter recordIds that the subscription sent to delete. The filter `record Id` sends the where for only one field: recordIds

03 - STEPS TO REPRODUCE (STEP (1...N), VIDEO, SCREENSHOTS, LOGS FOLDER, HEARTBEAT, ETC. – IF IS NOT POSSIBLE TO REPRODUCE EXPLAIN THE REASON):

  • Configure a subscription
  • Build a pipeline to reject records
  • Go to subscription UI and try to filter the record by recordId

Since the record was deleted, we can’t find it by the recordId filter.

Sample of query I used to validate this scenario:

select *
from `carol-8cd6e43115e9416eb236.8cd6e43115e9416eb23609486fa053e3.ingestion_stg_internal_system_log`
where 
mdmCounterForEntity__DATETIME__ between '2024-02-02T14:00:00' and '2024-02-02T15:00:00'
and tenantId = '5063472056c14860b7b4b8de90a58065'
and (recordIds like '%7c9c136b6dd2d7f46932ce124062c737%'
or deletedRecordIds like '%7c9c136b6dd2d7f46932ce124062c737%')
limit 10

The above query filters only records with the ID on deletedRecordIds column. The UI isn’t getting these records by this filter when filtering recordIDs.

05 - EXPECTED BEHAVIOR (LIST THE EXPECTED BEHAVIORS TO CONSIDER THIS BUG AS DONE):

  • As tenant admin I should be able to filter recordId for both: golden record and rejected record.
    • Rejected record are called as deletedRecordIds internally.

Activity

Douglas Coimbra Lopes 20 February 2024, 10:59 Jira Internal Users

@Ingo Wagner @Jonathan Willian Moraes It will be tested in production

Robson Thanael Poffo 20 February 2024, 03:08 Jira Internal Users

Validei em produção e está filtrando conforme esperado logs de subscription pelo mdmID de registros rejeitados/deletados na pipeline SQL:

Automation for Jira 12 February 2024, 19:31 Jira Internal Users

@MARCOS STUMPF ,
@Gabriel DAmore Marciano ,
@Geny Isam Hamud Herrera ,
This issue was planned to be delivered until 2024-03-04. You can check that by consulting the issue in the Due Date field.

Dates already planned for this issue: 2024-03-04

If External Issue Link field is filled, customer was also informed on JIRA TOTVS.