Why has MS Fabric team chosen to use the term 'mirroring' for the new 'Mirrored Azure Databricks Catalog' item? This is going to create utter confusion between mirroring vs. shortcuts in MS Fabric terminology. The delta tables in Azure Databricks are not actually getting mirrored/replicated, these are only (and correctly) getting accessible as shortcuts. This is similar to how other shortcuts work in MS Fabric.
I can understand the use of the term 'mirroring' here possibly because the Unity Catalog metadata is getting mirrored, but still, it breaks the norm because the actual data (delta tables) is just shortcut. Can a better name for this item be 'Azure Databricks Shortcut with Mirrored Catalog'?
1 Comment
- Status added:New
