Reference documentation and code samples for the Data Catalog V1 API module Google::Cloud::DataCatalog::V1::EntryType.
Metadata automatically ingested from Google Cloud resources like BigQuery
tables or Pub/Sub topics always uses enum values from EntryType as the type
of entry.
Other sources of metadata like Hive or Oracle databases can identify the type
by either using one of the enum values from EntryType (for example,
FILESET for a Cloud Storage fileset) or specifying a custom value using
the Entry field user_specified_type. For more
information, see
Surface files from Cloud Storage with fileset
entries or Create custom entries for
your data sources.
Constants
ENTRY_TYPE_UNSPECIFIED
value: 0
Default unknown type.
TABLE
value: 2
The entry type that has a GoogleSQL schema, including
logical views.
MODEL
DATA_STREAM
value: 3
An entry type for streaming entries. For example, a Pub/Sub topic.
FILESET
value: 4
An entry type for a set of files or objects. For example, a
Cloud Storage fileset.
CLUSTER
value: 6
A group of servers that work together. For example, a Kafka cluster.
DATABASE
value: 7
A database.
DATA_SOURCE_CONNECTION
value: 8
Connection to a data source. For example, a BigQuery
connection.
ROUTINE
value: 9
Routine, for example, a BigQuery routine.
LAKE
value: 10
A Dataplex lake.
ZONE
value: 11
A Dataplex zone.
SERVICE
value: 14
A service, for example, a Dataproc Metastore service.
DATABASE_SCHEMA
value: 15
Schema within a relational database.
DASHBOARD
value: 16
A Dashboard, for example from Looker.