mirror of
https://github.com/OMGeeky/google-apis-rs.git
synced 2026-02-23 15:49:49 +01:00
Update documentation
This commit is contained in:
Sebastian Thiel
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Delete - bigquery v2.0.4+20210327</title>
|
||||
<title>Delete - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Get - bigquery v2.0.4+20210327</title>
|
||||
<title>Get - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -338,11 +338,10 @@
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery.readonly</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform.read-only</em></li>
|
||||
</ul>
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery.readonly</em>.
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery</em>.
|
||||
You can set the scope for this method like this: <code>bigquery2 --scope <scope> datasets get ...</code></p>
|
||||
<h1 id="required-scalar-arguments">Required Scalar Arguments</h1>
|
||||
<ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Insert - bigquery v2.0.4+20210327</title>
|
||||
<title>Insert - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -363,6 +363,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
dataset-reference:
|
||||
dataset-id: string
|
||||
project-id: string
|
||||
default-collation: string
|
||||
default-encryption-configuration:
|
||||
kms-key-name: string
|
||||
default-partition-expiration-ms: string
|
||||
@@ -371,6 +372,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
etag: string
|
||||
friendly-name: string
|
||||
id: string
|
||||
is-case-insensitive: boolean
|
||||
kind: string
|
||||
labels: { string: string }
|
||||
last-modified-time: string
|
||||
@@ -397,51 +399,61 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..default-encryption-configuration kms-key-name=ipsum</code></p>
|
||||
<p><code>.. default-collation=ipsum</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] The default collation of the dataset.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>default-encryption-configuration kms-key-name=voluptua.</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Describes the Cloud KMS encryption key that will be used to protect destination BigQuery table. The BigQuery Service Account associated with your project requires access to this encryption key.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. default-partition-expiration-ms=voluptua.</code></p>
|
||||
<p><code>.. default-partition-expiration-ms=at</code></p>
|
||||
<ul>
|
||||
<li>[Optional] The default partition expiration for all partitioned tables in the dataset, in milliseconds. Once this property is set, all newly-created partitioned tables in the dataset will have an expirationMs property in the timePartitioning settings set to this value, and changing the value will only affect new tables, not existing ones. The storage in a partition will have an expiration time of its partition time plus this value. Setting this property overrides the use of defaultTableExpirationMs for partitioned tables: only one of defaultTableExpirationMs and defaultPartitionExpirationMs will be used for any new partitioned table. If you provide an explicit timePartitioning.expirationMs when creating or updating a partitioned table, that value takes precedence over the default partition expiration time indicated by this property.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>default-table-expiration-ms=at</code><ul>
|
||||
<li><code>default-table-expiration-ms=sanctus</code><ul>
|
||||
<li>[Optional] The default lifetime of all tables in the dataset, in milliseconds. The minimum value is 3600000 milliseconds (one hour). Once this property is set, all newly-created tables in the dataset will have an expirationTime property set to the creation time plus the value in this property, and changing the value will only affect new tables, not existing ones. When the expirationTime for a given table is reached, that table will be deleted automatically. If a table's expirationTime is modified or removed before the table expires, or if you provide an explicit expirationTime when creating a table, that value takes precedence over the default expiration time indicated by this property.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>description=sanctus</code><ul>
|
||||
<li><code>description=sed</code><ul>
|
||||
<li>[Optional] A user-friendly description of the dataset.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>etag=sed</code><ul>
|
||||
<li><code>etag=amet.</code><ul>
|
||||
<li>[Output-only] A hash of the resource.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>friendly-name=amet.</code><ul>
|
||||
<li><code>friendly-name=takimata</code><ul>
|
||||
<li>[Optional] A descriptive name for the dataset.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>id=takimata</code><ul>
|
||||
<li><code>id=amet.</code><ul>
|
||||
<li>[Output-only] The fully-qualified unique name of the dataset in the format projectId:datasetId. The dataset name without the project name is given in the datasetId field. When creating a new dataset, leave this field blank, and instead specify the datasetId field.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>kind=amet.</code><ul>
|
||||
<li><code>is-case-insensitive=true</code><ul>
|
||||
<li>[Optional] Indicates if table names are case insensitive in the dataset.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>kind=gubergren</code><ul>
|
||||
<li>[Output-only] The resource type.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>labels=key=duo</code><ul>
|
||||
<li><code>labels=key=lorem</code><ul>
|
||||
<li>The labels associated with this dataset. You can use these to organize and group your datasets. You can set this property when inserting or updating a dataset. See Creating and Updating Dataset Labels for more information.</li>
|
||||
<li>the value will be associated with the given <code>key</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>last-modified-time=ipsum</code><ul>
|
||||
<li><code>last-modified-time=gubergren</code><ul>
|
||||
<li>[Output-only] The date when this dataset or any of its tables was last modified, in milliseconds since the epoch.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>location=gubergren</code><ul>
|
||||
<li><code>location=eos</code><ul>
|
||||
<li>The geographic location where the dataset should reside. The default value is US. See details at https://cloud.google.com/bigquery/docs/locations.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -449,7 +461,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>[Output-only] Reserved for future use.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>self-link=gubergren</code><ul>
|
||||
<li><code>self-link=invidunt</code><ul>
|
||||
<li>[Output-only] A URL that can be used to access the resource again. You can use this URL in Get or Update requests to the resource.</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>List - bigquery v2.0.4+20210327</title>
|
||||
<title>List - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -341,11 +341,10 @@
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery.readonly</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform.read-only</em></li>
|
||||
</ul>
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery.readonly</em>.
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery</em>.
|
||||
You can set the scope for this method like this: <code>bigquery2 --scope <scope> datasets list ...</code></p>
|
||||
<h1 id="required-scalar-argument">Required Scalar Argument</h1>
|
||||
<ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Patch - bigquery v2.0.4+20210327</title>
|
||||
<title>Patch - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -367,6 +367,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
dataset-reference:
|
||||
dataset-id: string
|
||||
project-id: string
|
||||
default-collation: string
|
||||
default-encryption-configuration:
|
||||
kms-key-name: string
|
||||
default-partition-expiration-ms: string
|
||||
@@ -375,6 +376,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
etag: string
|
||||
friendly-name: string
|
||||
id: string
|
||||
is-case-insensitive: boolean
|
||||
kind: string
|
||||
labels: { string: string }
|
||||
last-modified-time: string
|
||||
@@ -386,37 +388,43 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r . creation-time=eos</code><ul>
|
||||
<li><code>-r . creation-time=amet</code><ul>
|
||||
<li>[Output-only] The time when this dataset was created, in milliseconds since the epoch.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>dataset-reference dataset-id=dolor</code><ul>
|
||||
<li><code>dataset-reference dataset-id=duo</code><ul>
|
||||
<li>[Required] A unique ID for this dataset, without the project name. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 1,024 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>project-id=ea</code></p>
|
||||
<p><code>project-id=ipsum</code></p>
|
||||
<ul>
|
||||
<li>[Optional] The ID of the project containing this dataset.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..default-encryption-configuration kms-key-name=ipsum</code></p>
|
||||
<p><code>.. default-collation=sed</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] The default collation of the dataset.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>default-encryption-configuration kms-key-name=ut</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Describes the Cloud KMS encryption key that will be used to protect destination BigQuery table. The BigQuery Service Account associated with your project requires access to this encryption key.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. default-partition-expiration-ms=invidunt</code></p>
|
||||
<p><code>.. default-partition-expiration-ms=gubergren</code></p>
|
||||
<ul>
|
||||
<li>[Optional] The default partition expiration for all partitioned tables in the dataset, in milliseconds. Once this property is set, all newly-created partitioned tables in the dataset will have an expirationMs property in the timePartitioning settings set to this value, and changing the value will only affect new tables, not existing ones. The storage in a partition will have an expiration time of its partition time plus this value. Setting this property overrides the use of defaultTableExpirationMs for partitioned tables: only one of defaultTableExpirationMs and defaultPartitionExpirationMs will be used for any new partitioned table. If you provide an explicit timePartitioning.expirationMs when creating or updating a partitioned table, that value takes precedence over the default partition expiration time indicated by this property.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>default-table-expiration-ms=amet</code><ul>
|
||||
<li><code>default-table-expiration-ms=rebum.</code><ul>
|
||||
<li>[Optional] The default lifetime of all tables in the dataset, in milliseconds. The minimum value is 3600000 milliseconds (one hour). Once this property is set, all newly-created tables in the dataset will have an expirationTime property set to the creation time plus the value in this property, and changing the value will only affect new tables, not existing ones. When the expirationTime for a given table is reached, that table will be deleted automatically. If a table's expirationTime is modified or removed before the table expires, or if you provide an explicit expirationTime when creating a table, that value takes precedence over the default expiration time indicated by this property.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>description=duo</code><ul>
|
||||
<li><code>description=est</code><ul>
|
||||
<li>[Optional] A user-friendly description of the dataset.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -424,36 +432,40 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>[Output-only] A hash of the resource.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>friendly-name=sed</code><ul>
|
||||
<li><code>friendly-name=ipsum</code><ul>
|
||||
<li>[Optional] A descriptive name for the dataset.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>id=ut</code><ul>
|
||||
<li><code>id=est</code><ul>
|
||||
<li>[Output-only] The fully-qualified unique name of the dataset in the format projectId:datasetId. The dataset name without the project name is given in the datasetId field. When creating a new dataset, leave this field blank, and instead specify the datasetId field.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>kind=gubergren</code><ul>
|
||||
<li><code>is-case-insensitive=true</code><ul>
|
||||
<li>[Optional] Indicates if table names are case insensitive in the dataset.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>kind=ea</code><ul>
|
||||
<li>[Output-only] The resource type.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>labels=key=rebum.</code><ul>
|
||||
<li><code>labels=key=dolor</code><ul>
|
||||
<li>The labels associated with this dataset. You can use these to organize and group your datasets. You can set this property when inserting or updating a dataset. See Creating and Updating Dataset Labels for more information.</li>
|
||||
<li>the value will be associated with the given <code>key</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>last-modified-time=est</code><ul>
|
||||
<li><code>last-modified-time=lorem</code><ul>
|
||||
<li>[Output-only] The date when this dataset or any of its tables was last modified, in milliseconds since the epoch.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>location=ipsum</code><ul>
|
||||
<li><code>location=eos</code><ul>
|
||||
<li>The geographic location where the dataset should reside. The default value is US. See details at https://cloud.google.com/bigquery/docs/locations.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>satisfies-pzs=true</code><ul>
|
||||
<li><code>satisfies-pzs=false</code><ul>
|
||||
<li>[Output-only] Reserved for future use.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>self-link=est</code><ul>
|
||||
<li><code>self-link=sed</code><ul>
|
||||
<li>[Output-only] A URL that can be used to access the resource again. You can use this URL in Get or Update requests to the resource.</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Update - bigquery v2.0.4+20210327</title>
|
||||
<title>Update - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -367,6 +367,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
dataset-reference:
|
||||
dataset-id: string
|
||||
project-id: string
|
||||
default-collation: string
|
||||
default-encryption-configuration:
|
||||
kms-key-name: string
|
||||
default-partition-expiration-ms: string
|
||||
@@ -375,6 +376,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
etag: string
|
||||
friendly-name: string
|
||||
id: string
|
||||
is-case-insensitive: boolean
|
||||
kind: string
|
||||
labels: { string: string }
|
||||
last-modified-time: string
|
||||
@@ -386,57 +388,67 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r . creation-time=gubergren</code><ul>
|
||||
<li><code>-r . creation-time=duo</code><ul>
|
||||
<li>[Output-only] The time when this dataset was created, in milliseconds since the epoch.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>dataset-reference dataset-id=ea</code><ul>
|
||||
<li><code>dataset-reference dataset-id=sed</code><ul>
|
||||
<li>[Required] A unique ID for this dataset, without the project name. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 1,024 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>project-id=dolor</code></p>
|
||||
<p><code>project-id=no</code></p>
|
||||
<ul>
|
||||
<li>[Optional] The ID of the project containing this dataset.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..default-encryption-configuration kms-key-name=lorem</code></p>
|
||||
<p><code>.. default-collation=stet</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] The default collation of the dataset.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>default-encryption-configuration kms-key-name=kasd</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Describes the Cloud KMS encryption key that will be used to protect destination BigQuery table. The BigQuery Service Account associated with your project requires access to this encryption key.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. default-partition-expiration-ms=eos</code></p>
|
||||
<p><code>.. default-partition-expiration-ms=et</code></p>
|
||||
<ul>
|
||||
<li>[Optional] The default partition expiration for all partitioned tables in the dataset, in milliseconds. Once this property is set, all newly-created partitioned tables in the dataset will have an expirationMs property in the timePartitioning settings set to this value, and changing the value will only affect new tables, not existing ones. The storage in a partition will have an expiration time of its partition time plus this value. Setting this property overrides the use of defaultTableExpirationMs for partitioned tables: only one of defaultTableExpirationMs and defaultPartitionExpirationMs will be used for any new partitioned table. If you provide an explicit timePartitioning.expirationMs when creating or updating a partitioned table, that value takes precedence over the default partition expiration time indicated by this property.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>default-table-expiration-ms=labore</code><ul>
|
||||
<li><code>default-table-expiration-ms=sed</code><ul>
|
||||
<li>[Optional] The default lifetime of all tables in the dataset, in milliseconds. The minimum value is 3600000 milliseconds (one hour). Once this property is set, all newly-created tables in the dataset will have an expirationTime property set to the creation time plus the value in this property, and changing the value will only affect new tables, not existing ones. When the expirationTime for a given table is reached, that table will be deleted automatically. If a table's expirationTime is modified or removed before the table expires, or if you provide an explicit expirationTime when creating a table, that value takes precedence over the default expiration time indicated by this property.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>description=sed</code><ul>
|
||||
<li><code>description=et</code><ul>
|
||||
<li>[Optional] A user-friendly description of the dataset.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>etag=duo</code><ul>
|
||||
<li><code>etag=et</code><ul>
|
||||
<li>[Output-only] A hash of the resource.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>friendly-name=sed</code><ul>
|
||||
<li><code>friendly-name=vero</code><ul>
|
||||
<li>[Optional] A descriptive name for the dataset.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>id=no</code><ul>
|
||||
<li><code>id=erat</code><ul>
|
||||
<li>[Output-only] The fully-qualified unique name of the dataset in the format projectId:datasetId. The dataset name without the project name is given in the datasetId field. When creating a new dataset, leave this field blank, and instead specify the datasetId field.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>kind=stet</code><ul>
|
||||
<li><code>is-case-insensitive=false</code><ul>
|
||||
<li>[Optional] Indicates if table names are case insensitive in the dataset.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>kind=duo</code><ul>
|
||||
<li>[Output-only] The resource type.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>labels=key=kasd</code><ul>
|
||||
<li><code>labels=key=dolore</code><ul>
|
||||
<li>The labels associated with this dataset. You can use these to organize and group your datasets. You can set this property when inserting or updating a dataset. See Creating and Updating Dataset Labels for more information.</li>
|
||||
<li>the value will be associated with the given <code>key</code></li>
|
||||
</ul>
|
||||
@@ -445,15 +457,15 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>[Output-only] The date when this dataset or any of its tables was last modified, in milliseconds since the epoch.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>location=sed</code><ul>
|
||||
<li><code>location=voluptua.</code><ul>
|
||||
<li>The geographic location where the dataset should reside. The default value is US. See details at https://cloud.google.com/bigquery/docs/locations.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>satisfies-pzs=true</code><ul>
|
||||
<li><code>satisfies-pzs=false</code><ul>
|
||||
<li>[Output-only] Reserved for future use.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>self-link=vero</code><ul>
|
||||
<li><code>self-link=diam</code><ul>
|
||||
<li>[Output-only] A URL that can be used to access the resource again. You can use this URL in Get or Update requests to the resource.</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>bigquery v2.0.4+20210327</title>
|
||||
<title>bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href="." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href="." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -336,7 +336,7 @@ capabilities. Errors will be printed to standard error, and cause the program's
|
||||
|
||||
<p>Find the source code <a href="https://github.com/Byron/google-apis-rs/tree/main/gen/bigquery2-cli">on github</a>.</p>
|
||||
<h1 id="usage">Usage</h1>
|
||||
<p>This documentation was generated from the <em>bigquery</em> API at revision <em>20210327</em>. The CLI is at version <em>2.0.4</em>.</p>
|
||||
<p>This documentation was generated from the <em>bigquery</em> API at revision <em>20220222</em>. The CLI is at version <em>3.0.0</em>.</p>
|
||||
<pre><code class="bash">bigquery2 [options]
|
||||
datasets
|
||||
delete <project-id> <dataset-id> [-p <v>]...
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Cancel - bigquery v2.0.4+20210327</title>
|
||||
<title>Cancel - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Delete - bigquery v2.0.4+20210327</title>
|
||||
<title>Delete - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -333,7 +333,7 @@
|
||||
</div>
|
||||
<div role="main">
|
||||
<div class="section">
|
||||
<p>Requests that a job is deleted. This call will return when the job is deleted. This method is available in limited preview.</p>
|
||||
<p>Requests the deletion of the metadata of a job. This call returns when the job's metadata is deleted.</p>
|
||||
<h1 id="scopes">Scopes</h1>
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
@@ -345,11 +345,11 @@ You can set the scope for this method like this: <code>bigquery2 --scope <sco
|
||||
<h1 id="required-scalar-arguments">Required Scalar Arguments</h1>
|
||||
<ul>
|
||||
<li><strong><project-id></strong> <em>(string)</em><ul>
|
||||
<li>Required. Project ID of the job to be deleted.</li>
|
||||
<li>Required. Project ID of the job for which metadata is to be deleted.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><strong><job-id></strong> <em>(string)</em><ul>
|
||||
<li>Required. Job ID of the job to be deleted. If this is a parent job which has child jobs, all child jobs will be deleted as well. Deletion of child jobs directly is not allowed.</li>
|
||||
<li>Required. Job ID of the job for which metadata is to be deleted. If this is a parent job which has child jobs, the metadata from all child jobs will be deleted as well. Direct deletion of the metadata of child jobs is not allowed.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Get Query Results - bigquery v2.0.4+20210327</title>
|
||||
<title>Get Query Results - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -341,11 +341,10 @@
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery.readonly</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform.read-only</em></li>
|
||||
</ul>
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery.readonly</em>.
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery</em>.
|
||||
You can set the scope for this method like this: <code>bigquery2 --scope <scope> jobs get-query-results ...</code></p>
|
||||
<h1 id="required-scalar-arguments">Required Scalar Arguments</h1>
|
||||
<ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Get - bigquery v2.0.4+20210327</title>
|
||||
<title>Get - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -341,11 +341,10 @@
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery.readonly</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform.read-only</em></li>
|
||||
</ul>
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery.readonly</em>.
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery</em>.
|
||||
You can set the scope for this method like this: <code>bigquery2 --scope <scope> jobs get ...</code></p>
|
||||
<h1 id="required-scalar-arguments">Required Scalar Arguments</h1>
|
||||
<ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Insert - bigquery v2.0.4+20210327</title>
|
||||
<title>Insert - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -416,6 +416,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
table-id: string
|
||||
destination-table-properties:
|
||||
description: string
|
||||
expiration-time: string
|
||||
friendly-name: string
|
||||
labels: { string: string }
|
||||
encoding: string
|
||||
@@ -431,6 +432,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
parquet-options:
|
||||
enable-list-inference: boolean
|
||||
enum-as-string: boolean
|
||||
preserve-ascii-control-characters: boolean
|
||||
projection-fields: [string]
|
||||
quote: string
|
||||
range-partitioning:
|
||||
@@ -513,9 +515,15 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
num-child-jobs: string
|
||||
parent-job-id: string
|
||||
query:
|
||||
bi-engine-statistics:
|
||||
bi-engine-mode: string
|
||||
billing-tier: integer
|
||||
cache-hit: boolean
|
||||
ddl-affected-row-access-policy-count: int64
|
||||
ddl-destination-table:
|
||||
dataset-id: string
|
||||
project-id: string
|
||||
table-id: string
|
||||
ddl-operation-performed: string
|
||||
ddl-target-dataset:
|
||||
dataset-id: string
|
||||
@@ -533,7 +541,13 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
dataset-id: string
|
||||
project-id: string
|
||||
table-id: string
|
||||
dml-stats:
|
||||
deleted-row-count: int64
|
||||
inserted-row-count: int64
|
||||
updated-row-count: int64
|
||||
estimated-bytes-processed: string
|
||||
ml-statistics:
|
||||
max-iterations: string
|
||||
model-training:
|
||||
current-iteration: integer
|
||||
expected-total-iterations: string
|
||||
@@ -552,12 +566,12 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
row-level-security-applied: boolean
|
||||
script-statistics:
|
||||
evaluation-kind: string
|
||||
session-info-template:
|
||||
session-info:
|
||||
session-id: string
|
||||
start-time: string
|
||||
total-bytes-processed: string
|
||||
total-slot-ms: string
|
||||
transaction-info-template:
|
||||
transaction-info:
|
||||
transaction-id: string
|
||||
status:
|
||||
error-result:
|
||||
@@ -572,82 +586,82 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r .configuration.copy create-disposition=erat</code><ul>
|
||||
<li><code>-r .configuration.copy create-disposition=dolor</code><ul>
|
||||
<li>[Optional] Specifies whether the job is allowed to create new tables. The following values are supported: CREATE_IF_NEEDED: If the table does not exist, BigQuery creates the table. CREATE_NEVER: The table must already exist. If it does not, a 'notFound' error is returned in the job result. The default value is CREATE_IF_NEEDED. Creation, truncation and append actions occur as one atomic update upon job completion.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>destination-encryption-configuration kms-key-name=sed</code></p>
|
||||
<p><code>destination-encryption-configuration kms-key-name=et</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Describes the Cloud KMS encryption key that will be used to protect destination BigQuery table. The BigQuery Service Account associated with your project requires access to this encryption key.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..destination-table dataset-id=duo</code></p>
|
||||
<p><code>..destination-table dataset-id=et</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the dataset containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>project-id=dolore</code><ul>
|
||||
<li><code>project-id=sadipscing</code><ul>
|
||||
<li>[Required] The ID of the project containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>table-id=et</code></p>
|
||||
<p><code>table-id=stet</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the table. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 1,024 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. operation-type=voluptua.</code></p>
|
||||
<p><code>.. operation-type=dolor</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Supported operation types in table copy job.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>source-table dataset-id=amet.</code><ul>
|
||||
<li><code>source-table dataset-id=duo</code><ul>
|
||||
<li>[Required] The ID of the dataset containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>project-id=consetetur</code><ul>
|
||||
<li><code>project-id=vero</code><ul>
|
||||
<li>[Required] The ID of the project containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>table-id=diam</code></p>
|
||||
<p><code>table-id=vero</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the table. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 1,024 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. write-disposition=dolor</code></p>
|
||||
<p><code>.. write-disposition=invidunt</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Specifies the action that occurs if the destination table already exists. The following values are supported: WRITE_TRUNCATE: If the table already exists, BigQuery overwrites the table data. WRITE_APPEND: If the table already exists, BigQuery appends the data to the table. WRITE_EMPTY: If the table already exists and contains data, a 'duplicate' error is returned in the job result. The default value is WRITE_EMPTY. Each action is atomic and only occurs if BigQuery is able to complete the job successfully. Creation, truncation and append actions occur as one atomic update upon job completion.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. dry-run=false</code></p>
|
||||
<p><code>.. dry-run=true</code></p>
|
||||
<ul>
|
||||
<li>[Optional] If set, don't actually run this job. A valid query will return a mostly empty response with some processing statistics, while an invalid query will return the same error it would if it wasn't a dry run. Behavior of non-query jobs is undefined.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>extract compression=stet</code><ul>
|
||||
<li><code>extract compression=vero</code><ul>
|
||||
<li>[Optional] The compression type to use for exported files. Possible values include GZIP, DEFLATE, SNAPPY, and NONE. The default value is NONE. DEFLATE and SNAPPY are only supported for Avro. Not applicable when extracting models.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>destination-format=dolor</code><ul>
|
||||
<li><code>destination-format=elitr</code><ul>
|
||||
<li>[Optional] The exported file format. Possible values include CSV, NEWLINE_DELIMITED_JSON, PARQUET or AVRO for tables and ML_TF_SAVED_MODEL or ML_XGBOOST_BOOSTER for models. The default value for tables is CSV. Tables with nested or repeated fields cannot be exported as CSV. The default value for models is ML_TF_SAVED_MODEL.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>destination-uri=duo</code><ul>
|
||||
<li><code>destination-uri=lorem</code><ul>
|
||||
<li>[Pick one] DEPRECATED: Use destinationUris instead, passing only one URI as necessary. The fully-qualified Google Cloud Storage URI where the extracted table should be written.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>destination-uris=vero</code><ul>
|
||||
<li><code>destination-uris=diam</code><ul>
|
||||
<li>[Pick one] A list of fully-qualified Google Cloud Storage URIs where the extracted table should be written.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>field-delimiter=vero</code><ul>
|
||||
<li><code>field-delimiter=no</code><ul>
|
||||
<li>[Optional] Delimiter to use between fields in the exported data. Default is ','. Not applicable when extracting models.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -655,32 +669,32 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>[Optional] Whether to print out a header row in the results. Default is true. Not applicable when extracting models.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>source-model dataset-id=stet</code><ul>
|
||||
<li><code>source-model dataset-id=accusam</code><ul>
|
||||
<li>[Required] The ID of the dataset containing this model.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>model-id=vero</code><ul>
|
||||
<li><code>model-id=takimata</code><ul>
|
||||
<li>[Required] The ID of the model. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 1,024 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>project-id=elitr</code></p>
|
||||
<p><code>project-id=consetetur</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the project containing this model.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..source-table dataset-id=lorem</code></p>
|
||||
<p><code>..source-table dataset-id=voluptua.</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the dataset containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>project-id=diam</code><ul>
|
||||
<li><code>project-id=et</code><ul>
|
||||
<li>[Required] The ID of the project containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>table-id=no</code></p>
|
||||
<p><code>table-id=erat</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the table. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 1,024 characters.</li>
|
||||
</ul>
|
||||
@@ -692,21 +706,21 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. job-timeout-ms=accusam</code></p>
|
||||
<p><code>.. job-timeout-ms=amet.</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Job timeout in milliseconds. If this time limit is exceeded, BigQuery may attempt to terminate the job.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>job-type=takimata</code><ul>
|
||||
<li><code>job-type=sed</code><ul>
|
||||
<li>[Output-only] The type of the job. Can be QUERY, LOAD, EXTRACT, COPY or UNKNOWN.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>labels=key=consetetur</code><ul>
|
||||
<li><code>labels=key=takimata</code><ul>
|
||||
<li>The labels associated with this job. You can use these to organize and group your jobs. Label keys and values can be no longer than 63 characters, can only contain lowercase letters, numeric characters, underscores and dashes. International characters are allowed. Label values are optional. Label keys must start with a letter and each label in the list must have a different key.</li>
|
||||
<li>the value will be associated with the given <code>key</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>load allow-jagged-rows=false</code><ul>
|
||||
<li><code>load allow-jagged-rows=true</code><ul>
|
||||
<li>[Optional] Accept rows that are missing trailing optional columns. The missing values are treated as nulls. If false, records with missing trailing columns are treated as bad records, and if there are too many bad records, an invalid error is returned in the job result. The default value is false. Only applicable to CSV, ignored for other formats.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -714,78 +728,82 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>Indicates if BigQuery should allow quoted data sections that contain newline characters in a CSV file. The default value is false.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>autodetect=true</code><ul>
|
||||
<li><code>autodetect=false</code><ul>
|
||||
<li>[Optional] Indicates if we should automatically infer the options and schema for CSV and JSON sources.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>clustering fields=et</code></p>
|
||||
<p><code>clustering fields=dolore</code></p>
|
||||
<ul>
|
||||
<li>[Repeated] One or more fields on which data should be clustered. Only top-level, non-repeated, simple-type fields are supported. When you cluster a table using multiple columns, the order of columns you specify is important. The order of the specified columns determines the sort order of the data.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. create-disposition=accusam</code></p>
|
||||
<p><code>.. create-disposition=dolore</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Specifies whether the job is allowed to create new tables. The following values are supported: CREATE_IF_NEEDED: If the table does not exist, BigQuery creates the table. CREATE_NEVER: The table must already exist. If it does not, a 'notFound' error is returned in the job result. The default value is CREATE_IF_NEEDED. Creation, truncation and append actions occur as one atomic update upon job completion.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>decimal-target-types=voluptua.</code><ul>
|
||||
<li>Defines the list of possible SQL data types to which the source decimal values are converted. This list and the precision and the scale parameters of the decimal field determine the target type. In the order of NUMERIC, BIGNUMERIC (<a href="..//products/#product-launch-stages">Preview</a>), and STRING, a type is picked if it is in the specified list and if it supports the precision and the scale. STRING supports all precision and scale values. If none of the listed types supports the precision and the scale, the type supporting the widest range in the specified list is picked, and if a value exceeds the supported range when reading the data, an error will be thrown. Example: Suppose the value of this field is ["NUMERIC", "BIGNUMERIC"]. If (precision,scale) is: * (38,9) -> NUMERIC; * (39,9) -> BIGNUMERIC (NUMERIC cannot hold 30 integer digits); * (38,10) -> BIGNUMERIC (NUMERIC cannot hold 10 fractional digits); * (76,38) -> BIGNUMERIC; * (77,38) -> BIGNUMERIC (error if value exeeds supported range). This field cannot contain duplicate types. The order of the types in this field is ignored. For example, ["BIGNUMERIC", "NUMERIC"] is the same as ["NUMERIC", "BIGNUMERIC"] and NUMERIC always takes precedence over BIGNUMERIC. Defaults to ["NUMERIC", "STRING"] for ORC and ["NUMERIC"] for the other file formats.</li>
|
||||
<li><code>decimal-target-types=dolore</code><ul>
|
||||
<li>[Optional] Defines the list of possible SQL data types to which the source decimal values are converted. This list and the precision and the scale parameters of the decimal field determine the target type. In the order of NUMERIC, BIGNUMERIC, and STRING, a type is picked if it is in the specified list and if it supports the precision and the scale. STRING supports all precision and scale values. If none of the listed types supports the precision and the scale, the type supporting the widest range in the specified list is picked, and if a value exceeds the supported range when reading the data, an error will be thrown. Example: Suppose the value of this field is ["NUMERIC", "BIGNUMERIC"]. If (precision,scale) is: (38,9) -> NUMERIC; (39,9) -> BIGNUMERIC (NUMERIC cannot hold 30 integer digits); (38,10) -> BIGNUMERIC (NUMERIC cannot hold 10 fractional digits); (76,38) -> BIGNUMERIC; (77,38) -> BIGNUMERIC (error if value exeeds supported range). This field cannot contain duplicate types. The order of the types in this field is ignored. For example, ["BIGNUMERIC", "NUMERIC"] is the same as ["NUMERIC", "BIGNUMERIC"] and NUMERIC always takes precedence over BIGNUMERIC. Defaults to ["NUMERIC", "STRING"] for ORC and ["NUMERIC"] for the other file formats.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>destination-encryption-configuration kms-key-name=dolore</code></p>
|
||||
<p><code>destination-encryption-configuration kms-key-name=voluptua.</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Describes the Cloud KMS encryption key that will be used to protect destination BigQuery table. The BigQuery Service Account associated with your project requires access to this encryption key.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..destination-table dataset-id=dolore</code></p>
|
||||
<p><code>..destination-table dataset-id=amet.</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the dataset containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>project-id=dolore</code><ul>
|
||||
<li><code>project-id=ea</code><ul>
|
||||
<li>[Required] The ID of the project containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>table-id=voluptua.</code></p>
|
||||
<p><code>table-id=sadipscing</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the table. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 1,024 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..destination-table-properties description=amet.</code></p>
|
||||
<p><code>..destination-table-properties description=lorem</code></p>
|
||||
<ul>
|
||||
<li>[Optional] The description for the destination table. This will only be used if the destination table is newly created. If the table already exists and a value different than the current description is provided, the job will fail.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>friendly-name=ea</code><ul>
|
||||
<li><code>expiration-time=invidunt</code><ul>
|
||||
<li>[Internal] This field is for Google internal use only.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>friendly-name=no</code><ul>
|
||||
<li>[Optional] The friendly name for the destination table. This will only be used if the destination table is newly created. If the table already exists and a value different than the current friendly name is provided, the job will fail.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>labels=key=sadipscing</code></p>
|
||||
<p><code>labels=key=est</code></p>
|
||||
<ul>
|
||||
<li>[Optional] The labels associated with this table. You can use these to organize and group your tables. This will only be used if the destination table is newly created. If the table already exists and labels are different than the current labels are provided, the job will fail.</li>
|
||||
<li>the value will be associated with the given <code>key</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. encoding=lorem</code></p>
|
||||
<p><code>.. encoding=at</code></p>
|
||||
<ul>
|
||||
<li>[Optional] The character encoding of the data. The supported values are UTF-8 or ISO-8859-1. The default value is UTF-8. BigQuery decodes the data after the raw, binary data has been split using the values of the quote and fieldDelimiter properties.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>field-delimiter=invidunt</code><ul>
|
||||
<li><code>field-delimiter=sed</code><ul>
|
||||
<li>[Optional] The separator for fields in a CSV file. The separator can be any ISO-8859-1 single-byte character. To use a character in the range 128-255, you must encode the character as UTF8. BigQuery converts the string to ISO-8859-1 encoding, and then uses the first byte of the encoded string to split the data in its raw, binary state. BigQuery also supports the escape sequence "\t" to specify a tab separator. The default value is a comma (',').</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>hive-partitioning-options mode=no</code><ul>
|
||||
<li><code>hive-partitioning-options mode=sit</code><ul>
|
||||
<li>[Optional] When set, what mode of hive partitioning to use when reading data. The following modes are supported. (1) AUTO: automatically infer partition key name(s) and type(s). (2) STRINGS: automatically infer partition key name(s). All types are interpreted as strings. (3) CUSTOM: partition key schema is encoded in the source URI prefix. Not all storage formats support hive partitioning. Requesting hive partitioning on an unsupported format will lead to an error. Currently supported types include: AVRO, CSV, JSON, ORC and Parquet.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -794,7 +812,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>source-uri-prefix=sit</code></p>
|
||||
<p><code>source-uri-prefix=aliquyam</code></p>
|
||||
<ul>
|
||||
<li>[Optional] When hive partition detection is requested, a common prefix for all source uris should be supplied. The prefix must end immediately before the partition key encoding begins. For example, consider files following this data layout. gs://bucket/path_to_table/dt=2019-01-01/country=BR/id=7/file.avro gs://bucket/path_to_table/dt=2018-12-31/country=CA/id=3/file.avro When hive partitioning is requested with either AUTO or STRINGS detection, the common prefix can be either of gs://bucket/path_to_table or gs://bucket/path_to_table/ (trailing slash does not matter).</li>
|
||||
</ul>
|
||||
@@ -805,15 +823,15 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>[Optional] Indicates if BigQuery should allow extra values that are not represented in the table schema. If true, the extra values are ignored. If false, records with extra columns are treated as bad records, and if there are too many bad records, an invalid error is returned in the job result. The default value is false. The sourceFormat property determines what BigQuery treats as an extra value: CSV: Trailing columns JSON: Named values that don't match any column names</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>json-extension=aliquyam</code><ul>
|
||||
<li><code>json-extension=est</code><ul>
|
||||
<li>[Optional] If sourceFormat is set to newline-delimited JSON, indicates whether it should be processed as a JSON variant such as GeoJSON. For a sourceFormat other than JSON, omit this field. If the sourceFormat is newline-delimited JSON: - for newline-delimited GeoJSON: set to GEOJSON.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>max-bad-records=96</code><ul>
|
||||
<li><code>max-bad-records=71</code><ul>
|
||||
<li>[Optional] The maximum number of bad records that BigQuery can ignore when running the job. If the number of bad records exceeds this value, an invalid error is returned in the job result. This is only valid for CSV and JSON. The default value is 0, which requires that all records are valid.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>null-marker=et</code><ul>
|
||||
<li><code>null-marker=diam</code><ul>
|
||||
<li>[Optional] Specifies a string that represents a null value in a CSV file. For example, if you specify "\N", BigQuery interprets "\N" as a null value when loading a CSV file. The default value is the empty string. If you set this property to a custom value, BigQuery throws an error if an empty string is present for all data types except for STRING and BYTE. For STRING and BYTE columns, BigQuery interprets the empty string as an empty value.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -828,107 +846,111 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. projection-fields=et</code></p>
|
||||
<p><code>.. preserve-ascii-control-characters=false</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Preserves the embedded ASCII control characters (the first 32 characters in the ASCII-table, from '\x00' to '\x1F') when loading from CSV. Only applicable to CSV, ignored for other formats.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>projection-fields=no</code><ul>
|
||||
<li>If sourceFormat is set to "DATASTORE_BACKUP", indicates which entity properties to load into BigQuery from a Cloud Datastore backup. Property names are case sensitive and must be top-level properties. If no properties are specified, BigQuery loads all properties. If any named property isn't found in the Cloud Datastore backup, an invalid error is returned in the job result.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>quote=sed</code><ul>
|
||||
<li><code>quote=et</code><ul>
|
||||
<li>[Optional] The value that is used to quote data sections in a CSV file. BigQuery converts the string to ISO-8859-1 encoding, and then uses the first byte of the encoded string to split the data in its raw, binary state. The default value is a double-quote ('"'). If your data does not contain quoted sections, set the property value to an empty string. If your data contains quoted newline characters, you must also set the allowQuotedNewlines property to true.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>range-partitioning field=no</code><ul>
|
||||
<li><code>range-partitioning field=elitr</code><ul>
|
||||
<li>[TrustedTester] [Required] The table is partitioned by this field. The field must be a top-level NULLABLE/REQUIRED field. The only supported type is INTEGER/INT64.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>range end=et</code><ul>
|
||||
<li><code>range end=sed</code><ul>
|
||||
<li>[TrustedTester] [Required] The end of range partitioning, exclusive.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>interval=elitr</code><ul>
|
||||
<li><code>interval=no</code><ul>
|
||||
<li>[TrustedTester] [Required] The width of each interval.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>start=sed</code></p>
|
||||
<p><code>start=nonumy</code></p>
|
||||
<ul>
|
||||
<li>[TrustedTester] [Required] The start of range partitioning, inclusive.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>... schema-inline=no</code></p>
|
||||
<p><code>... schema-inline=at</code></p>
|
||||
<ul>
|
||||
<li>[Deprecated] The inline schema. For CSV schemas, specify as "Field1:Type1[,Field2:Type2]*". For example, "foo:STRING, bar:INTEGER, baz:FLOAT".</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>schema-inline-format=nonumy</code><ul>
|
||||
<li><code>schema-inline-format=sadipscing</code><ul>
|
||||
<li>[Deprecated] The format of the schemaInline property.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>schema-update-options=at</code><ul>
|
||||
<li><code>schema-update-options=aliquyam</code><ul>
|
||||
<li>Allows the schema of the destination table to be updated as a side effect of the load job if a schema is autodetected or supplied in the job configuration. Schema update options are supported in two cases: when writeDisposition is WRITE_APPEND; when writeDisposition is WRITE_TRUNCATE and the destination table is a partition of a table, specified by partition decorators. For normal tables, WRITE_TRUNCATE will always overwrite the schema. One or more of the following values are specified: ALLOW_FIELD_ADDITION: allow adding a nullable field to the schema. ALLOW_FIELD_RELAXATION: allow relaxing a required field in the original schema to nullable.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>skip-leading-rows=56</code><ul>
|
||||
<li><code>skip-leading-rows=32</code><ul>
|
||||
<li>[Optional] The number of rows at the top of a CSV file that BigQuery will skip when loading the data. The default value is 0. This property is useful if you have header rows in the file that should be skipped.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>source-format=aliquyam</code><ul>
|
||||
<li><code>source-format=sadipscing</code><ul>
|
||||
<li>[Optional] The format of the data files. For CSV files, specify "CSV". For datastore backups, specify "DATASTORE_BACKUP". For newline-delimited JSON, specify "NEWLINE_DELIMITED_JSON". For Avro, specify "AVRO". For parquet, specify "PARQUET". For orc, specify "ORC". The default value is CSV.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>source-uris=dolores</code><ul>
|
||||
<li><code>source-uris=erat</code><ul>
|
||||
<li>[Required] The fully-qualified URIs that point to your data in Google Cloud. For Google Cloud Storage URIs: Each URI can contain one '<em>' wildcard character and it must come after the 'bucket' name. Size limits related to load jobs apply to external data sources. For Google Cloud Bigtable URIs: Exactly one URI can be specified and it has be a fully specified and valid HTTPS URL for a Google Cloud Bigtable table. For Google Cloud Datastore backups: Exactly one URI can be specified. Also, the '</em>' wildcard character is not allowed.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>time-partitioning expiration-ms=sadipscing</code><ul>
|
||||
<li><code>time-partitioning expiration-ms=aliquyam</code><ul>
|
||||
<li>[Optional] Number of milliseconds for which to keep the storage for partitions in the table. The storage in a partition will have an expiration time of its partition time plus this value.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>field=erat</code><ul>
|
||||
<li><code>field=amet</code><ul>
|
||||
<li>[Beta] [Optional] If not set, the table is partitioned by pseudo column, referenced via either '_PARTITIONTIME' as TIMESTAMP type, or '_PARTITIONDATE' as DATE type. If field is specified, the table is instead partitioned by this field. The field must be a top-level TIMESTAMP or DATE field. Its mode must be NULLABLE or REQUIRED.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>require-partition-filter=false</code><ul>
|
||||
<li><code>require-partition-filter=true</code><ul>
|
||||
<li>No description provided.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>type=amet</code></p>
|
||||
<p><code>type=et</code></p>
|
||||
<ul>
|
||||
<li>[Required] The supported types are DAY, HOUR, MONTH, and YEAR, which will generate one partition per day, hour, month, and year, respectively. When the type is not specified, the default behavior is DAY.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. use-avro-logical-types=true</code></p>
|
||||
<p><code>.. use-avro-logical-types=false</code></p>
|
||||
<ul>
|
||||
<li>[Optional] If sourceFormat is set to "AVRO", indicates whether to enable interpreting logical types into their corresponding types (ie. TIMESTAMP), instead of only using their raw types (ie. INTEGER).</li>
|
||||
<li>[Optional] If sourceFormat is set to "AVRO", indicates whether to interpret logical types as the corresponding BigQuery data type (for example, TIMESTAMP), instead of using the raw type (for example, INTEGER).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>write-disposition=et</code></p>
|
||||
<p><code>write-disposition=consetetur</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Specifies the action that occurs if the destination table already exists. The following values are supported: WRITE_TRUNCATE: If the table already exists, BigQuery overwrites the table data. WRITE_APPEND: If the table already exists, BigQuery appends the data to the table. WRITE_EMPTY: If the table already exists and contains data, a 'duplicate' error is returned in the job result. The default value is WRITE_APPEND. Each action is atomic and only occurs if BigQuery is able to complete the job successfully. Creation, truncation and append actions occur as one atomic update upon job completion.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..query allow-large-results=false</code></p>
|
||||
<p><code>..query allow-large-results=true</code></p>
|
||||
<ul>
|
||||
<li>[Optional] If true and query uses legacy SQL dialect, allows the query to produce arbitrarily large result tables at a slight cost in performance. Requires destinationTable to be set. For standard SQL queries, this flag is ignored and large results are always allowed. However, you must still set destinationTable when result size exceeds the allowed maximum response size.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>clustering fields=consetetur</code></p>
|
||||
<p><code>clustering fields=est</code></p>
|
||||
<ul>
|
||||
<li>[Repeated] One or more fields on which data should be clustered. Only top-level, non-repeated, simple-type fields are supported. When you cluster a table using multiple columns, the order of columns you specify is important. The order of the specified columns determines the sort order of the data.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. create-disposition=stet</code></p>
|
||||
<p><code>.. create-disposition=aliquyam</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Specifies whether the job is allowed to create new tables. The following values are supported: CREATE_IF_NEEDED: If the table does not exist, BigQuery creates the table. CREATE_NEVER: The table must already exist. If it does not, a 'notFound' error is returned in the job result. The default value is CREATE_IF_NEEDED. Creation, truncation and append actions occur as one atomic update upon job completion.</li>
|
||||
</ul>
|
||||
@@ -937,53 +959,53 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>If true, creates a new session, where session id will be a server generated random id. If false, runs query with an existing session_id passed in ConnectionProperty, otherwise runs query in non-session mode.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>default-dataset dataset-id=elitr</code><ul>
|
||||
<li><code>default-dataset dataset-id=duo</code><ul>
|
||||
<li>[Required] A unique ID for this dataset, without the project name. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 1,024 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>project-id=duo</code></p>
|
||||
<p><code>project-id=diam</code></p>
|
||||
<ul>
|
||||
<li>[Optional] The ID of the project containing this dataset.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..destination-encryption-configuration kms-key-name=diam</code></p>
|
||||
<p><code>..destination-encryption-configuration kms-key-name=est</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Describes the Cloud KMS encryption key that will be used to protect destination BigQuery table. The BigQuery Service Account associated with your project requires access to this encryption key.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..destination-table dataset-id=est</code></p>
|
||||
<p><code>..destination-table dataset-id=sit</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the dataset containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>project-id=sit</code><ul>
|
||||
<li><code>project-id=sed</code><ul>
|
||||
<li>[Required] The ID of the project containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>table-id=sed</code></p>
|
||||
<p><code>table-id=eos</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the table. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 1,024 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. flatten-results=false</code></p>
|
||||
<p><code>.. flatten-results=true</code></p>
|
||||
<ul>
|
||||
<li>[Optional] If true and query uses legacy SQL dialect, flattens all nested and repeated fields in the query results. allowLargeResults must be true if this is set to false. For standard SQL queries, this flag is ignored and results are never flattened.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>maximum-billing-tier=45</code><ul>
|
||||
<li><code>maximum-billing-tier=84</code><ul>
|
||||
<li>[Optional] Limits the billing tier for this job. Queries that have resource usage beyond this tier will fail (without incurring a charge). If unspecified, this will be set to your project default.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>maximum-bytes-billed=ea</code><ul>
|
||||
<li><code>maximum-bytes-billed=stet</code><ul>
|
||||
<li>[Optional] Limits the bytes billed for this job. Queries that will have bytes billed beyond this limit will fail (without incurring a charge). If unspecified, this will be set to your project default.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>parameter-mode=stet</code><ul>
|
||||
<li><code>parameter-mode=dolores</code><ul>
|
||||
<li>Standard SQL only. Set to POSITIONAL to use positional (?) query parameters or to NAMED to use named (@myparam) query parameters in this query.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -1149,7 +1171,15 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>[Output-only] If this is a child job, the id of the parent.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>query billing-tier=97</code><ul>
|
||||
<li>
|
||||
<p><code>query.bi-engine-statistics bi-engine-mode=dolor</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] Specifies which mode of BI Engine acceleration was performed (if any).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. billing-tier=69</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] Billing tier for the job.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -1161,136 +1191,176 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>[Output-only] [Preview] The number of row access policies affected by a DDL statement. Present only for DROP ALL ROW ACCESS POLICIES queries.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>ddl-operation-performed=ipsum</code><ul>
|
||||
<li>The DDL operation performed, possibly dependent on the pre-existence of the DDL target. Possible values (new values might be added in the future): "CREATE": The query created the DDL target. "SKIP": No-op. Example cases: the query is CREATE TABLE IF NOT EXISTS while the table already exists, or the query is DROP TABLE IF EXISTS while the table does not exist. "REPLACE": The query replaced the DDL target. Example case: the query is CREATE OR REPLACE TABLE, and the table already exists. "DROP": The query deleted the DDL target.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>ddl-target-dataset dataset-id=lorem</code><ul>
|
||||
<li>[Required] A unique ID for this dataset, without the project name. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 1,024 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>project-id=accusam</code></p>
|
||||
<ul>
|
||||
<li>[Optional] The ID of the project containing this dataset.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..ddl-target-routine dataset-id=gubergren</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the dataset containing this routine.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>project-id=sadipscing</code><ul>
|
||||
<li>[Required] The ID of the project containing this routine.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>routine-id=at</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the routine. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 256 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..ddl-target-row-access-policy dataset-id=sit</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the dataset containing this row access policy.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>policy-id=duo</code><ul>
|
||||
<li>[Required] The ID of the row access policy. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 256 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>project-id=sit</code><ul>
|
||||
<li>[Required] The ID of the project containing this row access policy.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>table-id=magna</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the table containing this row access policy.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..ddl-target-table dataset-id=et</code></p>
|
||||
<ul>
|
||||
<li><code>ddl-destination-table dataset-id=ipsum</code><ul>
|
||||
<li>[Required] The ID of the dataset containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>project-id=rebum.</code><ul>
|
||||
<li><code>project-id=lorem</code><ul>
|
||||
<li>[Required] The ID of the project containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>table-id=dolor</code></p>
|
||||
<p><code>table-id=accusam</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the table. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 1,024 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. estimated-bytes-processed=lorem</code></p>
|
||||
<p><code>.. ddl-operation-performed=gubergren</code></p>
|
||||
<ul>
|
||||
<li>The DDL operation performed, possibly dependent on the pre-existence of the DDL target. Possible values (new values might be added in the future): "CREATE": The query created the DDL target. "SKIP": No-op. Example cases: the query is CREATE TABLE IF NOT EXISTS while the table already exists, or the query is DROP TABLE IF EXISTS while the table does not exist. "REPLACE": The query replaced the DDL target. Example case: the query is CREATE OR REPLACE TABLE, and the table already exists. "DROP": The query deleted the DDL target.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>ddl-target-dataset dataset-id=sadipscing</code><ul>
|
||||
<li>[Required] A unique ID for this dataset, without the project name. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 1,024 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>project-id=at</code></p>
|
||||
<ul>
|
||||
<li>[Optional] The ID of the project containing this dataset.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..ddl-target-routine dataset-id=sit</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the dataset containing this routine.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>project-id=duo</code><ul>
|
||||
<li>[Required] The ID of the project containing this routine.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>routine-id=sit</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the routine. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 256 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..ddl-target-row-access-policy dataset-id=magna</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the dataset containing this row access policy.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>policy-id=et</code><ul>
|
||||
<li>[Required] The ID of the row access policy. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 256 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>project-id=rebum.</code><ul>
|
||||
<li>[Required] The ID of the project containing this row access policy.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>table-id=dolor</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the table containing this row access policy.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..ddl-target-table dataset-id=lorem</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the dataset containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>project-id=justo</code><ul>
|
||||
<li>[Required] The ID of the project containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>table-id=amet.</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the table. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 1,024 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..dml-stats deleted-row-count=-11</code></p>
|
||||
<ul>
|
||||
<li>Number of deleted Rows. populated by DML DELETE, MERGE and TRUNCATE statements.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>inserted-row-count=-91</code><ul>
|
||||
<li>Number of inserted Rows. Populated by DML INSERT and MERGE statements.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>updated-row-count=-43</code></p>
|
||||
<ul>
|
||||
<li>Number of updated Rows. Populated by DML UPDATE and MERGE statements.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. estimated-bytes-processed=kasd</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] The original estimate of bytes processed for the job.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>model-training current-iteration=30</code><ul>
|
||||
<li>
|
||||
<p><code>ml-statistics max-iterations=lorem</code></p>
|
||||
<ul>
|
||||
<li>Maximum number of iterations specified as max_iterations in the 'CREATE MODEL' query. The actual number of iterations may be less than this number due to early stop.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..model-training current-iteration=43</code></p>
|
||||
<ul>
|
||||
<li>[Output-only, Beta] Index of current ML training iteration. Updated during create model query job to show job progress.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>expected-total-iterations=amet.</code></p>
|
||||
<p><code>expected-total-iterations=nonumy</code></p>
|
||||
<ul>
|
||||
<li>[Output-only, Beta] Expected number of iterations for the create model query job specified as num_iterations in the input query. The actual total number of iterations may be less than this number due to early stop.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. model-training-current-iteration=90</code></p>
|
||||
<p><code>.. model-training-current-iteration=35</code></p>
|
||||
<ul>
|
||||
<li>[Output-only, Beta] Deprecated; do not use.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>model-training-expected-total-iteration=nonumy</code><ul>
|
||||
<li><code>model-training-expected-total-iteration=tempor</code><ul>
|
||||
<li>[Output-only, Beta] Deprecated; do not use.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>num-dml-affected-rows=sed</code><ul>
|
||||
<li><code>num-dml-affected-rows=dolore</code><ul>
|
||||
<li>[Output-only] The number of rows affected by a DML statement. Present only for DML statements INSERT, UPDATE or DELETE.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>statement-type=kasd</code><ul>
|
||||
<li><code>statement-type=eos</code><ul>
|
||||
<li>The type of query statement, if valid. Possible values (new values might be added in the future): "SELECT": SELECT query. "INSERT": INSERT query; see https://cloud.google.com/bigquery/docs/reference/standard-sql/data-manipulation-language. "UPDATE": UPDATE query; see https://cloud.google.com/bigquery/docs/reference/standard-sql/data-manipulation-language. "DELETE": DELETE query; see https://cloud.google.com/bigquery/docs/reference/standard-sql/data-manipulation-language. "MERGE": MERGE query; see https://cloud.google.com/bigquery/docs/reference/standard-sql/data-manipulation-language. "ALTER_TABLE": ALTER TABLE query. "ALTER_VIEW": ALTER VIEW query. "ASSERT": ASSERT condition AS 'description'. "CREATE_FUNCTION": CREATE FUNCTION query. "CREATE_MODEL": CREATE [OR REPLACE] MODEL ... AS SELECT ... . "CREATE_PROCEDURE": CREATE PROCEDURE query. "CREATE_TABLE": CREATE [OR REPLACE] TABLE without AS SELECT. "CREATE_TABLE_AS_SELECT": CREATE [OR REPLACE] TABLE ... AS SELECT ... . "CREATE_VIEW": CREATE [OR REPLACE] VIEW ... AS SELECT ... . "DROP_FUNCTION" : DROP FUNCTION query. "DROP_PROCEDURE": DROP PROCEDURE query. "DROP_TABLE": DROP TABLE query. "DROP_VIEW": DROP VIEW query.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>total-bytes-billed=lorem</code><ul>
|
||||
<li><code>total-bytes-billed=amet.</code><ul>
|
||||
<li>[Output-only] Total bytes billed for the job.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>total-bytes-processed=sanctus</code><ul>
|
||||
<li><code>total-bytes-processed=dolore</code><ul>
|
||||
<li>[Output-only] Total bytes processed for the job.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>total-bytes-processed-accuracy=nonumy</code><ul>
|
||||
<li><code>total-bytes-processed-accuracy=amet</code><ul>
|
||||
<li>[Output-only] For dry-run jobs, totalBytesProcessed is an estimate and this field specifies the accuracy of the estimate. Possible values can be: UNKNOWN: accuracy of the estimate is unknown. PRECISE: estimate is precise. LOWER_BOUND: estimate is lower bound of what the query would cost. UPPER_BOUND: estimate is upper bound of what the query would cost.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>total-partitions-processed=rebum.</code><ul>
|
||||
<li><code>total-partitions-processed=ut</code><ul>
|
||||
<li>[Output-only] Total number of partitions processed from all partitioned tables referenced in the job.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>total-slot-ms=tempor</code></p>
|
||||
<p><code>total-slot-ms=at</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] Slot-milliseconds for the job.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. quota-deferments=dolore</code></p>
|
||||
<p><code>.. quota-deferments=sit</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] Quotas which delayed this job's start time.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>reservation-id=eos</code><ul>
|
||||
<li><code>reservation-id=vero</code><ul>
|
||||
<li>[Output-only] Name of the primary reservation assigned to this job. Note that this could be different than reservations reported in the reservation usage field if parent reservations were used to execute this job.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -1301,65 +1371,65 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..script-statistics evaluation-kind=dolore</code></p>
|
||||
<p><code>..script-statistics evaluation-kind=ut</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] Whether this child job was a statement or expression.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..session-info-template session-id=amet</code></p>
|
||||
<p><code>..session-info session-id=rebum.</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] // [Preview] Id of the session.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. start-time=ut</code></p>
|
||||
<p><code>.. start-time=duo</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] Start time of this job, in milliseconds since the epoch. This field will be present when the job transitions from the PENDING state to either RUNNING or DONE.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>total-bytes-processed=at</code><ul>
|
||||
<li><code>total-bytes-processed=kasd</code><ul>
|
||||
<li>[Output-only] [Deprecated] Use the bytes processed in the query statistics instead.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>total-slot-ms=sit</code><ul>
|
||||
<li><code>total-slot-ms=sadipscing</code><ul>
|
||||
<li>[Output-only] Slot-milliseconds for the job.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>transaction-info-template transaction-id=vero</code></p>
|
||||
<p><code>transaction-info transaction-id=tempor</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] // [Alpha] Id of the transaction.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>...status.error-result debug-info=duo</code></p>
|
||||
<p><code>...status.error-result debug-info=sea</code></p>
|
||||
<ul>
|
||||
<li>Debugging information. This property is internal to Google and should not be used.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>location=sadipscing</code><ul>
|
||||
<li><code>location=et</code><ul>
|
||||
<li>Specifies where the error occurred, if present.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>message=ut</code><ul>
|
||||
<li><code>message=lorem</code><ul>
|
||||
<li>A human-readable description of the error.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>reason=rebum.</code></p>
|
||||
<p><code>reason=magna</code></p>
|
||||
<ul>
|
||||
<li>A short error code that summarizes the error.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. state=duo</code></p>
|
||||
<p><code>.. state=takimata</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] Running state of the job.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. user-email=kasd</code></p>
|
||||
<p><code>.. user-email=rebum.</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] Email address of the user who ran the job.</li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>List - bigquery v2.0.4+20210327</title>
|
||||
<title>List - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -341,11 +341,10 @@
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery.readonly</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform.read-only</em></li>
|
||||
</ul>
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery.readonly</em>.
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery</em>.
|
||||
You can set the scope for this method like this: <code>bigquery2 --scope <scope> jobs list ...</code></p>
|
||||
<h1 id="required-scalar-argument">Required Scalar Argument</h1>
|
||||
<ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Query - bigquery v2.0.4+20210327</title>
|
||||
<title>Query - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -343,7 +343,6 @@
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery.readonly</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform.read-only</em></li>
|
||||
</ul>
|
||||
@@ -387,12 +386,12 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>If true, creates a new session, where session id will be a server generated random id. If false, runs query with an existing session_id passed in ConnectionProperty, otherwise runs query in non-session mode.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>default-dataset dataset-id=tempor</code><ul>
|
||||
<li><code>default-dataset dataset-id=clita</code><ul>
|
||||
<li>[Required] A unique ID for this dataset, without the project name. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 1,024 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>project-id=sea</code></p>
|
||||
<p><code>project-id=stet</code></p>
|
||||
<ul>
|
||||
<li>[Optional] The ID of the project containing this dataset.</li>
|
||||
</ul>
|
||||
@@ -403,44 +402,44 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>[Optional] If set to true, BigQuery doesn't run the job. Instead, if the query is valid, BigQuery returns statistics about the job such as how many bytes would be processed. If the query is invalid, an error returns. The default value is false.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>kind=lorem</code><ul>
|
||||
<li><code>kind=ut</code><ul>
|
||||
<li>The resource type of the request.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>labels=key=magna</code><ul>
|
||||
<li><code>labels=key=sit</code><ul>
|
||||
<li>The labels associated with this job. You can use these to organize and group your jobs. Label keys and values can be no longer than 63 characters, can only contain lowercase letters, numeric characters, underscores and dashes. International characters are allowed. Label values are optional. Label keys must start with a letter and each label in the list must have a different key.</li>
|
||||
<li>the value will be associated with the given <code>key</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>location=takimata</code><ul>
|
||||
<li><code>location=vero</code><ul>
|
||||
<li>The geographic location where the job should run. See details at https://cloud.google.com/bigquery/docs/locations#specifying_your_location.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>max-results=35</code><ul>
|
||||
<li><code>max-results=85</code><ul>
|
||||
<li>[Optional] The maximum number of rows of data to return per page of results. Setting this flag to a small value such as 1000 and then paging through results might improve reliability when the query result set is large. In addition to this limit, responses are also limited to 10 MB. By default, there is no maximum row count, and only the byte limit applies.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>maximum-bytes-billed=at</code><ul>
|
||||
<li><code>maximum-bytes-billed=dolores</code><ul>
|
||||
<li>[Optional] Limits the bytes billed for this job. Queries that will have bytes billed beyond this limit will fail (without incurring a charge). If unspecified, this will be set to your project default.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>parameter-mode=invidunt</code><ul>
|
||||
<li><code>parameter-mode=consetetur</code><ul>
|
||||
<li>Standard SQL only. Set to POSITIONAL to use positional (?) query parameters or to NAMED to use named (@myparam) query parameters in this query.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>preserve-nulls=false</code><ul>
|
||||
<li><code>preserve-nulls=true</code><ul>
|
||||
<li>[Deprecated] This property is deprecated.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>query=ut</code><ul>
|
||||
<li><code>query=clita</code><ul>
|
||||
<li>[Required] A query string, following the BigQuery query syntax, of the query to execute. Example: "SELECT count(f1) FROM [myProjectId:myDatasetId.myTableId]".</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>request-id=sit</code><ul>
|
||||
<li><code>request-id=dolor</code><ul>
|
||||
<li>A unique user provided identifier to ensure idempotent behavior for queries. Note that this is different from the job_id. It has the following properties: 1. It is case-sensitive, limited to up to 36 ASCII characters. A UUID is recommended. 2. Read only queries can ignore this token since they are nullipotent by definition. 3. For the purposes of idempotency ensured by the request_id, a request is considered duplicate of another only if they have the same request_id and are actually duplicates. When determining whether a request is a duplicate of the previous request, all parameters in the request that may affect the behavior are considered. For example, query, connection_properties, query_parameters, use_legacy_sql are parameters that affect the result and are considered when determining whether a request is a duplicate, but properties like timeout_ms don't affect the result and are thus not considered. Dry run query requests are never considered duplicate of another request. 4. When a duplicate mutating query request is detected, it returns: a. the results of the mutation if it completes successfully within the timeout. b. the running operation if it is still in progress at the end of the timeout. 5. Its lifetime is limited to 15 minutes. In other words, if two requests are sent with the same request_id, but more than 15 minutes apart, idempotency is not guaranteed.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>timeout-ms=75</code><ul>
|
||||
<li><code>timeout-ms=19</code><ul>
|
||||
<li>[Optional] How long to wait for the query to complete, in milliseconds, before the request times out and returns. Note that this is only a timeout for the request, not the query. If the query takes longer to run than the timeout value, the call returns without any results and with the 'jobComplete' flag set to false. You can call GetQueryResults() to wait for the query to complete and read the results. The default value is 10000 milliseconds (10 seconds).</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Delete - bigquery v2.0.4+20210327</title>
|
||||
<title>Delete - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Get - bigquery v2.0.4+20210327</title>
|
||||
<title>Get - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -338,11 +338,10 @@
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery.readonly</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform.read-only</em></li>
|
||||
</ul>
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery.readonly</em>.
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery</em>.
|
||||
You can set the scope for this method like this: <code>bigquery2 --scope <scope> models get ...</code></p>
|
||||
<h1 id="required-scalar-arguments">Required Scalar Arguments</h1>
|
||||
<ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>List - bigquery v2.0.4+20210327</title>
|
||||
<title>List - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -336,16 +336,15 @@
|
||||
</div>
|
||||
<div role="main">
|
||||
<div class="section">
|
||||
<p>Lists all models in the specified dataset. Requires the READER dataset role.</p>
|
||||
<p>Lists all models in the specified dataset. Requires the READER dataset role. After retrieving the list of models, you can get information about a particular model by calling the models.get method.</p>
|
||||
<h1 id="scopes">Scopes</h1>
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery.readonly</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform.read-only</em></li>
|
||||
</ul>
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery.readonly</em>.
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery</em>.
|
||||
You can set the scope for this method like this: <code>bigquery2 --scope <scope> models list ...</code></p>
|
||||
<h1 id="required-scalar-arguments">Required Scalar Arguments</h1>
|
||||
<ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Patch - bigquery v2.0.4+20210327</title>
|
||||
<title>Patch - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -388,67 +388,67 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r . best-trial-id=clita</code><ul>
|
||||
<li><code>-r . best-trial-id=nonumy</code><ul>
|
||||
<li>The best trial_id across all training runs.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>creation-time=dolor</code><ul>
|
||||
<li><code>creation-time=et</code><ul>
|
||||
<li>Output only. The time when this model was created, in millisecs since the epoch.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>description=aliquyam</code><ul>
|
||||
<li><code>description=sanctus</code><ul>
|
||||
<li>Optional. A user-friendly description of this model.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>encryption-configuration kms-key-name=magna</code></p>
|
||||
<p><code>encryption-configuration kms-key-name=accusam</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Describes the Cloud KMS encryption key that will be used to protect destination BigQuery table. The BigQuery Service Account associated with your project requires access to this encryption key.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. etag=diam</code></p>
|
||||
<p><code>.. etag=tempor</code></p>
|
||||
<ul>
|
||||
<li>Output only. A hash of this resource.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>expiration-time=nonumy</code><ul>
|
||||
<li><code>expiration-time=sed</code><ul>
|
||||
<li>Optional. The time when this model expires, in milliseconds since the epoch. If not present, the model will persist indefinitely. Expired models will be deleted and their storage reclaimed. The defaultTableExpirationMs property of the encapsulating dataset can be used to set a default expirationTime on newly created models.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>friendly-name=et</code><ul>
|
||||
<li><code>friendly-name=est</code><ul>
|
||||
<li>Optional. A descriptive name for this model.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>labels=key=sanctus</code><ul>
|
||||
<li><code>labels=key=takimata</code><ul>
|
||||
<li>The labels associated with this model. You can use these to organize and group your models. Label keys and values can be no longer than 63 characters, can only contain lowercase letters, numeric characters, underscores and dashes. International characters are allowed. Label values are optional. Label keys must start with a letter and each label in the list must have a different key.</li>
|
||||
<li>the value will be associated with the given <code>key</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>last-modified-time=accusam</code><ul>
|
||||
<li><code>last-modified-time=dolor</code><ul>
|
||||
<li>Output only. The time when this model was last modified, in millisecs since the epoch.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>location=tempor</code><ul>
|
||||
<li><code>location=diam</code><ul>
|
||||
<li>Output only. The geographic location where the model resides. This value is inherited from the dataset.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>model-reference dataset-id=sed</code><ul>
|
||||
<li><code>model-reference dataset-id=at</code><ul>
|
||||
<li>[Required] The ID of the dataset containing this model.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>model-id=est</code><ul>
|
||||
<li><code>model-id=erat</code><ul>
|
||||
<li>[Required] The ID of the model. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 1,024 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>project-id=takimata</code></p>
|
||||
<p><code>project-id=justo</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the project containing this model.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. model-type=dolor</code></p>
|
||||
<p><code>.. model-type=ipsum</code></p>
|
||||
<ul>
|
||||
<li>Output only. Type of the model resource.</li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Get Service Account - bigquery v2.0.4+20210327</title>
|
||||
<title>Get Service Account - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -338,11 +338,10 @@
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery.readonly</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform.read-only</em></li>
|
||||
</ul>
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery.readonly</em>.
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery</em>.
|
||||
You can set the scope for this method like this: <code>bigquery2 --scope <scope> projects get-service-account ...</code></p>
|
||||
<h1 id="required-scalar-argument">Required Scalar Argument</h1>
|
||||
<ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>List - bigquery v2.0.4+20210327</title>
|
||||
<title>List - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -338,11 +338,10 @@
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery.readonly</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform.read-only</em></li>
|
||||
</ul>
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery.readonly</em>.
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery</em>.
|
||||
You can set the scope for this method like this: <code>bigquery2 --scope <scope> projects list ...</code></p>
|
||||
<h1 id="optional-output-flags">Optional Output Flags</h1>
|
||||
<p>The method's return value a JSON encoded structure, which will be written to standard output by default.</p>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Delete - bigquery v2.0.4+20210327</title>
|
||||
<title>Delete - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Get - bigquery v2.0.4+20210327</title>
|
||||
<title>Get - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -341,11 +341,10 @@
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery.readonly</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform.read-only</em></li>
|
||||
</ul>
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery.readonly</em>.
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery</em>.
|
||||
You can set the scope for this method like this: <code>bigquery2 --scope <scope> routines get ...</code></p>
|
||||
<h1 id="required-scalar-arguments">Required Scalar Arguments</h1>
|
||||
<ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Insert - bigquery v2.0.4+20210327</title>
|
||||
<title>Insert - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -378,72 +378,77 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
project-id: string
|
||||
routine-id: string
|
||||
routine-type: string
|
||||
strict-mode: boolean
|
||||
|
||||
</code></pre>
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r . creation-time=diam</code><ul>
|
||||
<li><code>-r . creation-time=accusam</code><ul>
|
||||
<li>Output only. The time when this routine was created, in milliseconds since the epoch.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>definition-body=at</code><ul>
|
||||
<li><code>definition-body=dolores</code><ul>
|
||||
<li>Required. The body of the routine. For functions, this is the expression in the AS clause. If language=SQL, it is the substring inside (but excluding) the parentheses. For example, for the function created with the following statement: <code>CREATE FUNCTION JoinLines(x string, y string) as (concat(x, &#34;\n&#34;, y))</code> The definition_body is <code>concat(x, &#34;\n&#34;, y)</code> (\n is not replaced with linebreak). If language=JAVASCRIPT, it is the evaluated string in the AS clause. For example, for the function created with the following statement: <code>CREATE FUNCTION f() RETURNS STRING LANGUAGE js AS &#39;return &#34;\n&#34;;\n&#39;</code> The definition_body is <code>return &#34;\n&#34;;\n</code> Note that both \n are replaced with linebreaks.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>description=erat</code><ul>
|
||||
<li>Optional. [Experimental] The description of the routine if defined.</li>
|
||||
<li><code>description=consetetur</code><ul>
|
||||
<li>Optional. The description of the routine, if defined.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>determinism-level=justo</code><ul>
|
||||
<li>Optional. [Experimental] The determinism level of the JavaScript UDF if defined.</li>
|
||||
<li><code>determinism-level=no</code><ul>
|
||||
<li>Optional. The determinism level of the JavaScript UDF, if defined.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>etag=ipsum</code><ul>
|
||||
<li><code>etag=justo</code><ul>
|
||||
<li>Output only. A hash of this resource.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>imported-libraries=accusam</code><ul>
|
||||
<li><code>imported-libraries=sadipscing</code><ul>
|
||||
<li>Optional. If language = "JAVASCRIPT", this field stores the path of the imported JAVASCRIPT libraries.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>language=dolores</code><ul>
|
||||
<li><code>language=diam</code><ul>
|
||||
<li>Optional. Defaults to "SQL".</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>last-modified-time=consetetur</code><ul>
|
||||
<li><code>last-modified-time=sea</code><ul>
|
||||
<li>Output only. The time when this routine was last modified, in milliseconds since the epoch.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>return-type type-kind=no</code></p>
|
||||
<p><code>return-type type-kind=ipsum</code></p>
|
||||
<ul>
|
||||
<li>Required. The top level type of this field. Can be any standard SQL data type (e.g., "INT64", "DATE", "ARRAY").</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..routine-reference dataset-id=justo</code></p>
|
||||
<p><code>..routine-reference dataset-id=stet</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the dataset containing this routine.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>project-id=sadipscing</code><ul>
|
||||
<li><code>project-id=gubergren</code><ul>
|
||||
<li>[Required] The ID of the project containing this routine.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>routine-id=diam</code></p>
|
||||
<p><code>routine-id=ipsum</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the routine. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 256 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. routine-type=sea</code></p>
|
||||
<p><code>.. routine-type=no</code></p>
|
||||
<ul>
|
||||
<li>Required. The type of routine.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>strict-mode=false</code><ul>
|
||||
<li>Optional. Can be set for procedures only. If true (default), the definition body will be validated in the creation and the updates of the procedure. For procedures with an argument of ANY TYPE, the definition body validtion is not supported at creation/update time, and thus this field must be set to false explicitly.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<h3 id="about-cursors">About Cursors</h3>
|
||||
<p>The cursor position is key to comfortably set complex nested structures. The following rules apply:</p>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>List - bigquery v2.0.4+20210327</title>
|
||||
<title>List - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -341,11 +341,10 @@
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery.readonly</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform.read-only</em></li>
|
||||
</ul>
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery.readonly</em>.
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery</em>.
|
||||
You can set the scope for this method like this: <code>bigquery2 --scope <scope> routines list ...</code></p>
|
||||
<h1 id="required-scalar-arguments">Required Scalar Arguments</h1>
|
||||
<ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Update - bigquery v2.0.4+20210327</title>
|
||||
<title>Update - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -382,72 +382,77 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
project-id: string
|
||||
routine-id: string
|
||||
routine-type: string
|
||||
strict-mode: boolean
|
||||
|
||||
</code></pre>
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r . creation-time=ipsum</code><ul>
|
||||
<li><code>-r . creation-time=kasd</code><ul>
|
||||
<li>Output only. The time when this routine was created, in milliseconds since the epoch.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>definition-body=stet</code><ul>
|
||||
<li><code>definition-body=amet</code><ul>
|
||||
<li>Required. The body of the routine. For functions, this is the expression in the AS clause. If language=SQL, it is the substring inside (but excluding) the parentheses. For example, for the function created with the following statement: <code>CREATE FUNCTION JoinLines(x string, y string) as (concat(x, &#34;\n&#34;, y))</code> The definition_body is <code>concat(x, &#34;\n&#34;, y)</code> (\n is not replaced with linebreak). If language=JAVASCRIPT, it is the evaluated string in the AS clause. For example, for the function created with the following statement: <code>CREATE FUNCTION f() RETURNS STRING LANGUAGE js AS &#39;return &#34;\n&#34;;\n&#39;</code> The definition_body is <code>return &#34;\n&#34;;\n</code> Note that both \n are replaced with linebreaks.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>description=gubergren</code><ul>
|
||||
<li>Optional. [Experimental] The description of the routine if defined.</li>
|
||||
<li><code>description=lorem</code><ul>
|
||||
<li>Optional. The description of the routine, if defined.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>determinism-level=ipsum</code><ul>
|
||||
<li>Optional. [Experimental] The determinism level of the JavaScript UDF if defined.</li>
|
||||
<li><code>determinism-level=justo</code><ul>
|
||||
<li>Optional. The determinism level of the JavaScript UDF, if defined.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>etag=no</code><ul>
|
||||
<li><code>etag=invidunt</code><ul>
|
||||
<li>Output only. A hash of this resource.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>imported-libraries=sit</code><ul>
|
||||
<li><code>imported-libraries=sed</code><ul>
|
||||
<li>Optional. If language = "JAVASCRIPT", this field stores the path of the imported JAVASCRIPT libraries.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>language=kasd</code><ul>
|
||||
<li><code>language=nonumy</code><ul>
|
||||
<li>Optional. Defaults to "SQL".</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>last-modified-time=amet</code><ul>
|
||||
<li><code>last-modified-time=sea</code><ul>
|
||||
<li>Output only. The time when this routine was last modified, in milliseconds since the epoch.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>return-type type-kind=lorem</code></p>
|
||||
<p><code>return-type type-kind=ipsum</code></p>
|
||||
<ul>
|
||||
<li>Required. The top level type of this field. Can be any standard SQL data type (e.g., "INT64", "DATE", "ARRAY").</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..routine-reference dataset-id=justo</code></p>
|
||||
<p><code>..routine-reference dataset-id=kasd</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the dataset containing this routine.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>project-id=invidunt</code><ul>
|
||||
<li><code>project-id=justo</code><ul>
|
||||
<li>[Required] The ID of the project containing this routine.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>routine-id=sed</code></p>
|
||||
<p><code>routine-id=ea</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the routine. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 256 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. routine-type=nonumy</code></p>
|
||||
<p><code>.. routine-type=at</code></p>
|
||||
<ul>
|
||||
<li>Required. The type of routine.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>strict-mode=false</code><ul>
|
||||
<li>Optional. Can be set for procedures only. If true (default), the definition body will be validated in the creation and the updates of the procedure. For procedures with an argument of ANY TYPE, the definition body validtion is not supported at creation/update time, and thus this field must be set to false explicitly.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<h3 id="about-cursors">About Cursors</h3>
|
||||
<p>The cursor position is key to comfortably set complex nested structures. The following rules apply:</p>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Get Iam Policy - bigquery v2.0.4+20210327</title>
|
||||
<title>Get Iam Policy - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -343,7 +343,6 @@
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery.readonly</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform.read-only</em></li>
|
||||
</ul>
|
||||
@@ -368,8 +367,8 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r .options requested-policy-version=91</code><ul>
|
||||
<li>Optional. The policy format version to be returned. Valid values are 0, 1, and 3. Requests specifying an invalid value will be rejected. Requests for policies with any conditional bindings must specify version 3. Policies without any conditional bindings may specify any valid value or leave the field unset. To learn which resources support conditions in their IAM policies, see the <a href="https://cloud.google.com/iam/help/conditions/resource-policies">IAM documentation</a>.</li>
|
||||
<li><code>-r .options requested-policy-version=87</code><ul>
|
||||
<li>Optional. The maximum policy version that will be used to format the policy. Valid values are 0, 1, and 3. Requests specifying an invalid value will be rejected. Requests for policies with any conditional role bindings must specify version 3. Policies with no conditional role bindings may specify any valid value or leave the field unset. The policy in the response might use the policy version that you specified, or it might use a lower policy version. For example, if you specify version 3, but the policy has no conditional role bindings, the response uses version 1. To learn which resources support conditions in their IAM policies, see the <a href="https://cloud.google.com/iam/help/conditions/resource-policies">IAM documentation</a>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>List - bigquery v2.0.4+20210327</title>
|
||||
<title>List - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -341,11 +341,10 @@
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery.readonly</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform.read-only</em></li>
|
||||
</ul>
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery.readonly</em>.
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery</em>.
|
||||
You can set the scope for this method like this: <code>bigquery2 --scope <scope> row-access-policies list ...</code></p>
|
||||
<h1 id="required-scalar-arguments">Required Scalar Arguments</h1>
|
||||
<ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Set Iam Policy - bigquery v2.0.4+20210327</title>
|
||||
<title>Set Iam Policy - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -368,18 +368,18 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r .policy etag=ipsum</code><ul>
|
||||
<li><code>-r .policy etag=vero</code><ul>
|
||||
<li><code>etag</code> is used for optimistic concurrency control as a way to help prevent simultaneous updates of a policy from overwriting each other. It is strongly suggested that systems make use of the <code>etag</code> in the read-modify-write cycle to perform policy updates in order to avoid race conditions: An <code>etag</code> is returned in the response to <code>getIamPolicy</code>, and systems are expected to put that etag in the request to <code>setIamPolicy</code> to ensure that their change will be applied to the same version of the policy. <strong>Important:</strong> If you use IAM Conditions, you must include the <code>etag</code> field whenever you call <code>setIamPolicy</code>. If you omit this field, then IAM allows you to overwrite a version <code>3</code> policy with a version <code>1</code> policy, and all of the conditions in the version <code>3</code> policy are lost.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>version=38</code></p>
|
||||
<p><code>version=13</code></p>
|
||||
<ul>
|
||||
<li>Specifies the format of the policy. Valid values are <code>0</code>, <code>1</code>, and <code>3</code>. Requests that specify an invalid value are rejected. Any operation that affects conditional role bindings must specify version <code>3</code>. This requirement applies to the following operations: * Getting a policy that includes a conditional role binding * Adding a conditional role binding to a policy * Changing a conditional role binding in a policy * Removing any role binding, with or without a condition, from a policy that includes conditions <strong>Important:</strong> If you use IAM Conditions, you must include the <code>etag</code> field whenever you call <code>setIamPolicy</code>. If you omit this field, then IAM allows you to overwrite a version <code>3</code> policy with a version <code>1</code> policy, and all of the conditions in the version <code>3</code> policy are lost. If a policy does not include any conditions, operations on that policy may specify any valid version or leave the field unset. To learn which resources support conditions in their IAM policies, see the <a href="https://cloud.google.com/iam/help/conditions/resource-policies">IAM documentation</a>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. update-mask=justo</code></p>
|
||||
<p><code>.. update-mask=nonumy</code></p>
|
||||
<ul>
|
||||
<li>OPTIONAL: A FieldMask specifying which fields of the policy to modify. Only the fields in the mask will be modified. If no mask is provided, the following default mask is used: <code>paths: &#34;bindings, etag&#34;</code></li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Test Iam Permissions - bigquery v2.0.4+20210327</title>
|
||||
<title>Test Iam Permissions - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -343,7 +343,6 @@
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery.readonly</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform.read-only</em></li>
|
||||
</ul>
|
||||
@@ -367,7 +366,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r . permissions=ea</code><ul>
|
||||
<li><code>-r . permissions=erat</code><ul>
|
||||
<li>The set of permissions to check for the <code>resource</code>. Permissions with wildcards (such as '<em>' or 'storage.</em>') are not allowed. For more information see <a href="https://cloud.google.com/iam/docs/overview#permissions">IAM Overview</a>.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Insert All - bigquery v2.0.4+20210327</title>
|
||||
<title>Insert All - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -377,11 +377,11 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r . ignore-unknown-values=false</code><ul>
|
||||
<li><code>-r . ignore-unknown-values=true</code><ul>
|
||||
<li>[Optional] Accept rows that contain values that do not match the schema. The unknown values are ignored. Default is false, which treats unknown values as errors.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>kind=erat</code><ul>
|
||||
<li><code>kind=voluptua.</code><ul>
|
||||
<li>The resource type of the response.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -389,7 +389,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>[Optional] Insert all valid rows of a request, even if invalid rows exist. The default value is false, which causes the entire request to fail if any invalid rows exist.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>template-suffix=invidunt</code><ul>
|
||||
<li><code>template-suffix=elitr</code><ul>
|
||||
<li>If specified, treats the destination table as a base template, and inserts the rows into an instance table named "{destination}{templateSuffix}". BigQuery will manage creation of the instance table, using the schema of the base template table. See https://cloud.google.com/bigquery/streaming-data-into-bigquery#template-tables for considerations when working with templates tables.</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>List - bigquery v2.0.4+20210327</title>
|
||||
<title>List - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -341,11 +341,10 @@
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery.readonly</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform.read-only</em></li>
|
||||
</ul>
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery.readonly</em>.
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery</em>.
|
||||
You can set the scope for this method like this: <code>bigquery2 --scope <scope> tabledata list ...</code></p>
|
||||
<h1 id="required-scalar-arguments">Required Scalar Arguments</h1>
|
||||
<ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Delete - bigquery v2.0.4+20210327</title>
|
||||
<title>Delete - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Get Iam Policy - bigquery v2.0.4+20210327</title>
|
||||
<title>Get Iam Policy - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -343,7 +343,6 @@
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery.readonly</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform.read-only</em></li>
|
||||
</ul>
|
||||
@@ -368,8 +367,8 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r .options requested-policy-version=10</code><ul>
|
||||
<li>Optional. The policy format version to be returned. Valid values are 0, 1, and 3. Requests specifying an invalid value will be rejected. Requests for policies with any conditional bindings must specify version 3. Policies without any conditional bindings may specify any valid value or leave the field unset. To learn which resources support conditions in their IAM policies, see the <a href="https://cloud.google.com/iam/help/conditions/resource-policies">IAM documentation</a>.</li>
|
||||
<li><code>-r .options requested-policy-version=55</code><ul>
|
||||
<li>Optional. The maximum policy version that will be used to format the policy. Valid values are 0, 1, and 3. Requests specifying an invalid value will be rejected. Requests for policies with any conditional role bindings must specify version 3. Policies with no conditional role bindings may specify any valid value or leave the field unset. The policy in the response might use the policy version that you specified, or it might use a lower policy version. For example, if you specify version 3, but the policy has no conditional role bindings, the response uses version 1. To learn which resources support conditions in their IAM policies, see the <a href="https://cloud.google.com/iam/help/conditions/resource-policies">IAM documentation</a>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Get - bigquery v2.0.4+20210327</title>
|
||||
<title>Get - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -341,11 +341,10 @@
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery.readonly</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform.read-only</em></li>
|
||||
</ul>
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery.readonly</em>.
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery</em>.
|
||||
You can set the scope for this method like this: <code>bigquery2 --scope <scope> tables get ...</code></p>
|
||||
<h1 id="required-scalar-arguments">Required Scalar Arguments</h1>
|
||||
<ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Insert - bigquery v2.0.4+20210327</title>
|
||||
<title>Insert - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -366,6 +366,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
clustering:
|
||||
fields: [string]
|
||||
creation-time: string
|
||||
default-collation: string
|
||||
description: string
|
||||
encryption-configuration:
|
||||
kms-key-name: string
|
||||
@@ -373,6 +374,8 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
expiration-time: string
|
||||
external-data-configuration:
|
||||
autodetect: boolean
|
||||
avro-options:
|
||||
use-avro-logical-types: boolean
|
||||
bigtable-options:
|
||||
ignore-unspecified-column-families: boolean
|
||||
read-rowkey-as-string: boolean
|
||||
@@ -383,8 +386,10 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
allow-quoted-newlines: boolean
|
||||
encoding: string
|
||||
field-delimiter: string
|
||||
null-marker: string
|
||||
quote: string
|
||||
skip-leading-rows: string
|
||||
decimal-target-types: [string]
|
||||
google-sheets-options:
|
||||
range: string
|
||||
skip-leading-rows: string
|
||||
@@ -449,6 +454,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
type: string
|
||||
view:
|
||||
query: string
|
||||
use-explicit-column-names: boolean
|
||||
use-legacy-sql: boolean
|
||||
|
||||
</code></pre>
|
||||
@@ -456,35 +462,39 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><code>-r .clustering fields=erat</code></p>
|
||||
<p><code>-r .clustering fields=et</code></p>
|
||||
<ul>
|
||||
<li>[Repeated] One or more fields on which data should be clustered. Only top-level, non-repeated, simple-type fields are supported. When you cluster a table using multiple columns, the order of columns you specify is important. The order of the specified columns determines the sort order of the data.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. creation-time=erat</code></p>
|
||||
<p><code>.. creation-time=clita</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] The time when this table was created, in milliseconds since the epoch.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>description=dolores</code><ul>
|
||||
<li><code>default-collation=sit</code><ul>
|
||||
<li>[Output-only] The default collation of the table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>description=takimata</code><ul>
|
||||
<li>[Optional] A user-friendly description of this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>encryption-configuration kms-key-name=ipsum</code></p>
|
||||
<p><code>encryption-configuration kms-key-name=erat</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Describes the Cloud KMS encryption key that will be used to protect destination BigQuery table. The BigQuery Service Account associated with your project requires access to this encryption key.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. etag=voluptua.</code></p>
|
||||
<p><code>.. etag=diam</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] A hash of the table metadata. Used to ensure there were no concurrent modifications to the resource when attempting an update. Not guaranteed to change when the table contents or the fields numRows, numBytes, numLongTermBytes or lastModifiedTime change.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>expiration-time=eos</code><ul>
|
||||
<li><code>expiration-time=nonumy</code><ul>
|
||||
<li>[Optional] The time when this table expires, in milliseconds since the epoch. If not present, the table will persist indefinitely. Expired tables will be deleted and their storage reclaimed. The defaultTableExpirationMs property of the encapsulating dataset can be used to set a default expirationTime on newly created tables.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -492,12 +502,20 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>Try to detect schema and format options automatically. Any option specified explicitly will be honored.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>bigtable-options ignore-unspecified-column-families=false</code><ul>
|
||||
<li>
|
||||
<p><code>avro-options use-avro-logical-types=false</code></p>
|
||||
<ul>
|
||||
<li>[Optional] If sourceFormat is set to "AVRO", indicates whether to interpret logical types as the corresponding BigQuery data type (for example, TIMESTAMP), instead of using the raw type (for example, INTEGER).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..bigtable-options ignore-unspecified-column-families=false</code></p>
|
||||
<ul>
|
||||
<li>[Optional] If field is true, then the column families that are not specified in columnFamilies list are not exposed in the table schema. Otherwise, they are read with BYTES type values. The default value is false.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>read-rowkey-as-string=true</code></p>
|
||||
<p><code>read-rowkey-as-string=false</code></p>
|
||||
<ul>
|
||||
<li>[Optional] If field is true, then the rowkey column families will be read and converted to string. Otherwise they are read with BYTES type values and users need to manually cast them with CAST if necessary. The default value is false.</li>
|
||||
</ul>
|
||||
@@ -508,11 +526,11 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>[Optional] The compression type of the data source. Possible values include GZIP and NONE. The default value is NONE. This setting is ignored for Google Cloud Bigtable, Google Cloud Datastore backups and Avro formats.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>connection-id=clita</code><ul>
|
||||
<li><code>connection-id=ea</code><ul>
|
||||
<li>[Optional, Trusted Tester] Connection for external data source.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>csv-options allow-jagged-rows=true</code><ul>
|
||||
<li><code>csv-options allow-jagged-rows=false</code><ul>
|
||||
<li>[Optional] Indicates if BigQuery should accept rows that are missing trailing optional columns. If true, BigQuery treats missing trailing columns as null values. If false, records with missing trailing columns are treated as bad records, and if there are too many bad records, an invalid error is returned in the job result. The default value is false.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -520,15 +538,19 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>[Optional] Indicates if BigQuery should allow quoted data sections that contain newline characters in a CSV file. The default value is false.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>encoding=erat</code><ul>
|
||||
<li><code>encoding=ea</code><ul>
|
||||
<li>[Optional] The character encoding of the data. The supported values are UTF-8 or ISO-8859-1. The default value is UTF-8. BigQuery decodes the data after the raw, binary data has been split using the values of the quote and fieldDelimiter properties.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>field-delimiter=diam</code><ul>
|
||||
<li><code>field-delimiter=at</code><ul>
|
||||
<li>[Optional] The separator for fields in a CSV file. BigQuery converts the string to ISO-8859-1 encoding, and then uses the first byte of the encoded string to split the data in its raw, binary state. BigQuery also supports the escape sequence "\t" to specify a tab separator. The default value is a comma (',').</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>quote=nonumy</code><ul>
|
||||
<li><code>null-marker=sit</code><ul>
|
||||
<li>[Optional] An custom string that will represent a NULL value in CSV import data.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>quote=sit</code><ul>
|
||||
<li>[Optional] The value that is used to quote data sections in a CSV file. BigQuery converts the string to ISO-8859-1 encoding, and then uses the first byte of the encoded string to split the data in its raw, binary state. The default value is a double-quote ('"'). If your data does not contain quoted sections, set the property value to an empty string. If your data contains quoted newline characters, you must also set the allowQuotedNewlines property to true.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -539,19 +561,24 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..google-sheets-options range=at</code></p>
|
||||
<p><code>.. decimal-target-types=stet</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Defines the list of possible SQL data types to which the source decimal values are converted. This list and the precision and the scale parameters of the decimal field determine the target type. In the order of NUMERIC, BIGNUMERIC, and STRING, a type is picked if it is in the specified list and if it supports the precision and the scale. STRING supports all precision and scale values. If none of the listed types supports the precision and the scale, the type supporting the widest range in the specified list is picked, and if a value exceeds the supported range when reading the data, an error will be thrown. Example: Suppose the value of this field is ["NUMERIC", "BIGNUMERIC"]. If (precision,scale) is: (38,9) -> NUMERIC; (39,9) -> BIGNUMERIC (NUMERIC cannot hold 30 integer digits); (38,10) -> BIGNUMERIC (NUMERIC cannot hold 10 fractional digits); (76,38) -> BIGNUMERIC; (77,38) -> BIGNUMERIC (error if value exeeds supported range). This field cannot contain duplicate types. The order of the types in this field is ignored. For example, ["BIGNUMERIC", "NUMERIC"] is the same as ["NUMERIC", "BIGNUMERIC"] and NUMERIC always takes precedence over BIGNUMERIC. Defaults to ["NUMERIC", "STRING"] for ORC and ["NUMERIC"] for the other file formats.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>google-sheets-options range=duo</code><ul>
|
||||
<li>[Optional] Range of a sheet to query from. Only used when non-empty. Typical format: sheet_name!top_left_cell_id:bottom_right_cell_id For example: sheet1!A1:B20</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>skip-leading-rows=diam</code></p>
|
||||
<p><code>skip-leading-rows=elitr</code></p>
|
||||
<ul>
|
||||
<li>[Optional] The number of rows at the top of a sheet that BigQuery will skip when reading the data. The default value is 0. This property is useful if you have header rows that should be skipped. When autodetect is on, behavior is the following: * skipLeadingRows unspecified - Autodetect tries to detect headers in the first row. If they are not detected, the row is read as data. Otherwise data is read starting from the second row. * skipLeadingRows is 0 - Instructs autodetect that there are no headers and data should be read starting from the first row. * skipLeadingRows = N > 0 - Autodetect skips N-1 rows and tries to detect headers in row N. If headers are not detected, row N is just skipped. Otherwise row N is used to extract column names for the detected schema.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..hive-partitioning-options mode=diam</code></p>
|
||||
<p><code>..hive-partitioning-options mode=aliquyam</code></p>
|
||||
<ul>
|
||||
<li>[Optional] When set, what mode of hive partitioning to use when reading data. The following modes are supported. (1) AUTO: automatically infer partition key name(s) and type(s). (2) STRINGS: automatically infer partition key name(s). All types are interpreted as strings. (3) CUSTOM: partition key schema is encoded in the source URI prefix. Not all storage formats support hive partitioning. Requesting hive partitioning on an unsupported format will lead to an error. Currently supported types include: AVRO, CSV, JSON, ORC and Parquet.</li>
|
||||
</ul>
|
||||
@@ -567,12 +594,12 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. ignore-unknown-values=false</code></p>
|
||||
<p><code>.. ignore-unknown-values=true</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Indicates if BigQuery should allow extra values that are not represented in the table schema. If true, the extra values are ignored. If false, records with extra columns are treated as bad records, and if there are too many bad records, an invalid error is returned in the job result. The default value is false. The sourceFormat property determines what BigQuery treats as an extra value: CSV: Trailing columns JSON: Named values that don't match any column names Google Cloud Bigtable: This setting is ignored. Google Cloud Datastore backups: This setting is ignored. Avro: This setting is ignored.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>max-bad-records=46</code><ul>
|
||||
<li><code>max-bad-records=35</code><ul>
|
||||
<li>[Optional] The maximum number of bad records that BigQuery can ignore when reading data. If the number of bad records exceeds this value, an invalid error is returned in the job result. This is only valid for CSV, JSON, and Google Sheets. The default value is 0, which requires that all records are valid. This setting is ignored for Google Cloud Bigtable, Google Cloud Datastore backups and Avro formats.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -581,13 +608,13 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>enum-as-string=true</code></p>
|
||||
<p><code>enum-as-string=false</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Indicates whether to infer Parquet ENUM logical type as STRING instead of BYTES by default.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. source-format=sit</code></p>
|
||||
<p><code>.. source-format=kasd</code></p>
|
||||
<ul>
|
||||
<li>[Required] The data format. For CSV files, specify "CSV". For Google sheets, specify "GOOGLE_SHEETS". For newline-delimited JSON, specify "NEWLINE_DELIMITED_JSON". For Avro files, specify "AVRO". For Google Cloud Datastore backups, specify "DATASTORE_BACKUP". [Beta] For Google Cloud Bigtable, specify "BIGTABLE".</li>
|
||||
</ul>
|
||||
@@ -600,29 +627,29 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. friendly-name=stet</code></p>
|
||||
<p><code>.. friendly-name=sit</code></p>
|
||||
<ul>
|
||||
<li>[Optional] A descriptive name for this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>id=duo</code><ul>
|
||||
<li><code>id=kasd</code><ul>
|
||||
<li>[Output-only] An opaque ID uniquely identifying the table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>kind=elitr</code><ul>
|
||||
<li><code>kind=tempor</code><ul>
|
||||
<li>[Output-only] The type of the resource.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>labels=key=aliquyam</code><ul>
|
||||
<li><code>labels=key=dolor</code><ul>
|
||||
<li>The labels associated with this table. You can use these to organize and group your tables. Label keys and values can be no longer than 63 characters, can only contain lowercase letters, numeric characters, underscores and dashes. International characters are allowed. Label values are optional. Label keys must start with a letter and each label in the list must have a different key.</li>
|
||||
<li>the value will be associated with the given <code>key</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>last-modified-time=erat</code><ul>
|
||||
<li><code>last-modified-time=amet</code><ul>
|
||||
<li>[Output-only] The time when this table was last modified, in milliseconds since the epoch.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>location=ut</code><ul>
|
||||
<li><code>location=sit</code><ul>
|
||||
<li>[Output-only] The geographic location where the table resides. This value is inherited from the dataset.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -630,75 +657,75 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>[Optional] [TrustedTester] Enable automatic refresh of the materialized view when the base table is updated. The default value is "true".</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>last-refresh-time=rebum.</code><ul>
|
||||
<li><code>last-refresh-time=ipsum</code><ul>
|
||||
<li>[Output-only] [TrustedTester] The time when this materialized view was last modified, in milliseconds since the epoch.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>query=et</code><ul>
|
||||
<li><code>query=ipsum</code><ul>
|
||||
<li>[Required] A query whose result is persisted.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>refresh-interval-ms=sed</code></p>
|
||||
<p><code>refresh-interval-ms=et</code></p>
|
||||
<ul>
|
||||
<li>[Optional] [TrustedTester] The maximum frequency at which this materialized view will be refreshed. The default value is "1800000" (30 minutes).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..model.model-options labels=stet</code></p>
|
||||
<p><code>..model.model-options labels=elitr</code></p>
|
||||
<ul>
|
||||
<li>No description provided.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>loss-type=aliquyam</code><ul>
|
||||
<li><code>loss-type=eirmod</code><ul>
|
||||
<li>No description provided.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>model-type=kasd</code></p>
|
||||
<p><code>model-type=dolor</code></p>
|
||||
<ul>
|
||||
<li>No description provided.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>... num-bytes=lorem</code></p>
|
||||
<p><code>... num-bytes=sadipscing</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] The size of this table in bytes, excluding any data in the streaming buffer.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>num-long-term-bytes=sit</code><ul>
|
||||
<li><code>num-long-term-bytes=dolor</code><ul>
|
||||
<li>[Output-only] The number of bytes in the table that are considered "long-term storage".</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>num-physical-bytes=kasd</code><ul>
|
||||
<li><code>num-physical-bytes=dolor</code><ul>
|
||||
<li>[Output-only] [TrustedTester] The physical size of this table in bytes, excluding any data in the streaming buffer. This includes compression and storage used for time travel.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>num-rows=tempor</code><ul>
|
||||
<li><code>num-rows=consetetur</code><ul>
|
||||
<li>[Output-only] The number of rows of data in this table, excluding any data in the streaming buffer.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>range-partitioning field=dolor</code><ul>
|
||||
<li><code>range-partitioning field=et</code><ul>
|
||||
<li>[TrustedTester] [Required] The table is partitioned by this field. The field must be a top-level NULLABLE/REQUIRED field. The only supported type is INTEGER/INT64.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>range end=amet</code><ul>
|
||||
<li><code>range end=sit</code><ul>
|
||||
<li>[TrustedTester] [Required] The end of range partitioning, exclusive.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>interval=sit</code><ul>
|
||||
<li><code>interval=lorem</code><ul>
|
||||
<li>[TrustedTester] [Required] The width of each interval.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>start=rebum.</code></p>
|
||||
<p><code>start=nonumy</code></p>
|
||||
<ul>
|
||||
<li>[TrustedTester] [Required] The start of range partitioning, inclusive.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>... require-partition-filter=true</code></p>
|
||||
<p><code>... require-partition-filter=false</code></p>
|
||||
<ul>
|
||||
<li>[Optional] If set to true, queries over this table require a partition filter that can be used for partition elimination to be specified.</li>
|
||||
</ul>
|
||||
@@ -707,65 +734,65 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>[Output-only] A URL that can be used to access this resource again.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>snapshot-definition.base-table-reference dataset-id=ipsum</code><ul>
|
||||
<li><code>snapshot-definition.base-table-reference dataset-id=invidunt</code><ul>
|
||||
<li>[Required] The ID of the dataset containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>project-id=et</code><ul>
|
||||
<li><code>project-id=stet</code><ul>
|
||||
<li>[Required] The ID of the project containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>table-id=elitr</code></p>
|
||||
<p><code>table-id=voluptua.</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the table. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 1,024 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. snapshot-time=eirmod</code></p>
|
||||
<p><code>.. snapshot-time=at</code></p>
|
||||
<ul>
|
||||
<li>[Required] The time at which the base table was snapshot.</li>
|
||||
<li>[Required] The time at which the base table was snapshot. This value is reported in the JSON response using RFC3339 format.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..streaming-buffer estimated-bytes=dolor</code></p>
|
||||
<p><code>..streaming-buffer estimated-bytes=diam</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] A lower-bound estimate of the number of bytes currently in the streaming buffer.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>estimated-rows=sadipscing</code><ul>
|
||||
<li><code>estimated-rows=amet</code><ul>
|
||||
<li>[Output-only] A lower-bound estimate of the number of rows currently in the streaming buffer.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>oldest-entry-time=dolor</code></p>
|
||||
<p><code>oldest-entry-time=at</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] Contains the timestamp of the oldest entry in the streaming buffer, in milliseconds since the epoch, if the streaming buffer is available.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..table-reference dataset-id=dolor</code></p>
|
||||
<p><code>..table-reference dataset-id=eirmod</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the dataset containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>project-id=consetetur</code><ul>
|
||||
<li><code>project-id=erat</code><ul>
|
||||
<li>[Required] The ID of the project containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>table-id=et</code></p>
|
||||
<p><code>table-id=duo</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the table. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 1,024 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..time-partitioning expiration-ms=sit</code></p>
|
||||
<p><code>..time-partitioning expiration-ms=et</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Number of milliseconds for which to keep the storage for partitions in the table. The storage in a partition will have an expiration time of its partition time plus this value.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>field=lorem</code><ul>
|
||||
<li><code>field=erat</code><ul>
|
||||
<li>[Beta] [Optional] If not set, the table is partitioned by pseudo column, referenced via either '_PARTITIONTIME' as TIMESTAMP type, or '_PARTITIONDATE' as DATE type. If field is specified, the table is instead partitioned by this field. The field must be a top-level TIMESTAMP or DATE field. Its mode must be NULLABLE or REQUIRED.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -774,21 +801,25 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>type=diam</code></p>
|
||||
<p><code>type=accusam</code></p>
|
||||
<ul>
|
||||
<li>[Required] The supported types are DAY, HOUR, MONTH, and YEAR, which will generate one partition per day, hour, month, and year, respectively. When the type is not specified, the default behavior is DAY.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. type=ipsum</code></p>
|
||||
<p><code>.. type=et</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] Describes the table type. The following values are supported: TABLE: A normal BigQuery table. VIEW: A virtual table defined by a SQL query. SNAPSHOT: An immutable, read-only table that is a copy of another table. [TrustedTester] MATERIALIZED_VIEW: SQL query whose result is persisted. EXTERNAL: A table that references data stored in an external storage system, such as Google Cloud Storage. The default value is TABLE.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>view query=invidunt</code><ul>
|
||||
<li><code>view query=nonumy</code><ul>
|
||||
<li>[Required] A query that BigQuery executes when the view is referenced.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>use-explicit-column-names=false</code><ul>
|
||||
<li>True if the column names are explicitly specified. For example by using the 'CREATE VIEW v(c1, c2) AS ...' syntax. Can only be set using BigQuery's standard SQL: https://cloud.google.com/bigquery/sql-reference/</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>use-legacy-sql=false</code><ul>
|
||||
<li>Specifies whether to use BigQuery's legacy SQL for this view. The default value is true. If set to false, the view will use BigQuery's standard SQL: https://cloud.google.com/bigquery/sql-reference/ Queries and views that reference this view must use the same flag value.</li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>List - bigquery v2.0.4+20210327</title>
|
||||
<title>List - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -341,11 +341,10 @@
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery.readonly</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform.read-only</em></li>
|
||||
</ul>
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery.readonly</em>.
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigquery</em>.
|
||||
You can set the scope for this method like this: <code>bigquery2 --scope <scope> tables list ...</code></p>
|
||||
<h1 id="required-scalar-arguments">Required Scalar Arguments</h1>
|
||||
<ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Patch - bigquery v2.0.4+20210327</title>
|
||||
<title>Patch - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -280,6 +280,9 @@
|
||||
<li class="toctree-l2"><a href="#optional-output-flags">Optional Output Flags</a></li>
|
||||
|
||||
|
||||
<li class="toctree-l2"><a href="#optional-method-properties">Optional Method Properties</a></li>
|
||||
|
||||
|
||||
<li class="toctree-l2"><a href="#optional-general-properties">Optional General Properties</a></li>
|
||||
|
||||
|
||||
@@ -370,6 +373,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
clustering:
|
||||
fields: [string]
|
||||
creation-time: string
|
||||
default-collation: string
|
||||
description: string
|
||||
encryption-configuration:
|
||||
kms-key-name: string
|
||||
@@ -377,6 +381,8 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
expiration-time: string
|
||||
external-data-configuration:
|
||||
autodetect: boolean
|
||||
avro-options:
|
||||
use-avro-logical-types: boolean
|
||||
bigtable-options:
|
||||
ignore-unspecified-column-families: boolean
|
||||
read-rowkey-as-string: boolean
|
||||
@@ -387,8 +393,10 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
allow-quoted-newlines: boolean
|
||||
encoding: string
|
||||
field-delimiter: string
|
||||
null-marker: string
|
||||
quote: string
|
||||
skip-leading-rows: string
|
||||
decimal-target-types: [string]
|
||||
google-sheets-options:
|
||||
range: string
|
||||
skip-leading-rows: string
|
||||
@@ -453,6 +461,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
type: string
|
||||
view:
|
||||
query: string
|
||||
use-explicit-column-names: boolean
|
||||
use-legacy-sql: boolean
|
||||
|
||||
</code></pre>
|
||||
@@ -460,35 +469,39 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><code>-r .clustering fields=at</code></p>
|
||||
<p><code>-r .clustering fields=consetetur</code></p>
|
||||
<ul>
|
||||
<li>[Repeated] One or more fields on which data should be clustered. Only top-level, non-repeated, simple-type fields are supported. When you cluster a table using multiple columns, the order of columns you specify is important. The order of the specified columns determines the sort order of the data.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. creation-time=diam</code></p>
|
||||
<p><code>.. creation-time=dolor</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] The time when this table was created, in milliseconds since the epoch.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>description=amet</code><ul>
|
||||
<li><code>default-collation=amet</code><ul>
|
||||
<li>[Output-only] The default collation of the table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>description=et</code><ul>
|
||||
<li>[Optional] A user-friendly description of this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>encryption-configuration kms-key-name=at</code></p>
|
||||
<p><code>encryption-configuration kms-key-name=aliquyam</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Describes the Cloud KMS encryption key that will be used to protect destination BigQuery table. The BigQuery Service Account associated with your project requires access to this encryption key.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. etag=eirmod</code></p>
|
||||
<p><code>.. etag=ipsum</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] A hash of the table metadata. Used to ensure there were no concurrent modifications to the resource when attempting an update. Not guaranteed to change when the table contents or the fields numRows, numBytes, numLongTermBytes or lastModifiedTime change.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>expiration-time=erat</code><ul>
|
||||
<li><code>expiration-time=gubergren</code><ul>
|
||||
<li>[Optional] The time when this table expires, in milliseconds since the epoch. If not present, the table will persist indefinitely. Expired tables will be deleted and their storage reclaimed. The defaultTableExpirationMs property of the encapsulating dataset can be used to set a default expirationTime on newly created tables.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -496,7 +509,15 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>Try to detect schema and format options automatically. Any option specified explicitly will be honored.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>bigtable-options ignore-unspecified-column-families=true</code><ul>
|
||||
<li>
|
||||
<p><code>avro-options use-avro-logical-types=true</code></p>
|
||||
<ul>
|
||||
<li>[Optional] If sourceFormat is set to "AVRO", indicates whether to interpret logical types as the corresponding BigQuery data type (for example, TIMESTAMP), instead of using the raw type (for example, INTEGER).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..bigtable-options ignore-unspecified-column-families=true</code></p>
|
||||
<ul>
|
||||
<li>[Optional] If field is true, then the column families that are not specified in columnFamilies list are not exposed in the table schema. Otherwise, they are read with BYTES type values. The default value is false.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -507,55 +528,64 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. compression=et</code></p>
|
||||
<p><code>.. compression=no</code></p>
|
||||
<ul>
|
||||
<li>[Optional] The compression type of the data source. Possible values include GZIP and NONE. The default value is NONE. This setting is ignored for Google Cloud Bigtable, Google Cloud Datastore backups and Avro formats.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>connection-id=nonumy</code><ul>
|
||||
<li><code>connection-id=tempor</code><ul>
|
||||
<li>[Optional, Trusted Tester] Connection for external data source.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>csv-options allow-jagged-rows=false</code><ul>
|
||||
<li><code>csv-options allow-jagged-rows=true</code><ul>
|
||||
<li>[Optional] Indicates if BigQuery should accept rows that are missing trailing optional columns. If true, BigQuery treats missing trailing columns as null values. If false, records with missing trailing columns are treated as bad records, and if there are too many bad records, an invalid error is returned in the job result. The default value is false.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>allow-quoted-newlines=false</code><ul>
|
||||
<li><code>allow-quoted-newlines=true</code><ul>
|
||||
<li>[Optional] Indicates if BigQuery should allow quoted data sections that contain newline characters in a CSV file. The default value is false.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>encoding=consetetur</code><ul>
|
||||
<li><code>encoding=sit</code><ul>
|
||||
<li>[Optional] The character encoding of the data. The supported values are UTF-8 or ISO-8859-1. The default value is UTF-8. BigQuery decodes the data after the raw, binary data has been split using the values of the quote and fieldDelimiter properties.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>field-delimiter=dolor</code><ul>
|
||||
<li><code>field-delimiter=amet.</code><ul>
|
||||
<li>[Optional] The separator for fields in a CSV file. BigQuery converts the string to ISO-8859-1 encoding, and then uses the first byte of the encoded string to split the data in its raw, binary state. BigQuery also supports the escape sequence "\t" to specify a tab separator. The default value is a comma (',').</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>quote=amet</code><ul>
|
||||
<li><code>null-marker=ipsum</code><ul>
|
||||
<li>[Optional] An custom string that will represent a NULL value in CSV import data.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>quote=at</code><ul>
|
||||
<li>[Optional] The value that is used to quote data sections in a CSV file. BigQuery converts the string to ISO-8859-1 encoding, and then uses the first byte of the encoded string to split the data in its raw, binary state. The default value is a double-quote ('"'). If your data does not contain quoted sections, set the property value to an empty string. If your data contains quoted newline characters, you must also set the allowQuotedNewlines property to true.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>skip-leading-rows=et</code></p>
|
||||
<p><code>skip-leading-rows=vero</code></p>
|
||||
<ul>
|
||||
<li>[Optional] The number of rows at the top of a CSV file that BigQuery will skip when reading the data. The default value is 0. This property is useful if you have header rows in the file that should be skipped. When autodetect is on, the behavior is the following: * skipLeadingRows unspecified - Autodetect tries to detect headers in the first row. If they are not detected, the row is read as data. Otherwise data is read starting from the second row. * skipLeadingRows is 0 - Instructs autodetect that there are no headers and data should be read starting from the first row. * skipLeadingRows = N > 0 - Autodetect skips N-1 rows and tries to detect headers in row N. If headers are not detected, row N is just skipped. Otherwise row N is used to extract column names for the detected schema.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..google-sheets-options range=aliquyam</code></p>
|
||||
<p><code>.. decimal-target-types=takimata</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Defines the list of possible SQL data types to which the source decimal values are converted. This list and the precision and the scale parameters of the decimal field determine the target type. In the order of NUMERIC, BIGNUMERIC, and STRING, a type is picked if it is in the specified list and if it supports the precision and the scale. STRING supports all precision and scale values. If none of the listed types supports the precision and the scale, the type supporting the widest range in the specified list is picked, and if a value exceeds the supported range when reading the data, an error will be thrown. Example: Suppose the value of this field is ["NUMERIC", "BIGNUMERIC"]. If (precision,scale) is: (38,9) -> NUMERIC; (39,9) -> BIGNUMERIC (NUMERIC cannot hold 30 integer digits); (38,10) -> BIGNUMERIC (NUMERIC cannot hold 10 fractional digits); (76,38) -> BIGNUMERIC; (77,38) -> BIGNUMERIC (error if value exeeds supported range). This field cannot contain duplicate types. The order of the types in this field is ignored. For example, ["BIGNUMERIC", "NUMERIC"] is the same as ["NUMERIC", "BIGNUMERIC"] and NUMERIC always takes precedence over BIGNUMERIC. Defaults to ["NUMERIC", "STRING"] for ORC and ["NUMERIC"] for the other file formats.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>google-sheets-options range=gubergren</code><ul>
|
||||
<li>[Optional] Range of a sheet to query from. Only used when non-empty. Typical format: sheet_name!top_left_cell_id:bottom_right_cell_id For example: sheet1!A1:B20</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>skip-leading-rows=ipsum</code></p>
|
||||
<p><code>skip-leading-rows=et</code></p>
|
||||
<ul>
|
||||
<li>[Optional] The number of rows at the top of a sheet that BigQuery will skip when reading the data. The default value is 0. This property is useful if you have header rows that should be skipped. When autodetect is on, behavior is the following: * skipLeadingRows unspecified - Autodetect tries to detect headers in the first row. If they are not detected, the row is read as data. Otherwise data is read starting from the second row. * skipLeadingRows is 0 - Instructs autodetect that there are no headers and data should be read starting from the first row. * skipLeadingRows = N > 0 - Autodetect skips N-1 rows and tries to detect headers in row N. If headers are not detected, row N is just skipped. Otherwise row N is used to extract column names for the detected schema.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..hive-partitioning-options mode=gubergren</code></p>
|
||||
<p><code>..hive-partitioning-options mode=invidunt</code></p>
|
||||
<ul>
|
||||
<li>[Optional] When set, what mode of hive partitioning to use when reading data. The following modes are supported. (1) AUTO: automatically infer partition key name(s) and type(s). (2) STRINGS: automatically infer partition key name(s). All types are interpreted as strings. (3) CUSTOM: partition key schema is encoded in the source URI prefix. Not all storage formats support hive partitioning. Requesting hive partitioning on an unsupported format will lead to an error. Currently supported types include: AVRO, CSV, JSON, ORC and Parquet.</li>
|
||||
</ul>
|
||||
@@ -565,27 +595,27 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>source-uri-prefix=sea</code></p>
|
||||
<p><code>source-uri-prefix=gubergren</code></p>
|
||||
<ul>
|
||||
<li>[Optional] When hive partition detection is requested, a common prefix for all source uris should be supplied. The prefix must end immediately before the partition key encoding begins. For example, consider files following this data layout. gs://bucket/path_to_table/dt=2019-01-01/country=BR/id=7/file.avro gs://bucket/path_to_table/dt=2018-12-31/country=CA/id=3/file.avro When hive partitioning is requested with either AUTO or STRINGS detection, the common prefix can be either of gs://bucket/path_to_table or gs://bucket/path_to_table/ (trailing slash does not matter).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. ignore-unknown-values=true</code></p>
|
||||
<p><code>.. ignore-unknown-values=false</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Indicates if BigQuery should allow extra values that are not represented in the table schema. If true, the extra values are ignored. If false, records with extra columns are treated as bad records, and if there are too many bad records, an invalid error is returned in the job result. The default value is false. The sourceFormat property determines what BigQuery treats as an extra value: CSV: Trailing columns JSON: Named values that don't match any column names Google Cloud Bigtable: This setting is ignored. Google Cloud Datastore backups: This setting is ignored. Avro: This setting is ignored.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>max-bad-records=36</code><ul>
|
||||
<li><code>max-bad-records=51</code><ul>
|
||||
<li>[Optional] The maximum number of bad records that BigQuery can ignore when reading data. If the number of bad records exceeds this value, an invalid error is returned in the job result. This is only valid for CSV, JSON, and Google Sheets. The default value is 0, which requires that all records are valid. This setting is ignored for Google Cloud Bigtable, Google Cloud Datastore backups and Avro formats.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>parquet-options enable-list-inference=false</code><ul>
|
||||
<li><code>parquet-options enable-list-inference=true</code><ul>
|
||||
<li>[Optional] Indicates whether to use schema inference specifically for Parquet LIST logical type.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>enum-as-string=true</code></p>
|
||||
<p><code>enum-as-string=false</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Indicates whether to infer Parquet ENUM logical type as STRING instead of BYTES by default.</li>
|
||||
</ul>
|
||||
@@ -597,32 +627,32 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>source-uris=sea</code></p>
|
||||
<p><code>source-uris=lorem</code></p>
|
||||
<ul>
|
||||
<li>[Required] The fully-qualified URIs that point to your data in Google Cloud. For Google Cloud Storage URIs: Each URI can contain one '<em>' wildcard character and it must come after the 'bucket' name. Size limits related to load jobs apply to external data sources. For Google Cloud Bigtable URIs: Exactly one URI can be specified and it has be a fully specified and valid HTTPS URL for a Google Cloud Bigtable table. For Google Cloud Datastore backups, exactly one URI can be specified. Also, the '</em>' wildcard character is not allowed.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. friendly-name=sit</code></p>
|
||||
<p><code>.. friendly-name=dolores</code></p>
|
||||
<ul>
|
||||
<li>[Optional] A descriptive name for this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>id=amet.</code><ul>
|
||||
<li><code>id=consetetur</code><ul>
|
||||
<li>[Output-only] An opaque ID uniquely identifying the table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>kind=ipsum</code><ul>
|
||||
<li><code>kind=stet</code><ul>
|
||||
<li>[Output-only] The type of the resource.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>labels=key=at</code><ul>
|
||||
<li><code>labels=key=accusam</code><ul>
|
||||
<li>The labels associated with this table. You can use these to organize and group your tables. Label keys and values can be no longer than 63 characters, can only contain lowercase letters, numeric characters, underscores and dashes. International characters are allowed. Label values are optional. Label keys must start with a letter and each label in the list must have a different key.</li>
|
||||
<li>the value will be associated with the given <code>key</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>last-modified-time=vero</code><ul>
|
||||
<li><code>last-modified-time=consetetur</code><ul>
|
||||
<li>[Output-only] The time when this table was last modified, in milliseconds since the epoch.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -630,73 +660,73 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>[Output-only] The geographic location where the table resides. This value is inherited from the dataset.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>materialized-view enable-refresh=false</code><ul>
|
||||
<li><code>materialized-view enable-refresh=true</code><ul>
|
||||
<li>[Optional] [TrustedTester] Enable automatic refresh of the materialized view when the base table is updated. The default value is "true".</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>last-refresh-time=invidunt</code><ul>
|
||||
<li><code>last-refresh-time=nonumy</code><ul>
|
||||
<li>[Output-only] [TrustedTester] The time when this materialized view was last modified, in milliseconds since the epoch.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>query=magna</code><ul>
|
||||
<li><code>query=sea</code><ul>
|
||||
<li>[Required] A query whose result is persisted.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>refresh-interval-ms=sit</code></p>
|
||||
<p><code>refresh-interval-ms=eos</code></p>
|
||||
<ul>
|
||||
<li>[Optional] [TrustedTester] The maximum frequency at which this materialized view will be refreshed. The default value is "1800000" (30 minutes).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..model.model-options labels=gubergren</code></p>
|
||||
<p><code>..model.model-options labels=dolore</code></p>
|
||||
<ul>
|
||||
<li>No description provided.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>loss-type=elitr</code><ul>
|
||||
<li><code>loss-type=accusam</code><ul>
|
||||
<li>No description provided.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>model-type=ipsum</code></p>
|
||||
<p><code>model-type=elitr</code></p>
|
||||
<ul>
|
||||
<li>No description provided.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>... num-bytes=kasd</code></p>
|
||||
<p><code>... num-bytes=sed</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] The size of this table in bytes, excluding any data in the streaming buffer.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>num-long-term-bytes=dolore</code><ul>
|
||||
<li><code>num-long-term-bytes=labore</code><ul>
|
||||
<li>[Output-only] The number of bytes in the table that are considered "long-term storage".</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>num-physical-bytes=lorem</code><ul>
|
||||
<li><code>num-physical-bytes=et</code><ul>
|
||||
<li>[Output-only] [TrustedTester] The physical size of this table in bytes, excluding any data in the streaming buffer. This includes compression and storage used for time travel.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>num-rows=amet</code><ul>
|
||||
<li><code>num-rows=eirmod</code><ul>
|
||||
<li>[Output-only] The number of rows of data in this table, excluding any data in the streaming buffer.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>range-partitioning field=ipsum</code><ul>
|
||||
<li><code>range-partitioning field=sed</code><ul>
|
||||
<li>[TrustedTester] [Required] The table is partitioned by this field. The field must be a top-level NULLABLE/REQUIRED field. The only supported type is INTEGER/INT64.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>range end=lorem</code><ul>
|
||||
<li><code>range end=at</code><ul>
|
||||
<li>[TrustedTester] [Required] The end of range partitioning, exclusive.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>interval=dolores</code><ul>
|
||||
<li><code>interval=stet</code><ul>
|
||||
<li>[TrustedTester] [Required] The width of each interval.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>start=consetetur</code></p>
|
||||
<p><code>start=sit</code></p>
|
||||
<ul>
|
||||
<li>[TrustedTester] [Required] The start of range partitioning, inclusive.</li>
|
||||
</ul>
|
||||
@@ -707,69 +737,69 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>[Optional] If set to true, queries over this table require a partition filter that can be used for partition elimination to be specified.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>self-link=takimata</code><ul>
|
||||
<li><code>self-link=lorem</code><ul>
|
||||
<li>[Output-only] A URL that can be used to access this resource again.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>snapshot-definition.base-table-reference dataset-id=sed</code><ul>
|
||||
<li><code>snapshot-definition.base-table-reference dataset-id=dolor</code><ul>
|
||||
<li>[Required] The ID of the dataset containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>project-id=nonumy</code><ul>
|
||||
<li><code>project-id=amet</code><ul>
|
||||
<li>[Required] The ID of the project containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>table-id=sea</code></p>
|
||||
<p><code>table-id=magna</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the table. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 1,024 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. snapshot-time=eos</code></p>
|
||||
<p><code>.. snapshot-time=magna</code></p>
|
||||
<ul>
|
||||
<li>[Required] The time at which the base table was snapshot.</li>
|
||||
<li>[Required] The time at which the base table was snapshot. This value is reported in the JSON response using RFC3339 format.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..streaming-buffer estimated-bytes=dolore</code></p>
|
||||
<p><code>..streaming-buffer estimated-bytes=invidunt</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] A lower-bound estimate of the number of bytes currently in the streaming buffer.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>estimated-rows=accusam</code><ul>
|
||||
<li><code>estimated-rows=et</code><ul>
|
||||
<li>[Output-only] A lower-bound estimate of the number of rows currently in the streaming buffer.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>oldest-entry-time=elitr</code></p>
|
||||
<p><code>oldest-entry-time=et</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] Contains the timestamp of the oldest entry in the streaming buffer, in milliseconds since the epoch, if the streaming buffer is available.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..table-reference dataset-id=sed</code></p>
|
||||
<p><code>..table-reference dataset-id=dolor</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the dataset containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>project-id=labore</code><ul>
|
||||
<li><code>project-id=erat</code><ul>
|
||||
<li>[Required] The ID of the project containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>table-id=et</code></p>
|
||||
<p><code>table-id=dolore</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the table. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 1,024 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..time-partitioning expiration-ms=eirmod</code></p>
|
||||
<p><code>..time-partitioning expiration-ms=vero</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Number of milliseconds for which to keep the storage for partitions in the table. The storage in a partition will have an expiration time of its partition time plus this value.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>field=sed</code><ul>
|
||||
<li><code>field=ea</code><ul>
|
||||
<li>[Beta] [Optional] If not set, the table is partitioned by pseudo column, referenced via either '_PARTITIONTIME' as TIMESTAMP type, or '_PARTITIONDATE' as DATE type. If field is specified, the table is instead partitioned by this field. The field must be a top-level TIMESTAMP or DATE field. Its mode must be NULLABLE or REQUIRED.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -778,22 +808,26 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>type=lorem</code></p>
|
||||
<p><code>type=amet.</code></p>
|
||||
<ul>
|
||||
<li>[Required] The supported types are DAY, HOUR, MONTH, and YEAR, which will generate one partition per day, hour, month, and year, respectively. When the type is not specified, the default behavior is DAY.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. type=dolor</code></p>
|
||||
<p><code>.. type=eirmod</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] Describes the table type. The following values are supported: TABLE: A normal BigQuery table. VIEW: A virtual table defined by a SQL query. SNAPSHOT: An immutable, read-only table that is a copy of another table. [TrustedTester] MATERIALIZED_VIEW: SQL query whose result is persisted. EXTERNAL: A table that references data stored in an external storage system, such as Google Cloud Storage. The default value is TABLE.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>view query=amet</code><ul>
|
||||
<li><code>view query=sanctus</code><ul>
|
||||
<li>[Required] A query that BigQuery executes when the view is referenced.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>use-legacy-sql=false</code><ul>
|
||||
<li><code>use-explicit-column-names=false</code><ul>
|
||||
<li>True if the column names are explicitly specified. For example by using the 'CREATE VIEW v(c1, c2) AS ...' syntax. Can only be set using BigQuery's standard SQL: https://cloud.google.com/bigquery/sql-reference/</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>use-legacy-sql=true</code><ul>
|
||||
<li>Specifies whether to use BigQuery's legacy SQL for this view. The default value is true. If set to false, the view will use BigQuery's standard SQL: https://cloud.google.com/bigquery/sql-reference/ Queries and views that reference this view must use the same flag value.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -817,6 +851,16 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<h1 id="optional-method-properties">Optional Method Properties</h1>
|
||||
<p>You may set the following properties to further configure the call. Please note that <code>-p</code> is followed by one
|
||||
or more key-value-pairs, and is called like this <code>-p k1=v1 k2=v2</code> even though the listing below repeats the
|
||||
<code>-p</code> for completeness.</p>
|
||||
<ul>
|
||||
<li><strong>-p autodetect-schema=boolean</strong><ul>
|
||||
<li>When true will autodetect schema, else will keep original schema</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<h1 id="optional-general-properties">Optional General Properties</h1>
|
||||
<p>The following properties can configure any call, and are not specific to this method.</p>
|
||||
<ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Set Iam Policy - bigquery v2.0.4+20210327</title>
|
||||
<title>Set Iam Policy - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -368,18 +368,18 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r .policy etag=magna</code><ul>
|
||||
<li><code>-r .policy etag=et</code><ul>
|
||||
<li><code>etag</code> is used for optimistic concurrency control as a way to help prevent simultaneous updates of a policy from overwriting each other. It is strongly suggested that systems make use of the <code>etag</code> in the read-modify-write cycle to perform policy updates in order to avoid race conditions: An <code>etag</code> is returned in the response to <code>getIamPolicy</code>, and systems are expected to put that etag in the request to <code>setIamPolicy</code> to ensure that their change will be applied to the same version of the policy. <strong>Important:</strong> If you use IAM Conditions, you must include the <code>etag</code> field whenever you call <code>setIamPolicy</code>. If you omit this field, then IAM allows you to overwrite a version <code>3</code> policy with a version <code>1</code> policy, and all of the conditions in the version <code>3</code> policy are lost.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>version=13</code></p>
|
||||
<p><code>version=27</code></p>
|
||||
<ul>
|
||||
<li>Specifies the format of the policy. Valid values are <code>0</code>, <code>1</code>, and <code>3</code>. Requests that specify an invalid value are rejected. Any operation that affects conditional role bindings must specify version <code>3</code>. This requirement applies to the following operations: * Getting a policy that includes a conditional role binding * Adding a conditional role binding to a policy * Changing a conditional role binding in a policy * Removing any role binding, with or without a condition, from a policy that includes conditions <strong>Important:</strong> If you use IAM Conditions, you must include the <code>etag</code> field whenever you call <code>setIamPolicy</code>. If you omit this field, then IAM allows you to overwrite a version <code>3</code> policy with a version <code>1</code> policy, and all of the conditions in the version <code>3</code> policy are lost. If a policy does not include any conditions, operations on that policy may specify any valid version or leave the field unset. To learn which resources support conditions in their IAM policies, see the <a href="https://cloud.google.com/iam/help/conditions/resource-policies">IAM documentation</a>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. update-mask=et</code></p>
|
||||
<p><code>.. update-mask=erat</code></p>
|
||||
<ul>
|
||||
<li>OPTIONAL: A FieldMask specifying which fields of the policy to modify. Only the fields in the mask will be modified. If no mask is provided, the following default mask is used: <code>paths: &#34;bindings, etag&#34;</code></li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Test Iam Permissions - bigquery v2.0.4+20210327</title>
|
||||
<title>Test Iam Permissions - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -343,7 +343,6 @@
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/bigquery.readonly</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform.read-only</em></li>
|
||||
</ul>
|
||||
@@ -367,7 +366,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r . permissions=et</code><ul>
|
||||
<li><code>-r . permissions=eos</code><ul>
|
||||
<li>The set of permissions to check for the <code>resource</code>. Permissions with wildcards (such as '<em>' or 'storage.</em>') are not allowed. For more information see <a href="https://cloud.google.com/iam/docs/overview#permissions">IAM Overview</a>.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Update - bigquery v2.0.4+20210327</title>
|
||||
<title>Update - bigquery v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> bigquery v2.0.4+20210327</a>
|
||||
<a href=".." class="icon icon-home"> bigquery v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -295,6 +295,9 @@
|
||||
<li class="toctree-l2"><a href="#optional-output-flags">Optional Output Flags</a></li>
|
||||
|
||||
|
||||
<li class="toctree-l2"><a href="#optional-method-properties">Optional Method Properties</a></li>
|
||||
|
||||
|
||||
<li class="toctree-l2"><a href="#optional-general-properties">Optional General Properties</a></li>
|
||||
|
||||
|
||||
@@ -370,6 +373,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
clustering:
|
||||
fields: [string]
|
||||
creation-time: string
|
||||
default-collation: string
|
||||
description: string
|
||||
encryption-configuration:
|
||||
kms-key-name: string
|
||||
@@ -377,6 +381,8 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
expiration-time: string
|
||||
external-data-configuration:
|
||||
autodetect: boolean
|
||||
avro-options:
|
||||
use-avro-logical-types: boolean
|
||||
bigtable-options:
|
||||
ignore-unspecified-column-families: boolean
|
||||
read-rowkey-as-string: boolean
|
||||
@@ -387,8 +393,10 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
allow-quoted-newlines: boolean
|
||||
encoding: string
|
||||
field-delimiter: string
|
||||
null-marker: string
|
||||
quote: string
|
||||
skip-leading-rows: string
|
||||
decimal-target-types: [string]
|
||||
google-sheets-options:
|
||||
range: string
|
||||
skip-leading-rows: string
|
||||
@@ -453,6 +461,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
type: string
|
||||
view:
|
||||
query: string
|
||||
use-explicit-column-names: boolean
|
||||
use-legacy-sql: boolean
|
||||
|
||||
</code></pre>
|
||||
@@ -460,35 +469,39 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><code>-r .clustering fields=dolor</code></p>
|
||||
<p><code>-r .clustering fields=nonumy</code></p>
|
||||
<ul>
|
||||
<li>[Repeated] One or more fields on which data should be clustered. Only top-level, non-repeated, simple-type fields are supported. When you cluster a table using multiple columns, the order of columns you specify is important. The order of the specified columns determines the sort order of the data.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. creation-time=erat</code></p>
|
||||
<p><code>.. creation-time=ea</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] The time when this table was created, in milliseconds since the epoch.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>description=dolore</code><ul>
|
||||
<li><code>default-collation=aliquyam</code><ul>
|
||||
<li>[Output-only] The default collation of the table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>description=nonumy</code><ul>
|
||||
<li>[Optional] A user-friendly description of this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>encryption-configuration kms-key-name=vero</code></p>
|
||||
<p><code>encryption-configuration kms-key-name=stet</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Describes the Cloud KMS encryption key that will be used to protect destination BigQuery table. The BigQuery Service Account associated with your project requires access to this encryption key.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. etag=ea</code></p>
|
||||
<p><code>.. etag=rebum.</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] A hash of the table metadata. Used to ensure there were no concurrent modifications to the resource when attempting an update. Not guaranteed to change when the table contents or the fields numRows, numBytes, numLongTermBytes or lastModifiedTime change.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>expiration-time=et</code><ul>
|
||||
<li><code>expiration-time=eirmod</code><ul>
|
||||
<li>[Optional] The time when this table expires, in milliseconds since the epoch. If not present, the table will persist indefinitely. Expired tables will be deleted and their storage reclaimed. The defaultTableExpirationMs property of the encapsulating dataset can be used to set a default expirationTime on newly created tables.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -496,23 +509,31 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>Try to detect schema and format options automatically. Any option specified explicitly will be honored.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>bigtable-options ignore-unspecified-column-families=true</code><ul>
|
||||
<li>
|
||||
<p><code>avro-options use-avro-logical-types=false</code></p>
|
||||
<ul>
|
||||
<li>[Optional] If sourceFormat is set to "AVRO", indicates whether to interpret logical types as the corresponding BigQuery data type (for example, TIMESTAMP), instead of using the raw type (for example, INTEGER).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..bigtable-options ignore-unspecified-column-families=false</code></p>
|
||||
<ul>
|
||||
<li>[Optional] If field is true, then the column families that are not specified in columnFamilies list are not exposed in the table schema. Otherwise, they are read with BYTES type values. The default value is false.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>read-rowkey-as-string=true</code></p>
|
||||
<p><code>read-rowkey-as-string=false</code></p>
|
||||
<ul>
|
||||
<li>[Optional] If field is true, then the rowkey column families will be read and converted to string. Otherwise they are read with BYTES type values and users need to manually cast them with CAST if necessary. The default value is false.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. compression=sed</code></p>
|
||||
<p><code>.. compression=magna</code></p>
|
||||
<ul>
|
||||
<li>[Optional] The compression type of the data source. Possible values include GZIP and NONE. The default value is NONE. This setting is ignored for Google Cloud Bigtable, Google Cloud Datastore backups and Avro formats.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>connection-id=dolor</code><ul>
|
||||
<li><code>connection-id=no</code><ul>
|
||||
<li>[Optional, Trusted Tester] Connection for external data source.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -524,109 +545,118 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>[Optional] Indicates if BigQuery should allow quoted data sections that contain newline characters in a CSV file. The default value is false.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>encoding=eos</code><ul>
|
||||
<li><code>encoding=consetetur</code><ul>
|
||||
<li>[Optional] The character encoding of the data. The supported values are UTF-8 or ISO-8859-1. The default value is UTF-8. BigQuery decodes the data after the raw, binary data has been split using the values of the quote and fieldDelimiter properties.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>field-delimiter=nonumy</code><ul>
|
||||
<li><code>field-delimiter=ea</code><ul>
|
||||
<li>[Optional] The separator for fields in a CSV file. BigQuery converts the string to ISO-8859-1 encoding, and then uses the first byte of the encoded string to split the data in its raw, binary state. BigQuery also supports the escape sequence "\t" to specify a tab separator. The default value is a comma (',').</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>quote=ea</code><ul>
|
||||
<li><code>null-marker=lorem</code><ul>
|
||||
<li>[Optional] An custom string that will represent a NULL value in CSV import data.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>quote=elitr</code><ul>
|
||||
<li>[Optional] The value that is used to quote data sections in a CSV file. BigQuery converts the string to ISO-8859-1 encoding, and then uses the first byte of the encoded string to split the data in its raw, binary state. The default value is a double-quote ('"'). If your data does not contain quoted sections, set the property value to an empty string. If your data contains quoted newline characters, you must also set the allowQuotedNewlines property to true.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>skip-leading-rows=aliquyam</code></p>
|
||||
<p><code>skip-leading-rows=justo</code></p>
|
||||
<ul>
|
||||
<li>[Optional] The number of rows at the top of a CSV file that BigQuery will skip when reading the data. The default value is 0. This property is useful if you have header rows in the file that should be skipped. When autodetect is on, the behavior is the following: * skipLeadingRows unspecified - Autodetect tries to detect headers in the first row. If they are not detected, the row is read as data. Otherwise data is read starting from the second row. * skipLeadingRows is 0 - Instructs autodetect that there are no headers and data should be read starting from the first row. * skipLeadingRows = N > 0 - Autodetect skips N-1 rows and tries to detect headers in row N. If headers are not detected, row N is just skipped. Otherwise row N is used to extract column names for the detected schema.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..google-sheets-options range=nonumy</code></p>
|
||||
<p><code>.. decimal-target-types=lorem</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Defines the list of possible SQL data types to which the source decimal values are converted. This list and the precision and the scale parameters of the decimal field determine the target type. In the order of NUMERIC, BIGNUMERIC, and STRING, a type is picked if it is in the specified list and if it supports the precision and the scale. STRING supports all precision and scale values. If none of the listed types supports the precision and the scale, the type supporting the widest range in the specified list is picked, and if a value exceeds the supported range when reading the data, an error will be thrown. Example: Suppose the value of this field is ["NUMERIC", "BIGNUMERIC"]. If (precision,scale) is: (38,9) -> NUMERIC; (39,9) -> BIGNUMERIC (NUMERIC cannot hold 30 integer digits); (38,10) -> BIGNUMERIC (NUMERIC cannot hold 10 fractional digits); (76,38) -> BIGNUMERIC; (77,38) -> BIGNUMERIC (error if value exeeds supported range). This field cannot contain duplicate types. The order of the types in this field is ignored. For example, ["BIGNUMERIC", "NUMERIC"] is the same as ["NUMERIC", "BIGNUMERIC"] and NUMERIC always takes precedence over BIGNUMERIC. Defaults to ["NUMERIC", "STRING"] for ORC and ["NUMERIC"] for the other file formats.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>google-sheets-options range=labore</code><ul>
|
||||
<li>[Optional] Range of a sheet to query from. Only used when non-empty. Typical format: sheet_name!top_left_cell_id:bottom_right_cell_id For example: sheet1!A1:B20</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>skip-leading-rows=stet</code></p>
|
||||
<p><code>skip-leading-rows=gubergren</code></p>
|
||||
<ul>
|
||||
<li>[Optional] The number of rows at the top of a sheet that BigQuery will skip when reading the data. The default value is 0. This property is useful if you have header rows that should be skipped. When autodetect is on, behavior is the following: * skipLeadingRows unspecified - Autodetect tries to detect headers in the first row. If they are not detected, the row is read as data. Otherwise data is read starting from the second row. * skipLeadingRows is 0 - Instructs autodetect that there are no headers and data should be read starting from the first row. * skipLeadingRows = N > 0 - Autodetect skips N-1 rows and tries to detect headers in row N. If headers are not detected, row N is just skipped. Otherwise row N is used to extract column names for the detected schema.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..hive-partitioning-options mode=rebum.</code></p>
|
||||
<p><code>..hive-partitioning-options mode=vero</code></p>
|
||||
<ul>
|
||||
<li>[Optional] When set, what mode of hive partitioning to use when reading data. The following modes are supported. (1) AUTO: automatically infer partition key name(s) and type(s). (2) STRINGS: automatically infer partition key name(s). All types are interpreted as strings. (3) CUSTOM: partition key schema is encoded in the source URI prefix. Not all storage formats support hive partitioning. Requesting hive partitioning on an unsupported format will lead to an error. Currently supported types include: AVRO, CSV, JSON, ORC and Parquet.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>require-partition-filter=true</code><ul>
|
||||
<li><code>require-partition-filter=false</code><ul>
|
||||
<li>[Optional] If set to true, queries over this table require a partition filter that can be used for partition elimination to be specified. Note that this field should only be true when creating a permanent external table or querying a temporary external table. Hive-partitioned loads with requirePartitionFilter explicitly set to true will fail.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>source-uri-prefix=dolores</code></p>
|
||||
<p><code>source-uri-prefix=sanctus</code></p>
|
||||
<ul>
|
||||
<li>[Optional] When hive partition detection is requested, a common prefix for all source uris should be supplied. The prefix must end immediately before the partition key encoding begins. For example, consider files following this data layout. gs://bucket/path_to_table/dt=2019-01-01/country=BR/id=7/file.avro gs://bucket/path_to_table/dt=2018-12-31/country=CA/id=3/file.avro When hive partitioning is requested with either AUTO or STRINGS detection, the common prefix can be either of gs://bucket/path_to_table or gs://bucket/path_to_table/ (trailing slash does not matter).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. ignore-unknown-values=false</code></p>
|
||||
<p><code>.. ignore-unknown-values=true</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Indicates if BigQuery should allow extra values that are not represented in the table schema. If true, the extra values are ignored. If false, records with extra columns are treated as bad records, and if there are too many bad records, an invalid error is returned in the job result. The default value is false. The sourceFormat property determines what BigQuery treats as an extra value: CSV: Trailing columns JSON: Named values that don't match any column names Google Cloud Bigtable: This setting is ignored. Google Cloud Datastore backups: This setting is ignored. Avro: This setting is ignored.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>max-bad-records=93</code><ul>
|
||||
<li><code>max-bad-records=79</code><ul>
|
||||
<li>[Optional] The maximum number of bad records that BigQuery can ignore when reading data. If the number of bad records exceeds this value, an invalid error is returned in the job result. This is only valid for CSV, JSON, and Google Sheets. The default value is 0, which requires that all records are valid. This setting is ignored for Google Cloud Bigtable, Google Cloud Datastore backups and Avro formats.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>parquet-options enable-list-inference=false</code><ul>
|
||||
<li><code>parquet-options enable-list-inference=true</code><ul>
|
||||
<li>[Optional] Indicates whether to use schema inference specifically for Parquet LIST logical type.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>enum-as-string=false</code></p>
|
||||
<p><code>enum-as-string=true</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Indicates whether to infer Parquet ENUM logical type as STRING instead of BYTES by default.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. source-format=magna</code></p>
|
||||
<p><code>.. source-format=eirmod</code></p>
|
||||
<ul>
|
||||
<li>[Required] The data format. For CSV files, specify "CSV". For Google sheets, specify "GOOGLE_SHEETS". For newline-delimited JSON, specify "NEWLINE_DELIMITED_JSON". For Avro files, specify "AVRO". For Google Cloud Datastore backups, specify "DATASTORE_BACKUP". [Beta] For Google Cloud Bigtable, specify "BIGTABLE".</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>source-uris=no</code></p>
|
||||
<p><code>source-uris=vero</code></p>
|
||||
<ul>
|
||||
<li>[Required] The fully-qualified URIs that point to your data in Google Cloud. For Google Cloud Storage URIs: Each URI can contain one '<em>' wildcard character and it must come after the 'bucket' name. Size limits related to load jobs apply to external data sources. For Google Cloud Bigtable URIs: Exactly one URI can be specified and it has be a fully specified and valid HTTPS URL for a Google Cloud Bigtable table. For Google Cloud Datastore backups, exactly one URI can be specified. Also, the '</em>' wildcard character is not allowed.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. friendly-name=gubergren</code></p>
|
||||
<p><code>.. friendly-name=voluptua.</code></p>
|
||||
<ul>
|
||||
<li>[Optional] A descriptive name for this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>id=erat</code><ul>
|
||||
<li><code>id=sea</code><ul>
|
||||
<li>[Output-only] An opaque ID uniquely identifying the table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>kind=aliquyam</code><ul>
|
||||
<li><code>kind=ipsum</code><ul>
|
||||
<li>[Output-only] The type of the resource.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>labels=key=consetetur</code><ul>
|
||||
<li><code>labels=key=sea</code><ul>
|
||||
<li>The labels associated with this table. You can use these to organize and group your tables. Label keys and values can be no longer than 63 characters, can only contain lowercase letters, numeric characters, underscores and dashes. International characters are allowed. Label values are optional. Label keys must start with a letter and each label in the list must have a different key.</li>
|
||||
<li>the value will be associated with the given <code>key</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>last-modified-time=ea</code><ul>
|
||||
<li><code>last-modified-time=et</code><ul>
|
||||
<li>[Output-only] The time when this table was last modified, in milliseconds since the epoch.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>location=lorem</code><ul>
|
||||
<li><code>location=gubergren</code><ul>
|
||||
<li>[Output-only] The geographic location where the table resides. This value is inherited from the dataset.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -634,165 +664,169 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>[Optional] [TrustedTester] Enable automatic refresh of the materialized view when the base table is updated. The default value is "true".</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>last-refresh-time=justo</code><ul>
|
||||
<li><code>last-refresh-time=takimata</code><ul>
|
||||
<li>[Output-only] [TrustedTester] The time when this materialized view was last modified, in milliseconds since the epoch.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>query=lorem</code><ul>
|
||||
<li><code>query=duo</code><ul>
|
||||
<li>[Required] A query whose result is persisted.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>refresh-interval-ms=labore</code></p>
|
||||
<p><code>refresh-interval-ms=tempor</code></p>
|
||||
<ul>
|
||||
<li>[Optional] [TrustedTester] The maximum frequency at which this materialized view will be refreshed. The default value is "1800000" (30 minutes).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..model.model-options labels=gubergren</code></p>
|
||||
<p><code>..model.model-options labels=clita</code></p>
|
||||
<ul>
|
||||
<li>No description provided.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>loss-type=vero</code><ul>
|
||||
<li><code>loss-type=sed</code><ul>
|
||||
<li>No description provided.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>model-type=ea</code></p>
|
||||
<p><code>model-type=no</code></p>
|
||||
<ul>
|
||||
<li>No description provided.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>... num-bytes=sed</code></p>
|
||||
<p><code>... num-bytes=stet</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] The size of this table in bytes, excluding any data in the streaming buffer.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>num-long-term-bytes=sanctus</code><ul>
|
||||
<li><code>num-long-term-bytes=sea</code><ul>
|
||||
<li>[Output-only] The number of bytes in the table that are considered "long-term storage".</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>num-physical-bytes=labore</code><ul>
|
||||
<li><code>num-physical-bytes=clita</code><ul>
|
||||
<li>[Output-only] [TrustedTester] The physical size of this table in bytes, excluding any data in the streaming buffer. This includes compression and storage used for time travel.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>num-rows=amet</code><ul>
|
||||
<li><code>num-rows=consetetur</code><ul>
|
||||
<li>[Output-only] The number of rows of data in this table, excluding any data in the streaming buffer.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>range-partitioning field=et</code><ul>
|
||||
<li><code>range-partitioning field=dolores</code><ul>
|
||||
<li>[TrustedTester] [Required] The table is partitioned by this field. The field must be a top-level NULLABLE/REQUIRED field. The only supported type is INTEGER/INT64.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>range end=dolore</code><ul>
|
||||
<li><code>range end=sit</code><ul>
|
||||
<li>[TrustedTester] [Required] The end of range partitioning, exclusive.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>interval=voluptua.</code><ul>
|
||||
<li><code>interval=sea</code><ul>
|
||||
<li>[TrustedTester] [Required] The width of each interval.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>start=sit</code></p>
|
||||
<p><code>start=sanctus</code></p>
|
||||
<ul>
|
||||
<li>[TrustedTester] [Required] The start of range partitioning, inclusive.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>... require-partition-filter=true</code></p>
|
||||
<p><code>... require-partition-filter=false</code></p>
|
||||
<ul>
|
||||
<li>[Optional] If set to true, queries over this table require a partition filter that can be used for partition elimination to be specified.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>self-link=eirmod</code><ul>
|
||||
<li><code>self-link=dolores</code><ul>
|
||||
<li>[Output-only] A URL that can be used to access this resource again.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>snapshot-definition.base-table-reference dataset-id=vero</code><ul>
|
||||
<li><code>snapshot-definition.base-table-reference dataset-id=aliquyam</code><ul>
|
||||
<li>[Required] The ID of the dataset containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>project-id=voluptua.</code><ul>
|
||||
<li><code>project-id=dolor</code><ul>
|
||||
<li>[Required] The ID of the project containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>table-id=sea</code></p>
|
||||
<p><code>table-id=vero</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the table. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 1,024 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. snapshot-time=ipsum</code></p>
|
||||
<p><code>.. snapshot-time=ea</code></p>
|
||||
<ul>
|
||||
<li>[Required] The time at which the base table was snapshot.</li>
|
||||
<li>[Required] The time at which the base table was snapshot. This value is reported in the JSON response using RFC3339 format.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..streaming-buffer estimated-bytes=sea</code></p>
|
||||
<p><code>..streaming-buffer estimated-bytes=magna</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] A lower-bound estimate of the number of bytes currently in the streaming buffer.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>estimated-rows=et</code><ul>
|
||||
<li><code>estimated-rows=rebum.</code><ul>
|
||||
<li>[Output-only] A lower-bound estimate of the number of rows currently in the streaming buffer.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>oldest-entry-time=gubergren</code></p>
|
||||
<p><code>oldest-entry-time=amet</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] Contains the timestamp of the oldest entry in the streaming buffer, in milliseconds since the epoch, if the streaming buffer is available.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..table-reference dataset-id=dolore</code></p>
|
||||
<p><code>..table-reference dataset-id=sea</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the dataset containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>project-id=ea</code><ul>
|
||||
<li><code>project-id=sadipscing</code><ul>
|
||||
<li>[Required] The ID of the project containing this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>table-id=elitr</code></p>
|
||||
<p><code>table-id=dolore</code></p>
|
||||
<ul>
|
||||
<li>[Required] The ID of the table. The ID must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_). The maximum length is 1,024 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..time-partitioning expiration-ms=takimata</code></p>
|
||||
<p><code>..time-partitioning expiration-ms=amet</code></p>
|
||||
<ul>
|
||||
<li>[Optional] Number of milliseconds for which to keep the storage for partitions in the table. The storage in a partition will have an expiration time of its partition time plus this value.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>field=duo</code><ul>
|
||||
<li><code>field=invidunt</code><ul>
|
||||
<li>[Beta] [Optional] If not set, the table is partitioned by pseudo column, referenced via either '_PARTITIONTIME' as TIMESTAMP type, or '_PARTITIONDATE' as DATE type. If field is specified, the table is instead partitioned by this field. The field must be a top-level TIMESTAMP or DATE field. Its mode must be NULLABLE or REQUIRED.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>require-partition-filter=false</code><ul>
|
||||
<li><code>require-partition-filter=true</code><ul>
|
||||
<li>No description provided.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>type=clita</code></p>
|
||||
<p><code>type=dolores</code></p>
|
||||
<ul>
|
||||
<li>[Required] The supported types are DAY, HOUR, MONTH, and YEAR, which will generate one partition per day, hour, month, and year, respectively. When the type is not specified, the default behavior is DAY.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. type=sed</code></p>
|
||||
<p><code>.. type=diam</code></p>
|
||||
<ul>
|
||||
<li>[Output-only] Describes the table type. The following values are supported: TABLE: A normal BigQuery table. VIEW: A virtual table defined by a SQL query. SNAPSHOT: An immutable, read-only table that is a copy of another table. [TrustedTester] MATERIALIZED_VIEW: SQL query whose result is persisted. EXTERNAL: A table that references data stored in an external storage system, such as Google Cloud Storage. The default value is TABLE.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>view query=no</code><ul>
|
||||
<li><code>view query=sanctus</code><ul>
|
||||
<li>[Required] A query that BigQuery executes when the view is referenced.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>use-explicit-column-names=false</code><ul>
|
||||
<li>True if the column names are explicitly specified. For example by using the 'CREATE VIEW v(c1, c2) AS ...' syntax. Can only be set using BigQuery's standard SQL: https://cloud.google.com/bigquery/sql-reference/</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>use-legacy-sql=true</code><ul>
|
||||
<li>Specifies whether to use BigQuery's legacy SQL for this view. The default value is true. If set to false, the view will use BigQuery's standard SQL: https://cloud.google.com/bigquery/sql-reference/ Queries and views that reference this view must use the same flag value.</li>
|
||||
</ul>
|
||||
@@ -817,6 +851,16 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<h1 id="optional-method-properties">Optional Method Properties</h1>
|
||||
<p>You may set the following properties to further configure the call. Please note that <code>-p</code> is followed by one
|
||||
or more key-value-pairs, and is called like this <code>-p k1=v1 k2=v2</code> even though the listing below repeats the
|
||||
<code>-p</code> for completeness.</p>
|
||||
<ul>
|
||||
<li><strong>-p autodetect-schema=boolean</strong><ul>
|
||||
<li>When true will autodetect schema, else will keep original schema</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<h1 id="optional-general-properties">Optional General Properties</h1>
|
||||
<p>The following properties can configure any call, and are not specific to this method.</p>
|
||||
<ul>
|
||||
|
||||
Reference in New Issue
Block a user