com.databricks.sdk.service.settings.SettingsService Maven / Gradle / Ivy
// Code generated from OpenAPI specs by Databricks SDK Generator. DO NOT EDIT.
package com.databricks.sdk.service.settings;
import com.databricks.sdk.support.Generated;
/**
* The default namespace setting API allows users to configure the default namespace for a
* Databricks workspace.
*
* 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.
*/
@Generated
public interface SettingsService {
/**
* Delete the default namespace setting.
*
*
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 will fail
* with 409 and the request will need to be retried by using the fresh etag in the 409 response.
*/
DeleteDefaultWorkspaceNamespaceResponse deleteDefaultWorkspaceNamespace(
DeleteDefaultWorkspaceNamespaceRequest deleteDefaultWorkspaceNamespaceRequest);
/**
* Get the default namespace setting.
*
*
Gets the default namespace setting.
*/
DefaultNamespaceSetting readDefaultWorkspaceNamespace(
ReadDefaultWorkspaceNamespaceRequest readDefaultWorkspaceNamespaceRequest);
/**
* Update the default namespace setting.
*
*
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 will return a
* NOT_FOUND error and the etag will be present in the error response, which should be set in the
* PATCH request. If the setting is updated concurrently, PATCH will fail with 409 and the request
* will need to be retried by using the fresh etag in the 409 response.
*/
DefaultNamespaceSetting updateDefaultWorkspaceNamespace(
UpdateDefaultWorkspaceNamespaceRequest updateDefaultWorkspaceNamespaceRequest);
}