You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CatalogSchema._get_database_source_target_mapping assumes a unique mapping from a source schema to a target catalog and schema pair. This results in a collision when a user maps two tables from a single source schema to different target catalog schema pairs, for example:
Is there an existing issue for this?
Current Behavior
CatalogSchema._get_database_source_target_mapping
assumes a unique mapping from a source schema to a target catalog and schema pair. This results in a collision when a user maps two tables from a single source schema to different target catalog schema pairs, for example:Expected Behavior
The user should be able to map tables from the same source schema to different target schemas.
Steps To Reproduce
Extend the unit test with the example above in the current behavior.
Cloud
Azure
Operating System
macOS
Version
latest via Databricks CLI
Relevant log output
No response
The text was updated successfully, but these errors were encountered: