|
SG-8109 Data Lake Upload Setup | Tables - view table DLV not removed with DLAUTOVW set to YES |
|
|
Description |
|
|
There is a recurring issue in Data Lake Upload when install param DLAUTOVW=YES which potentially leads to having duplicates of the same view table *DLV_*_ in column TABLENAME from DATALAKE_TABLE. This is not allowed by the system for the rest of tables, but can happen with the view table for the lastsaved nulls. Customers are warned to double-check and remove the specific *DLV_*_ from any previous schedule, even if inactive (schedule or table), however it would be better if, when manually removing the associated main table, the system removed the view table too. Or that the system restricted having duplicates in TABLENAME from DATALAKE_TABLE. This is because having the same *DLV_*_ table in multiple schedules or even duplicated in the same schedule leads to a FAIL sync and (example) Error Message: _There is an error getting Tenant data for table R5DLVORGANIZATION 2023-09-14 13:21:00A valid connection does not exist to get the Timestamp Field for the table_ *Steps to reproduce:* #Choose a table (allowed for and not yet on Datalake upload) and verify there are nulls on XXX_LASTSAVED, for example R5ORGANIZATION. #Set DLAUTOVW=YES. #Create a Datalake Schedule, and on Tables tab add R5ORGANIZATION. System adds R5DLVORGANIZATION. #Remove table R5ORGANIZATION from the schedule. *Expected results:* (actually no use case mentions this) R5DLVORGANIZATION is automatically removed
*Actual results:* R5DLVORGANIZATION remains in the schedule #Add R5ORGANIZATION back. *Expected results:* (actually no use case mentions this) system prevents having duplicates for R5DLVORGANIZATION
*Actual results:* now there are 2 entries for R5DLVORGANIZATION #Activate the 3 tables and the schedule with frequency of 5 minutes. Complete the setup on ION Desk and wait for initial sync. #Check Data Lake Setup | Tables for R5DLVORGANIZATION - Error Message: _There is an error getting Tenant data for table R5DLVORGANIZATION 2023-09-14 13:21:00A valid connection does not exist to get the Timestamp Field for the table |
|