OCID of the compartment which holds the metastore.
Location under which external tables will be created by default. This references Object Storage using an HDFS URI format. Example: oci://bucket@namespace/sub-dir/
Location under which managed tables will be created by default. This references Object Storage using an HDFS URI format. Example: oci://bucket@namespace/sub-dir/
Usage of predefined tag keys. These predefined keys are scoped to namespaces. Example: {@code {"foo-namespace": {"bar-key": "value"}}}
Mutable name of the metastore.
Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. Example: {@code {"bar-key": "value"}}
The metastore's OCID.
A message describing the current state in more detail. For example, can be used to provide actionable information for a resource in Failed state.
The current state of the metastore.
Locks associated with this resource.
System tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. System tags can be viewed by users, but can only be created by the system.
Example: {@code {\"orcl-cloud\": {\"free-tier-retained\": \"true\"}}}
Time at which the metastore was created. An RFC3339 formatted datetime string.
Time at which the metastore was last modified. An RFC3339 formatted datetime string.
A Data Catalog Metastore provides a centralized metastore repository for use by other OCI services.