EntryType(value)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 <#resource:-entry>__ fielduser_specified_type. For more information, seeSurface files
from Cloud Storage with fileset
entries </data-catalog/docs/how-to/filesets>__ orCreate custom
entries for your data
sources </data-catalog/docs/how-to/custom-entries>`__.
Values: ENTRY_TYPE_UNSPECIFIED (0): Default unknown type. TABLE (2): The entry type that has a GoogleSQL schema, including logical views. MODEL (5): The type of models.
For more information, see `Supported models in BigQuery
ML </bigquery/docs/bqml-introduction#supported_models>`__.
DATA_STREAM (3):
An entry type for streaming entries. For
example, a Pub/Sub topic.
FILESET (4):
An entry type for a set of files or objects.
For example, a Cloud Storage fileset.
CLUSTER (6):
A group of servers that work together. For
example, a Kafka cluster.
DATABASE (7):
A database.
DATA_SOURCE_CONNECTION (8):
Connection to a data source. For example, a
BigQuery connection.
ROUTINE (9):
Routine, for example, a BigQuery routine.
LAKE (10):
A Dataplex lake.
ZONE (11):
A Dataplex zone.
SERVICE (14):
A service, for example, a Dataproc Metastore
service.
DATABASE_SCHEMA (15):
Schema within a relational database.
DASHBOARD (16):
A Dashboard, for example from Looker.
EXPLORE (17):
A Looker Explore.
For more information, see [Looker Explore API]
(https://developers.looker.com/api/explorer/4.0/methods/LookmlModel/lookml_model_explore).
LOOK (18):
A Looker Look.
For more information, see [Looker Look API]
(https://developers.looker.com/api/explorer/4.0/methods/Look).