Upgrade to latest API versions + code regen

This commit is contained in:
Sebastian Thiel
2017-12-12 14:30:54 +01:00
parent dc30217711
commit 357a0e650e
776 changed files with 356718 additions and 104442 deletions

View File

@@ -1,11 +1,11 @@
{
"kind": "discovery#restDescription",
"etag": "\"YWOzh2SDasdU84ArJnpYek-OMdg/6KmyniE-DVTht1WBAWvasoVbs7Y\"",
"etag": "\"YWOzh2SDasdU84ArJnpYek-OMdg/RHgdSKr7KDuh1e1sszGVdMKFPWE\"",
"discoveryVersion": "v1",
"id": "bigquery:v2",
"name": "bigquery",
"version": "v2",
"revision": "20170917",
"revision": "20171202",
"title": "BigQuery API",
"description": "A data platform for customers to create, manage, share and query data.",
"ownerDomain": "google.com",
@@ -413,6 +413,11 @@
"id": "ExplainQueryStage",
"type": "object",
"properties": {
"completedParallelInputs": {
"type": "string",
"description": "Number of parallel input segments completed.",
"format": "int64"
},
"computeMsAvg": {
"type": "string",
"description": "Milliseconds the average shard spent on CPU-bound tasks.",
@@ -442,6 +447,11 @@
"type": "string",
"description": "Human-readable name for stage."
},
"parallelInputs": {
"type": "string",
"description": "Number of parallel input segments to be processed.",
"format": "int64"
},
"readMsAvg": {
"type": "string",
"description": "Milliseconds the average shard spent reading input.",
@@ -897,7 +907,7 @@
},
"schemaUpdateOptions": {
"type": "array",
"description": "[Experimental] Allows the schema of the desitination 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.",
"description": "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.",
"items": {
"type": "string"
}
@@ -920,7 +930,7 @@
},
"timePartitioning": {
"$ref": "TimePartitioning",
"description": "[Experimental] If specified, configures time-based partitioning for the destination table."
"description": "If specified, configures time-based partitioning for the destination table."
},
"writeDisposition": {
"type": "string",
@@ -994,7 +1004,7 @@
},
"schemaUpdateOptions": {
"type": "array",
"description": "[Experimental] Allows the schema of the destination table to be updated as a side effect of the query job. 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.",
"description": "Allows the schema of the destination table to be updated as a side effect of the query job. 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.",
"items": {
"type": "string"
}
@@ -1008,7 +1018,7 @@
},
"timePartitioning": {
"$ref": "TimePartitioning",
"description": "[Experimental] If specified, configures time-based partitioning for the destination table."
"description": "If specified, configures time-based partitioning for the destination table."
},
"useLegacySql": {
"type": "boolean",
@@ -1205,6 +1215,19 @@
"type": "boolean",
"description": "[Output-only] Whether the query result was fetched from the query cache."
},
"ddlOperationPerformed": {
"type": "string",
"description": "[Output-only, Experimental] 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."
},
"ddlTargetTable": {
"$ref": "TableReference",
"description": "[Output-only, Experimental] The DDL target table. Present only for CREATE/DROP TABLE/VIEW queries."
},
"estimatedBytesProcessed": {
"type": "string",
"description": "[Output-only] The original estimate of bytes processed for the job.",
"format": "int64"
},
"numDmlAffectedRows": {
"type": "string",
"description": "[Output-only] The number of rows affected by a DML statement. Present only for DML statements INSERT, UPDATE or DELETE.",
@@ -1230,7 +1253,7 @@
},
"statementType": {
"type": "string",
"description": "[Output-only, Experimental] The type of query statement, if valid."
"description": "[Output-only, Experimental] 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 \"CREATE_TABLE\": CREATE [OR REPLACE] TABLE without AS SELECT. \"CREATE_TABLE_AS_SELECT\": CREATE [OR REPLACE] TABLE ... AS SELECT ... \"DROP_TABLE\": DROP TABLE query. \"CREATE_VIEW\": CREATE [OR REPLACE] VIEW ... AS SELECT ... \"DROP_VIEW\": DROP VIEW query."
},
"totalBytesBilled": {
"type": "string",
@@ -1712,7 +1735,7 @@
},
"timePartitioning": {
"$ref": "TimePartitioning",
"description": "[Experimental] If specified, configures time-based partitioning for this table."
"description": "If specified, configures time-based partitioning for this table."
},
"type": {
"type": "string",
@@ -1888,6 +1911,16 @@
"items": {
"type": "object",
"properties": {
"creationTime": {
"type": "string",
"description": "The time when this table was created, in milliseconds since the epoch.",
"format": "int64"
},
"expirationTime": {
"type": "string",
"description": "[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.",
"format": "int64"
},
"friendlyName": {
"type": "string",
"description": "The user-friendly name for this table."
@@ -1914,7 +1947,7 @@
},
"timePartitioning": {
"$ref": "TimePartitioning",
"description": "[Experimental] The time-based partitioning for this table."
"description": "The time-based partitioning for this table."
},
"type": {
"type": "string",