Empty error message when updating DLP Data Pattern
318
Created On 04/09/25 20:45 PM - Last Modified 10/21/25 22:14 PM
Symptom
- The data pattern to Data Lake tried to get TSGID on TenantMapping points to Null.
- The empty error message (NullPointException) failed the update of DLP data pattern.
Environment
- DLP
- DLP Inline
Cause
- API failed to update DLP data pattern and data profile because of the failure error caused by data lake provision.
- Failed to check the tenantMapping is empty for the giving tenant ID during the process of data lake provision
- Failed to catch any error or exception from data lake provision process which may block API to update the DLP data pattern and data profile
- Metis missed the regression tests on creating/updating/deleting data pattern and/or data profile for different DLP tenant IDs.
Resolution
- The empty error message happened when provisioning the updated data pattern to data lake.
- To provision this data pattern, it requires the TSG ID from the tenant's tenantMapping object. Usually every tenant has a tenantMapping object in DLP data base. However, the tenantConfigService's getTenantMapping method returns empty null. This empty returned object throws NullPointException when API tries to get TSG ID on it.
- As data lake provision requires several pre-conditions (tenant has tsgId, tenant is enabled in data lake, DLP data maps to data lake data, and so on), the data lake provision is allowed eventual consistency.
- To fix this issue, the tenantmapping look-up needs to look for dsstenantid if not found via tenantId. If tenantMapping is till empty, the process of data lake provision will log the empty tenantMapping and be skipped. It will not block the DLP user to update data pattern and store it into DLP database. The fix does retrieve tenantMapping via tenant ID and then via dlp Tenant ID if not found. The fix logs the empty tenantMapping and kips the data lake provision. Also, the fix catches all exception thrown by data lake provision process.