@Generated public interface DefaultNamespaceService
Through this API, users can retrieve, set, or modify the default namespace used when queries do not reference a fully qualified three-level name. For example, if you use the API to set 'retail_prod' as the default catalog, then a query 'SELECT * FROM myTable' would reference the object 'retail_prod.default.myTable' (the schema 'default' is always assumed).
This setting requires a restart of clusters and SQL warehouses to take effect. Additionally, the default namespace only applies when using Unity Catalog-enabled compute.
This is the high-level interface, that contains generated methods.
Evolving: this interface is under development. Method signatures may change.
Modifier and Type | Method and Description |
---|---|
DeleteDefaultNamespaceSettingResponse |
delete(DeleteDefaultNamespaceSettingRequest deleteDefaultNamespaceSettingRequest)
Delete the default namespace setting.
|
DefaultNamespaceSetting |
get(GetDefaultNamespaceSettingRequest getDefaultNamespaceSettingRequest)
Get the default namespace setting.
|
DefaultNamespaceSetting |
update(UpdateDefaultNamespaceSettingRequest updateDefaultNamespaceSettingRequest)
Update the default namespace setting.
|
DeleteDefaultNamespaceSettingResponse delete(DeleteDefaultNamespaceSettingRequest deleteDefaultNamespaceSettingRequest)
Deletes the default namespace setting for the workspace. A fresh etag needs to be provided in `DELETE` requests (as a query parameter). The etag can be retrieved by making a `GET` request before the `DELETE` request. If the setting is updated/deleted concurrently, `DELETE` fails with 409 and the request must be retried by using the fresh etag in the 409 response.
DefaultNamespaceSetting get(GetDefaultNamespaceSettingRequest getDefaultNamespaceSettingRequest)
Gets the default namespace setting.
DefaultNamespaceSetting update(UpdateDefaultNamespaceSettingRequest updateDefaultNamespaceSettingRequest)
Updates the default namespace setting for the workspace. A fresh etag needs to be provided in `PATCH` requests (as part of the setting field). The etag can be retrieved by making a `GET` request before the `PATCH` request. Note that if the setting does not exist, `GET` returns a NOT_FOUND error and the etag is present in the error response, which should be set in the `PATCH` request. If the setting is updated concurrently, `PATCH` fails with 409 and the request must be retried by using the fresh etag in the 409 response.
Copyright © 2024. All rights reserved.