Reference documentation and code samples for the Google Cloud Data Catalog V1 Client class LookupEntryRequest.
Request message for LookupEntry.
Generated from protobuf message google.cloud.datacatalog.v1.LookupEntryRequest
Methods
__construct
Constructor.
Parameters | |
---|---|
Name | Description |
data |
array
Optional. Data for populating the Message object. |
↳ linked_resource |
string
The full name of the Google Cloud Platform resource the Data Catalog entry represents. For more information, see Full Resource Name. Full names are case-sensitive. For example: * |
↳ sql_resource |
string
The SQL name of the entry. SQL names are case-sensitive. Examples: * |
↳ fully_qualified_name |
string
Fully qualified name (FQN) of the resource. FQNs take two forms: * For non-regionalized resources: |
getLinkedResource
The full name of the Google Cloud Platform resource the Data Catalog entry represents. For more information, see Full Resource Name.
Full names are case-sensitive. For example:
//bigquery.googleapis.com/projects/{PROJECT_ID}/datasets/{DATASET_ID}/tables/{TABLE_ID}
//pubsub.googleapis.com/projects/{PROJECT_ID}/topics/{TOPIC_ID}
Returns | |
---|---|
Type | Description |
string |
hasLinkedResource
setLinkedResource
The full name of the Google Cloud Platform resource the Data Catalog entry represents. For more information, see Full Resource Name.
Full names are case-sensitive. For example:
//bigquery.googleapis.com/projects/{PROJECT_ID}/datasets/{DATASET_ID}/tables/{TABLE_ID}
//pubsub.googleapis.com/projects/{PROJECT_ID}/topics/{TOPIC_ID}
Parameter | |
---|---|
Name | Description |
var |
string
|
Returns | |
---|---|
Type | Description |
$this |
getSqlResource
The SQL name of the entry. SQL names are case-sensitive.
Examples:
pubsub.topic.{PROJECT_ID}.{TOPIC_ID}
pubsub.topic.{PROJECT_ID}.
`{TOPIC.ID.SEPARATED.WITH.DOTS}
`bigquery.table.{PROJECT_ID}.{DATASET_ID}.{TABLE_ID}
bigquery.dataset.{PROJECT_ID}.{DATASET_ID}
datacatalog.entry.{PROJECT_ID}.{LOCATION_ID}.{ENTRY_GROUP_ID}.{ENTRY_ID}
Identifiers (*_ID
) should comply with the Lexical structure in Standard SQL.
Returns | |
---|---|
Type | Description |
string |
hasSqlResource
setSqlResource
The SQL name of the entry. SQL names are case-sensitive.
Examples:
pubsub.topic.{PROJECT_ID}.{TOPIC_ID}
pubsub.topic.{PROJECT_ID}.
`{TOPIC.ID.SEPARATED.WITH.DOTS}
`bigquery.table.{PROJECT_ID}.{DATASET_ID}.{TABLE_ID}
bigquery.dataset.{PROJECT_ID}.{DATASET_ID}
datacatalog.entry.{PROJECT_ID}.{LOCATION_ID}.{ENTRY_GROUP_ID}.{ENTRY_ID}
Identifiers (*_ID
) should comply with the Lexical structure in Standard SQL.
Parameter | |
---|---|
Name | Description |
var |
string
|
Returns | |
---|---|
Type | Description |
$this |
getFullyQualifiedName
Fully qualified name (FQN) of the resource.
FQNs take two forms:
- For non-regionalized resources:
{SYSTEM}:{PROJECT}.{PATH_TO_RESOURCE_SEPARATED_WITH_DOTS}
- For regionalized resources:
{SYSTEM}:{PROJECT}.{LOCATION_ID}.{PATH_TO_RESOURCE_SEPARATED_WITH_DOTS}
Example for a DPMS table:dataproc_metastore:{PROJECT_ID}.{LOCATION_ID}.{INSTANCE_ID}.{DATABASE_ID}.{TABLE_ID}
Returns | |
---|---|
Type | Description |
string |
hasFullyQualifiedName
setFullyQualifiedName
Fully qualified name (FQN) of the resource.
FQNs take two forms:
- For non-regionalized resources:
{SYSTEM}:{PROJECT}.{PATH_TO_RESOURCE_SEPARATED_WITH_DOTS}
- For regionalized resources:
{SYSTEM}:{PROJECT}.{LOCATION_ID}.{PATH_TO_RESOURCE_SEPARATED_WITH_DOTS}
Example for a DPMS table:dataproc_metastore:{PROJECT_ID}.{LOCATION_ID}.{INSTANCE_ID}.{DATABASE_ID}.{TABLE_ID}
Parameter | |
---|---|
Name | Description |
var |
string
|
Returns | |
---|---|
Type | Description |
$this |
getTargetName
Returns | |
---|---|
Type | Description |
string |