Ensure that for each source table and target schema (preferably per database), there is at most one Lakehouse shortcut. This prevents duplication of shortcuts pointing to the same source, simplifies data governance, and reduces confusion in downstream processes.
Problem Statement:
Currently, multiple shortcuts can be created for the same source table within the same schema, leading to redundancy and potential inconsistencies in data access and lineage tracking.
Proposed Solution:
Implement a validation mechanism or enforcement rule that checks for existing shortcuts before creating a new one. If a shortcut already exists for the given source table and target schema (or database), the system should either:
- Block the creation of a duplicate shortcut, or
- Prompt the user to reuse the existing shortcut.
Benefits:
- Improves data consistency and governance.
- Reduces storage and maintenance overhead.
- Enhances clarity for developers and analysts working with Lakehouse shortcuts.
dm-p
on:
Allow standard Focus Mode for custom visuals that ...
on:
Data Pipelines - Run only selected activities
on:
More granular control and better design experience...
on:
Consistent TMDL serialisation across developer mac...