| subcategory |
|---|
Unity Catalog |
-> Public Preview This feature is in Public Preview. Contact your Databricks representative to request access.
Within a metastore, Unity Catalog provides a 3-level namespace for organizing data: Catalogs, Databases (also called Schemas), and Tables / Views.
A databricks_catalog is contained within databricks_metastore and can contain databricks_schema. By default, Databricks creates default schema for every new catalog, but Terraform plugin is removing this auto-created schema, so that resource destruction could be done in a clean way.
resource "databricks_catalog" "sandbox" {
metastore_id = databricks_metastore.this.id
name = "sandbox"
comment = "this catalog is managed by terraform"
properties = {
purpose = "testing"
}
}The following arguments are required:
name- Name of Catalog relative to parent metastore. Change forces creation of a new resource.owner- (Optional) Username/groupname of catalog owner. Currently this field can only be changed after the resource is created.comment- (Optional) User-supplied free-form text.properties- (Optional) Extensible Catalog properties.
This resource can be imported by name:
$ terraform import databricks_catalog.this <name>The following resources are used in the same context:
- databricks_table data to list tables within Unity Catalog.
- databricks_schema data to list schemas within Unity Catalog.
- databricks_catalog data to list catalogs within Unity Catalog.