The list of private reverse connection endpoints attached to the catalog
Compartment identifier.
Usage of predefined tag keys. These predefined keys are scoped to namespaces. Example: {@code {"foo-namespace": {"bar-key": "value"}}}
Data catalog identifier, that can be renamed.
Simple key-value pair that is applied without any predefined name, type, or scope. Exists for cross-compatibility only. Example: {@code {"bar-key": "value"}}
Unique identifier that is immutable on creation.
An 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 data catalog resource.
Locks associated with this resource.
The number of high level objects added to the data catalog. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
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\"}}}
The time the data catalog was created. An RFC3339 formatted datetime string.
The time the data catalog was updated. An RFC3339 formatted datetime string.
Summary of the data catalog.