Entry Metadata.
A Data Catalog Entry resource represents another resource in Google
Cloud Platform (such as a BigQuery dataset or a Pub/Sub topic), or
outside of Google Cloud Platform. Clients can use the `linked_resource` field
in the Entry resource to refer to the original resource ID of the source
system.
An Entry resource contains resource details, such as its schema. An Entry can
also be used to attach flexible metadata, such as a
[Tag][google.cloud.datacatalog.v1beta1.Tag].
Protobuf type google.cloud.datacatalog.v1beta1.Entry
Specification for a group of BigQuery tables with name pattern
`[prefix]YYYYMMDD`. Context:
https://cloud.google.com/bigquery/docs/partitioned-tables#partitioning_versus_sharding.
Specification for a group of BigQuery tables with name pattern
`[prefix]YYYYMMDD`. Context:
https://cloud.google.com/bigquery/docs/partitioned-tables#partitioning_versus_sharding.
Display information such as title and description. A short name to identify
the entry, for example, "Analytics Data - Jan 2011". Default value is an
empty string.
Display information such as title and description. A short name to identify
the entry, for example, "Analytics Data - Jan 2011". Default value is an
empty string.
The enum numeric value on the wire for integratedSystem.
getLinkedResource()
publicStringgetLinkedResource()
The resource this metadata entry refers to.
For Google Cloud Platform resources, `linked_resource` is the [full name of
the
resource](https://cloud.google.com/apis/design/resource_names#full_resource_name).
For example, the `linked_resource` for a table resource from BigQuery is:
* //bigquery.googleapis.com/projects/projectId/datasets/datasetId/tables/tableId
Output only when Entry is of type in the EntryType enum. For entries with
user_specified_type, this field is optional and defaults to an empty
string.
The resource this metadata entry refers to.
For Google Cloud Platform resources, `linked_resource` is the [full name of
the
resource](https://cloud.google.com/apis/design/resource_names#full_resource_name).
For example, the `linked_resource` for a table resource from BigQuery is:
* //bigquery.googleapis.com/projects/projectId/datasets/datasetId/tables/tableId
Output only when Entry is of type in the EntryType enum. For entries with
user_specified_type, this field is optional and defaults to an empty
string.
The Data Catalog resource name of the entry in URL format. Example:
* projects/{project_id}/locations/{location}/entryGroups/{entry_group_id}/entries/{entry_id}
Note that this Entry and its child resources may not actually be stored in
the location in this name.
string name = 1 [(.google.api.resource_reference) = { ... }
The Data Catalog resource name of the entry in URL format. Example:
* projects/{project_id}/locations/{location}/entryGroups/{entry_group_id}/entries/{entry_id}
Note that this Entry and its child resources may not actually be stored in
the location in this name.
string name = 1 [(.google.api.resource_reference) = { ... }
Output only. Timestamps about the underlying resource, not about this Data Catalog
entry. Output only when Entry is of type in the EntryType enum. For entries
with user_specified_type, this field is optional and defaults to an empty
timestamp.
Output only. Timestamps about the underlying resource, not about this Data Catalog
entry. Output only when Entry is of type in the EntryType enum. For entries
with user_specified_type, this field is optional and defaults to an empty
timestamp.
This field indicates the entry's source system that Data Catalog does not
integrate with. `user_specified_system` strings must begin with a letter
or underscore and can only contain letters, numbers, and underscores; are
case insensitive; must be at least 1 character and at most 64 characters
long.
This field indicates the entry's source system that Data Catalog does not
integrate with. `user_specified_system` strings must begin with a letter
or underscore and can only contain letters, numbers, and underscores; are
case insensitive; must be at least 1 character and at most 64 characters
long.
Entry type if it does not fit any of the input-allowed values listed in
`EntryType` enum above. When creating an entry, users should check the
enum values first, if nothing matches the entry to be created, then
provide a custom value, for example "my_special_type".
`user_specified_type` strings must begin with a letter or underscore and
can only contain letters, numbers, and underscores; are case insensitive;
must be at least 1 character and at most 64 characters long.
Currently, only FILESET enum value is allowed. All other entries created
through Data Catalog must use `user_specified_type`.
Entry type if it does not fit any of the input-allowed values listed in
`EntryType` enum above. When creating an entry, users should check the
enum values first, if nothing matches the entry to be created, then
provide a custom value, for example "my_special_type".
`user_specified_type` strings must begin with a letter or underscore and
can only contain letters, numbers, and underscores; are case insensitive;
must be at least 1 character and at most 64 characters long.
Currently, only FILESET enum value is allowed. All other entries created
through Data Catalog must use `user_specified_type`.
Specification for a group of BigQuery tables with name pattern
`[prefix]YYYYMMDD`. Context:
https://cloud.google.com/bigquery/docs/partitioned-tables#partitioning_versus_sharding.
Output only. Timestamps about the underlying resource, not about this Data Catalog
entry. Output only when Entry is of type in the EntryType enum. For entries
with user_specified_type, this field is optional and defaults to an empty
timestamp.
This field indicates the entry's source system that Data Catalog does not
integrate with. `user_specified_system` strings must begin with a letter
or underscore and can only contain letters, numbers, and underscores; are
case insensitive; must be at least 1 character and at most 64 characters
long.
Entry type if it does not fit any of the input-allowed values listed in
`EntryType` enum above. When creating an entry, users should check the
enum values first, if nothing matches the entry to be created, then
provide a custom value, for example "my_special_type".
`user_specified_type` strings must begin with a letter or underscore and
can only contain letters, numbers, and underscores; are case insensitive;
must be at least 1 character and at most 64 characters long.
Currently, only FILESET enum value is allowed. All other entries created
through Data Catalog must use `user_specified_type`.
[[["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-03-22 UTC."],[],[]]
