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
Exporter: don't emit all UC objects when handling dependencies (#3556)
Right now, if we discover any UC dependency, we emit upstream objects as well, such as
schemas, catalogs, etc., but in their `Import` operations we're doing all nested objects
unnecessarily - so emit one init script from a UC Volume may lead to emitting of the whole
UC Catalog with all schemas/tables/volumes...
With this change, we list all nested objects (schemas in catalog, tables/models/volumes in
a schema) only if these services are explicitly specified in the `-listing` option.
Fixes#3555
*`uc-grants` - [databricks_grants](../resources/grants.md). *Please note that during export the list of grants is expanded to include the identity that does the export! This is done to allow to create objects in case when catalogs/schemas have different owners than current identity.*.
89
89
*`uc-metastores` - **listing**[databricks_metastore](../resources/metastore.md) and [databricks_metastore_assignment](../resource/metastore_assignment.md) (only on account-level). *Please note that when using workspace-level configuration, only metastores from the workspace's region are listed!*
*`uc-models` - **listing** (*we can't list directly, only via dependencies to top-level object*) [databricks_registered_model](../resources/registered_model.md)
91
+
*`uc-schemas` - **listing** (*we can't list directly, only via dependencies to top-level object*)[databricks_schema](../resources/schema.md)
92
92
*`uc-shares` - **listing**[databricks_share](../resources/share.md) and [databricks_recipient](../resources/recipient.md)
93
93
*`uc-storage-credentials` - **listing** exports [databricks_storage_credential](../resources/storage_credential.md) resources on workspace or account level.
94
94
*`uc-system-schemas` - **listing** exports [databricks_system_schema](../resources/system_schema.md) resources for the UC metastore of the current workspace.
*`uc-tables` - **listing** (*we can't list directly, only via dependencies to top-level object*) [databricks_sql_table](../resources/sql_table.md) resource.
96
+
*`uc-volumes` - **listing** (*we can't list directly, only via dependencies to top-level object*)[databricks_volume](../resources/volume.md)
97
97
*`users` - [databricks_user](../resources/user.md) and [databricks_service_principal](../resources/service_principal.md) are written to their own file, simply because of their amount. If you use SCIM provisioning, migrating workspaces is the only use case for importing `users` service.
98
98
*`workspace` - **listing**[databricks_workspace_conf](../resources/workspace_conf.md) and [databricks_global_init_script](../resources/global_init_script.md)
0 commit comments