-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Open
Labels
component:catalog-syncCatalog-sync relatedCatalog-sync relatedfrom-jirapriority:highSignificant impact; potential bugsSignificant impact; potential bugsstatus:pr-availablePull request availablePull request availabletype:devtaskDevelopment tasks and maintenance workDevelopment tasks and maintenance work
Description
Datahub has a notion of soft-deletes (the entity still exists in the database with a status=removed:true). Such entities could get re-ingested with new properties at a later time, such that the older one gets overwritten. The current implementation in DatahubSyncTool does not handle this scenario. It fails to update the status flag to removed:false during ingest, which means the entity won't surface in the Datahub UI at all.
Ref: See sections on Soft Delete and Hard Delete in the Datahub docs: [https://datahubproject.io/docs/how/delete-metadata/#soft-delete-the-default]
JIRA info
- Link: https://issues.apache.org/jira/browse/HUDI-4994
- Type: Task
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
component:catalog-syncCatalog-sync relatedCatalog-sync relatedfrom-jirapriority:highSignificant impact; potential bugsSignificant impact; potential bugsstatus:pr-availablePull request availablePull request availabletype:devtaskDevelopment tasks and maintenance workDevelopment tasks and maintenance work