Reference documentation and code samples for the Google Cloud Data Catalog V1 Client class 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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-09 UTC."],[],[],null,["# Google Cloud Data Catalog V1 Client - Class EntryType (2.3.2)\n\nVersion latestkeyboard_arrow_down\n\n- [2.3.2 (latest)](/php/docs/reference/cloud-data-catalog/latest/V1.EntryType)\n- [2.3.1](/php/docs/reference/cloud-data-catalog/2.3.1/V1.EntryType)\n- [2.2.4](/php/docs/reference/cloud-data-catalog/2.2.4/V1.EntryType)\n- [2.1.0](/php/docs/reference/cloud-data-catalog/2.1.0/V1.EntryType)\n- [2.0.2](/php/docs/reference/cloud-data-catalog/2.0.2/V1.EntryType)\n- [1.10.3](/php/docs/reference/cloud-data-catalog/1.10.3/V1.EntryType)\n- [1.9.1](/php/docs/reference/cloud-data-catalog/1.9.1/V1.EntryType)\n- [1.8.2](/php/docs/reference/cloud-data-catalog/1.8.2/V1.EntryType)\n- [1.7.1](/php/docs/reference/cloud-data-catalog/1.7.1/V1.EntryType)\n- [1.6.0](/php/docs/reference/cloud-data-catalog/1.6.0/V1.EntryType)\n- [1.5.1](/php/docs/reference/cloud-data-catalog/1.5.1/V1.EntryType)\n- [1.4.2](/php/docs/reference/cloud-data-catalog/1.4.2/V1.EntryType)\n- [1.3.9](/php/docs/reference/cloud-data-catalog/1.3.9/V1.EntryType) \nReference documentation and code samples for the Google Cloud Data Catalog V1 Client class EntryType.\n\nMetadata automatically ingested from Google Cloud resources like BigQuery\ntables or Pub/Sub topics always uses enum values from `EntryType` as the type\nof entry.\n\nOther sources of metadata like Hive or Oracle databases can identify the type\nby either using one of the enum values from `EntryType` (for example,\n`FILESET` for a Cloud Storage fileset) or specifying a custom value using\nthe [`Entry`](#resource:-entry) field `user_specified_type`. For more\ninformation, see\n[Surface files from Cloud Storage with fileset\nentries](/data-catalog/docs/how-to/filesets) or [Create custom entries for\nyour data sources](/data-catalog/docs/how-to/custom-entries).\n\nProtobuf type `google.cloud.datacatalog.v1.EntryType`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ DataCatalog \\\\ V1\n\nMethods\n-------\n\n### static::name\n\n### static::value\n\nConstants\n---------\n\n### ENTRY_TYPE_UNSPECIFIED\n\n Value: 0\n\nDefault unknown type.\n\nGenerated from protobuf enum `ENTRY_TYPE_UNSPECIFIED = 0;`\n\n### TABLE\n\n Value: 2\n\nThe entry type that has a GoogleSQL schema, including\nlogical views.\n\nGenerated from protobuf enum `TABLE = 2;`\n\n### MODEL\n\n Value: 5\n\nThe type of models.\n\nFor more information, see [Supported models in BigQuery\nML](/bigquery/docs/bqml-introduction#supported_models).\n\nGenerated from protobuf enum `MODEL = 5;`\n\n### DATA_STREAM\n\n Value: 3\n\nAn entry type for streaming entries. For example, a Pub/Sub topic.\n\nGenerated from protobuf enum `DATA_STREAM = 3;`\n\n### FILESET\n\n Value: 4\n\nAn entry type for a set of files or objects. For example, a\nCloud Storage fileset.\n\nGenerated from protobuf enum `FILESET = 4;`\n\n### CLUSTER\n\n Value: 6\n\nA group of servers that work together. For example, a Kafka cluster.\n\nGenerated from protobuf enum `CLUSTER = 6;`\n\n### DATABASE\n\n Value: 7\n\nA database.\n\nGenerated from protobuf enum `DATABASE = 7;`\n\n### DATA_SOURCE_CONNECTION\n\n Value: 8\n\nConnection to a data source. For example, a BigQuery\nconnection.\n\nGenerated from protobuf enum `DATA_SOURCE_CONNECTION = 8;`\n\n### ROUTINE\n\n Value: 9\n\nRoutine, for example, a BigQuery routine.\n\nGenerated from protobuf enum `ROUTINE = 9;`\n\n### LAKE\n\n Value: 10\n\nA Dataplex lake.\n\nGenerated from protobuf enum `LAKE = 10;`\n\n### ZONE\n\n Value: 11\n\nA Dataplex zone.\n\nGenerated from protobuf enum `ZONE = 11;`\n\n### SERVICE\n\n Value: 14\n\nA service, for example, a Dataproc Metastore service.\n\nGenerated from protobuf enum `SERVICE = 14;`\n\n### DATABASE_SCHEMA\n\n Value: 15\n\nSchema within a relational database.\n\nGenerated from protobuf enum `DATABASE_SCHEMA = 15;`\n\n### DASHBOARD\n\n Value: 16\n\nA Dashboard, for example from Looker.\n\nGenerated from protobuf enum `DASHBOARD = 16;`\n\n### EXPLORE\n\n Value: 17\n\nA Looker Explore.\n\nFor more information, see [Looker Explore API](https://developers.looker.com/api/explorer/4.0/methods/LookmlModel/lookml_model_explore).\n\nGenerated from protobuf enum `EXPLORE = 17;`\n\n### LOOK\n\n Value: 18\n\nA Looker Look.\n\nFor more information, see [Looker Look API](https://developers.looker.com/api/explorer/4.0/methods/Look).\n\nGenerated from protobuf enum `LOOK = 18;`\n\n### FEATURE_ONLINE_STORE\n\n Value: 19\n\nFeature Online Store resource in Vertex AI Feature Store.\n\nGenerated from protobuf enum `FEATURE_ONLINE_STORE = 19;`\n\n### FEATURE_VIEW\n\n Value: 20\n\nFeature View resource in Vertex AI Feature Store.\n\nGenerated from protobuf enum `FEATURE_VIEW = 20;`\n\n### FEATURE_GROUP\n\n Value: 21\n\nFeature Group resource in Vertex AI Feature Store.\n\nGenerated from protobuf enum `FEATURE_GROUP = 21;`"]]
