Skip to content

Commit

Permalink
feat(datacatalog): update the api
Browse files Browse the repository at this point in the history
#### datacatalog:v1

The following keys were added:
- resources.entries.methods.lookup.parameters.location (Total Keys: 2)
- resources.entries.methods.lookup.parameters.project (Total Keys: 2)
- schemas.GoogleCloudDatacatalogV1SearchCatalogResponse.properties.totalSize (Total Keys: 2)

#### datacatalog:v1beta1

The following keys were added:
- schemas.GoogleCloudDatacatalogV1beta1SearchCatalogResponse.properties.totalSize (Total Keys: 2)
  • Loading branch information
yoshi-automation committed May 24, 2023
1 parent 90725e7 commit acd9205
Show file tree
Hide file tree
Showing 8 changed files with 56 additions and 32 deletions.
1 change: 1 addition & 0 deletions docs/dyn/datacatalog_v1.catalog.html
Expand Up @@ -142,6 +142,7 @@ <h3>Method Details</h3>
&quot;userSpecifiedSystem&quot;: &quot;A String&quot;, # Custom source system that you can manually integrate Data Catalog with.
},
],
&quot;totalSize&quot;: 42, # The approximate total number of entries matched by the query.
&quot;unreachable&quot;: [ # Unreachable locations. Search results don&#x27;t include data from those locations. To get additional information on an error, repeat the search request and restrict it to specific locations by setting the `SearchCatalogRequest.scope.restricted_locations` parameter.
&quot;A String&quot;,
],
Expand Down
10 changes: 6 additions & 4 deletions docs/dyn/datacatalog_v1.entries.html
Expand Up @@ -78,7 +78,7 @@ <h2>Instance Methods</h2>
<code><a href="#close">close()</a></code></p>
<p class="firstline">Close httplib2 connections.</p>
<p class="toc_element">
<code><a href="#lookup">lookup(fullyQualifiedName=None, linkedResource=None, sqlResource=None, x__xgafv=None)</a></code></p>
<code><a href="#lookup">lookup(fullyQualifiedName=None, linkedResource=None, location=None, project=None, sqlResource=None, x__xgafv=None)</a></code></p>
<p class="firstline">Gets an entry by its target resource name. The resource name comes from the source Google Cloud Platform service.</p>
<h3>Method Details</h3>
<div class="method">
Expand All @@ -87,12 +87,14 @@ <h3>Method Details</h3>
</div>

<div class="method">
<code class="details" id="lookup">lookup(fullyQualifiedName=None, linkedResource=None, sqlResource=None, x__xgafv=None)</code>
<code class="details" id="lookup">lookup(fullyQualifiedName=None, linkedResource=None, location=None, project=None, sqlResource=None, x__xgafv=None)</code>
<pre>Gets an entry by its target resource name. The resource name comes from the source Google Cloud Platform service.

Args:
fullyQualifiedName: string, 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}`
fullyQualifiedName: string, [Fully Qualified Name (FQN)](https://cloud.google.com//data-catalog/docs/fully-qualified-names) 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}`
linkedResource: string, The full name of the Google Cloud Platform resource the Data Catalog entry represents. For more information, see [Full Resource Name] (https://cloud.google.com/apis/design/resource_names#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}`
location: string, Location where the lookup should be performed. Required to lookup entry that is not a part of `DPMS` or `DATAPLEX` `integrated_system` using its `fully_qualified_name`. Ignored in other cases.
project: string, Project where the lookup should be performed. Required to lookup entry that is not a part of `DPMS` or `DATAPLEX` `integrated_system` using its `fully_qualified_name`. Ignored in other cases.
sqlResource: string, 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] (https://cloud.google.com/bigquery/docs/reference/standard-sql/lexical).
x__xgafv: string, V1 error format.
Allowed values
Expand Down Expand Up @@ -225,7 +227,7 @@ <h3>Method Details</h3>
},
},
},
&quot;fullyQualifiedName&quot;: &quot;A String&quot;, # Fully qualified name (FQN) of the resource. Set automatically for entries representing resources from synced systems. Settable only during creation and read-only afterwards. Can be used for search and lookup of the entries. 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}`
&quot;fullyQualifiedName&quot;: &quot;A String&quot;, # [Fully Qualified Name (FQN)](https://cloud.google.com//data-catalog/docs/fully-qualified-names) of the resource. Set automatically for entries representing resources from synced systems. Settable only during creation, and read-only later. Can be used for search and lookup of the entries.
&quot;gcsFilesetSpec&quot;: { # Describes a Cloud Storage fileset entry. # Specification that applies to a Cloud Storage fileset. Valid only for entries with the `FILESET` type.
&quot;filePatterns&quot;: [ # Required. Patterns to identify a set of files in Google Cloud Storage. For more information, see [Wildcard Names] (https://cloud.google.com/storage/docs/gsutil/addlhelp/WildcardNames). Note: Currently, bucket wildcards are not supported. Examples of valid `file_patterns`: * `gs://bucket_name/dir/*`: matches all files in `bucket_name/dir` directory * `gs://bucket_name/dir/**`: matches all files in `bucket_name/dir` and all subdirectories * `gs://bucket_name/file*`: matches files prefixed by `file` in `bucket_name` * `gs://bucket_name/??.txt`: matches files with two characters followed by `.txt` in `bucket_name` * `gs://bucket_name/[aeiou].txt`: matches files that contain a single vowel character followed by `.txt` in `bucket_name` * `gs://bucket_name/[a-m].txt`: matches files that contain `a`, `b`, ... or `m` followed by `.txt` in `bucket_name` * `gs://bucket_name/a/*/b`: matches all files in `bucket_name` that match the `a/*/b` pattern, such as `a/c/b`, `a/d/b` * `gs://another_bucket/a.txt`: matches `gs://another_bucket/a.txt` You can combine wildcards to match complex sets of files, for example: `gs://bucket_name/[a-m]??.j*g`
&quot;A String&quot;,
Expand Down

0 comments on commit acd9205

Please sign in to comment.