@Generated public interface MetastoresService
Each metastore is configured with a root storage location in a cloud storage account. This storage location is used for metadata and managed tables data.
NOTE: This metastore is distinct from the metastore included in Databricks workspaces created before Unity Catalog was released. If your workspace includes a legacy Hive metastore, the data in that metastore is available in a catalog named hive_metastore.
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 |
|---|---|
void |
assign(CreateMetastoreAssignment createMetastoreAssignment)
Creates a new metastore assignment.
|
MetastoreInfo |
create(CreateMetastore createMetastore)
Creates a new metastore based on a provided name and optional storage root path.
|
MetastoreAssignment |
current()
Gets the metastore assignment for the workspace being accessed.
|
void |
delete(DeleteMetastoreRequest deleteMetastoreRequest)
Deletes a metastore.
|
MetastoreInfo |
get(GetMetastoreRequest getMetastoreRequest)
Gets a metastore that matches the supplied ID.
|
ListMetastoresResponse |
list(ListMetastoresRequest listMetastoresRequest)
Gets an array of the available metastores (as __MetastoreInfo__ objects).
|
GetMetastoreSummaryResponse |
summary()
Gets information about a metastore.
|
void |
unassign(UnassignRequest unassignRequest)
Deletes a metastore assignment.
|
MetastoreInfo |
update(UpdateMetastore updateMetastore)
Updates information for a specific metastore.
|
void |
updateAssignment(UpdateMetastoreAssignment updateMetastoreAssignment)
Updates a metastore assignment.
|
void assign(CreateMetastoreAssignment createMetastoreAssignment)
MetastoreInfo create(CreateMetastore createMetastore)
MetastoreAssignment current()
void delete(DeleteMetastoreRequest deleteMetastoreRequest)
MetastoreInfo get(GetMetastoreRequest getMetastoreRequest)
ListMetastoresResponse list(ListMetastoresRequest listMetastoresRequest)
NOTE: we recommend using max_results=0 to use the paginated version of this API. Unpaginated calls will be deprecated soon.
PAGINATION BEHAVIOR: When using pagination (max_results >= 0), a page may contain zero results while still providing a next_page_token. Clients must continue reading pages until next_page_token is absent, which is the only indication that the end of results has been reached.
GetMetastoreSummaryResponse summary()
void unassign(UnassignRequest unassignRequest)
MetastoreInfo update(UpdateMetastore updateMetastore)
void updateAssignment(UpdateMetastoreAssignment updateMetastoreAssignment)
Copyright © 2026. All rights reserved.