-
Notifications
You must be signed in to change notification settings - Fork 152
Open
Labels
Description
Following up the community post https://community.databricks.com/t5/data-engineering/how-to-specify-home-catalog-for-table-trigger-in-yaml/m-p/150146#M53271
When deploying a trigger on a table in the home catalog, that catalog name is required in job YAML trigger, as of 3 part table name:
trigger:
pause_status: UNPAUSED
table_update:
table_names:
- {HOME_CATALOG}.schema.table
When the workspace is dynamically created, and there is no predefined target for the host, that name cannot be acquired though system variables and has to be provided externally, such as via cli variable, environment variable etc.
This is also blocking deployment via UI:
Proposed solutions:
- Create a system variable for home catalog name (OR workspace name as a substitute, as they correlate).
- Allow 2 part name for table trigger, which will automatically map to the home catalog schema.table.
Reactions are currently unavailable