Skip to content
Permalink
Browse files
chore: Update discovery artifacts (#1389)
## Discovery Artifact Change Summary:
feat(bigquery): update the api 086d714
  • Loading branch information
yoshi-code-bot committed May 30, 2021
1 parent 38664e8 commit 508c39fa665c901d9d754aa31dc9d1af45469ec4
@@ -346,6 +346,7 @@ <h3>Method Details</h3>
&quot;type&quot;: &quot;A String&quot;, # [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.
&quot;view&quot;: { # [Optional] The view definition.
&quot;query&quot;: &quot;A String&quot;, # [Required] A query that BigQuery executes when the view is referenced.
&quot;useExplicitColumnNames&quot;: True or False, # True if the column names are explicitly specified. For example by using the &#x27;CREATE VIEW v(c1, c2) AS ...&#x27; syntax. Can only be set using BigQuery&#x27;s standard SQL: https://cloud.google.com/bigquery/sql-reference/
&quot;useLegacySql&quot;: True or False, # Specifies whether to use BigQuery&#x27;s legacy SQL for this view. The default value is true. If set to false, the view will use BigQuery&#x27;s standard SQL: https://cloud.google.com/bigquery/sql-reference/ Queries and views that reference this view must use the same flag value.
&quot;userDefinedFunctionResources&quot;: [ # Describes user-defined function resources used in the query.
{ # This is used for defining User Defined Function (UDF) resources only when using legacy SQL. Users of Standard SQL should leverage either DDL (e.g. CREATE [TEMPORARY] FUNCTION ... ) or the Routines API to define UDF resources. For additional information on migrating, see: https://cloud.google.com/bigquery/docs/reference/standard-sql/migrating-from-legacy-sql#differences_in_user-defined_javascript_functions
@@ -628,6 +629,7 @@ <h3>Method Details</h3>
&quot;type&quot;: &quot;A String&quot;, # [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.
&quot;view&quot;: { # [Optional] The view definition.
&quot;query&quot;: &quot;A String&quot;, # [Required] A query that BigQuery executes when the view is referenced.
&quot;useExplicitColumnNames&quot;: True or False, # True if the column names are explicitly specified. For example by using the &#x27;CREATE VIEW v(c1, c2) AS ...&#x27; syntax. Can only be set using BigQuery&#x27;s standard SQL: https://cloud.google.com/bigquery/sql-reference/
&quot;useLegacySql&quot;: True or False, # Specifies whether to use BigQuery&#x27;s legacy SQL for this view. The default value is true. If set to false, the view will use BigQuery&#x27;s standard SQL: https://cloud.google.com/bigquery/sql-reference/ Queries and views that reference this view must use the same flag value.
&quot;userDefinedFunctionResources&quot;: [ # Describes user-defined function resources used in the query.
{ # This is used for defining User Defined Function (UDF) resources only when using legacy SQL. Users of Standard SQL should leverage either DDL (e.g. CREATE [TEMPORARY] FUNCTION ... ) or the Routines API to define UDF resources. For additional information on migrating, see: https://cloud.google.com/bigquery/docs/reference/standard-sql/migrating-from-legacy-sql#differences_in_user-defined_javascript_functions
@@ -851,6 +853,7 @@ <h3>Method Details</h3>
&quot;type&quot;: &quot;A String&quot;, # [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.
&quot;view&quot;: { # [Optional] The view definition.
&quot;query&quot;: &quot;A String&quot;, # [Required] A query that BigQuery executes when the view is referenced.
&quot;useExplicitColumnNames&quot;: True or False, # True if the column names are explicitly specified. For example by using the &#x27;CREATE VIEW v(c1, c2) AS ...&#x27; syntax. Can only be set using BigQuery&#x27;s standard SQL: https://cloud.google.com/bigquery/sql-reference/
&quot;useLegacySql&quot;: True or False, # Specifies whether to use BigQuery&#x27;s legacy SQL for this view. The default value is true. If set to false, the view will use BigQuery&#x27;s standard SQL: https://cloud.google.com/bigquery/sql-reference/ Queries and views that reference this view must use the same flag value.
&quot;userDefinedFunctionResources&quot;: [ # Describes user-defined function resources used in the query.
{ # This is used for defining User Defined Function (UDF) resources only when using legacy SQL. Users of Standard SQL should leverage either DDL (e.g. CREATE [TEMPORARY] FUNCTION ... ) or the Routines API to define UDF resources. For additional information on migrating, see: https://cloud.google.com/bigquery/docs/reference/standard-sql/migrating-from-legacy-sql#differences_in_user-defined_javascript_functions
@@ -1157,6 +1160,7 @@ <h3>Method Details</h3>
&quot;type&quot;: &quot;A String&quot;, # [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.
&quot;view&quot;: { # [Optional] The view definition.
&quot;query&quot;: &quot;A String&quot;, # [Required] A query that BigQuery executes when the view is referenced.
&quot;useExplicitColumnNames&quot;: True or False, # True if the column names are explicitly specified. For example by using the &#x27;CREATE VIEW v(c1, c2) AS ...&#x27; syntax. Can only be set using BigQuery&#x27;s standard SQL: https://cloud.google.com/bigquery/sql-reference/
&quot;useLegacySql&quot;: True or False, # Specifies whether to use BigQuery&#x27;s legacy SQL for this view. The default value is true. If set to false, the view will use BigQuery&#x27;s standard SQL: https://cloud.google.com/bigquery/sql-reference/ Queries and views that reference this view must use the same flag value.
&quot;userDefinedFunctionResources&quot;: [ # Describes user-defined function resources used in the query.
{ # This is used for defining User Defined Function (UDF) resources only when using legacy SQL. Users of Standard SQL should leverage either DDL (e.g. CREATE [TEMPORARY] FUNCTION ... ) or the Routines API to define UDF resources. For additional information on migrating, see: https://cloud.google.com/bigquery/docs/reference/standard-sql/migrating-from-legacy-sql#differences_in_user-defined_javascript_functions
@@ -1380,6 +1384,7 @@ <h3>Method Details</h3>
&quot;type&quot;: &quot;A String&quot;, # [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.
&quot;view&quot;: { # [Optional] The view definition.
&quot;query&quot;: &quot;A String&quot;, # [Required] A query that BigQuery executes when the view is referenced.
&quot;useExplicitColumnNames&quot;: True or False, # True if the column names are explicitly specified. For example by using the &#x27;CREATE VIEW v(c1, c2) AS ...&#x27; syntax. Can only be set using BigQuery&#x27;s standard SQL: https://cloud.google.com/bigquery/sql-reference/
&quot;useLegacySql&quot;: True or False, # Specifies whether to use BigQuery&#x27;s legacy SQL for this view. The default value is true. If set to false, the view will use BigQuery&#x27;s standard SQL: https://cloud.google.com/bigquery/sql-reference/ Queries and views that reference this view must use the same flag value.
&quot;userDefinedFunctionResources&quot;: [ # Describes user-defined function resources used in the query.
{ # This is used for defining User Defined Function (UDF) resources only when using legacy SQL. Users of Standard SQL should leverage either DDL (e.g. CREATE [TEMPORARY] FUNCTION ... ) or the Routines API to define UDF resources. For additional information on migrating, see: https://cloud.google.com/bigquery/docs/reference/standard-sql/migrating-from-legacy-sql#differences_in_user-defined_javascript_functions
@@ -1718,6 +1723,7 @@ <h3>Method Details</h3>
&quot;type&quot;: &quot;A String&quot;, # [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.
&quot;view&quot;: { # [Optional] The view definition.
&quot;query&quot;: &quot;A String&quot;, # [Required] A query that BigQuery executes when the view is referenced.
&quot;useExplicitColumnNames&quot;: True or False, # True if the column names are explicitly specified. For example by using the &#x27;CREATE VIEW v(c1, c2) AS ...&#x27; syntax. Can only be set using BigQuery&#x27;s standard SQL: https://cloud.google.com/bigquery/sql-reference/
&quot;useLegacySql&quot;: True or False, # Specifies whether to use BigQuery&#x27;s legacy SQL for this view. The default value is true. If set to false, the view will use BigQuery&#x27;s standard SQL: https://cloud.google.com/bigquery/sql-reference/ Queries and views that reference this view must use the same flag value.
&quot;userDefinedFunctionResources&quot;: [ # Describes user-defined function resources used in the query.
{ # This is used for defining User Defined Function (UDF) resources only when using legacy SQL. Users of Standard SQL should leverage either DDL (e.g. CREATE [TEMPORARY] FUNCTION ... ) or the Routines API to define UDF resources. For additional information on migrating, see: https://cloud.google.com/bigquery/docs/reference/standard-sql/migrating-from-legacy-sql#differences_in_user-defined_javascript_functions
@@ -1941,6 +1947,7 @@ <h3>Method Details</h3>
&quot;type&quot;: &quot;A String&quot;, # [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.
&quot;view&quot;: { # [Optional] The view definition.
&quot;query&quot;: &quot;A String&quot;, # [Required] A query that BigQuery executes when the view is referenced.
&quot;useExplicitColumnNames&quot;: True or False, # True if the column names are explicitly specified. For example by using the &#x27;CREATE VIEW v(c1, c2) AS ...&#x27; syntax. Can only be set using BigQuery&#x27;s standard SQL: https://cloud.google.com/bigquery/sql-reference/
&quot;useLegacySql&quot;: True or False, # Specifies whether to use BigQuery&#x27;s legacy SQL for this view. The default value is true. If set to false, the view will use BigQuery&#x27;s standard SQL: https://cloud.google.com/bigquery/sql-reference/ Queries and views that reference this view must use the same flag value.
&quot;userDefinedFunctionResources&quot;: [ # Describes user-defined function resources used in the query.
{ # This is used for defining User Defined Function (UDF) resources only when using legacy SQL. Users of Standard SQL should leverage either DDL (e.g. CREATE [TEMPORARY] FUNCTION ... ) or the Routines API to define UDF resources. For additional information on migrating, see: https://cloud.google.com/bigquery/docs/reference/standard-sql/migrating-from-legacy-sql#differences_in_user-defined_javascript_functions
@@ -518,6 +518,10 @@ <h3>Method Details</h3>
},
},
&quot;nodeIpv4CidrSize&quot;: 42, # [Output only] The size of the address space on each node for hosting containers. This is provisioned from within the `container_ipv4_cidr` range. This field will only be set when cluster is in route-based network mode.
&quot;nodePoolDefaults&quot;: { # Subset of Nodepool message that has defaults. # Default NodePool settings for the entire cluster. These settings are overridden if specified on the specific NodePool object.
&quot;nodeConfigDefaults&quot;: { # Subset of NodeConfig message that has defaults. # Subset of NodeConfig message that has defaults.
},
},
&quot;nodePools&quot;: [ # The node pools associated with this cluster. This field should not be set if &quot;node_config&quot; or &quot;initial_node_count&quot; are specified.
{ # NodePool contains the name and configuration for a cluster&#x27;s node pool. Node pools are a set of nodes (i.e. VM&#x27;s), with a common configuration and specification, under the control of the cluster master. They may have a set of Kubernetes labels applied to them, which may be used to reference them during pod scheduling. They may also be resized up or down, to accommodate the workload.
&quot;autoscaling&quot;: { # NodePoolAutoscaling contains information required by cluster autoscaler to adjust the size of the node pool to the current cluster usage. # Autoscaler configuration for this NodePool. Autoscaler is enabled only if a valid configuration is present.
@@ -1138,6 +1142,10 @@ <h3>Method Details</h3>
},
},
&quot;nodeIpv4CidrSize&quot;: 42, # [Output only] The size of the address space on each node for hosting containers. This is provisioned from within the `container_ipv4_cidr` range. This field will only be set when cluster is in route-based network mode.
&quot;nodePoolDefaults&quot;: { # Subset of Nodepool message that has defaults. # Default NodePool settings for the entire cluster. These settings are overridden if specified on the specific NodePool object.
&quot;nodeConfigDefaults&quot;: { # Subset of NodeConfig message that has defaults. # Subset of NodeConfig message that has defaults.
},
},
&quot;nodePools&quot;: [ # The node pools associated with this cluster. This field should not be set if &quot;node_config&quot; or &quot;initial_node_count&quot; are specified.
{ # NodePool contains the name and configuration for a cluster&#x27;s node pool. Node pools are a set of nodes (i.e. VM&#x27;s), with a common configuration and specification, under the control of the cluster master. They may have a set of Kubernetes labels applied to them, which may be used to reference them during pod scheduling. They may also be resized up or down, to accommodate the workload.
&quot;autoscaling&quot;: { # NodePoolAutoscaling contains information required by cluster autoscaler to adjust the size of the node pool to the current cluster usage. # Autoscaler configuration for this NodePool. Autoscaler is enabled only if a valid configuration is present.
@@ -1661,6 +1669,10 @@ <h3>Method Details</h3>
},
},
&quot;nodeIpv4CidrSize&quot;: 42, # [Output only] The size of the address space on each node for hosting containers. This is provisioned from within the `container_ipv4_cidr` range. This field will only be set when cluster is in route-based network mode.
&quot;nodePoolDefaults&quot;: { # Subset of Nodepool message that has defaults. # Default NodePool settings for the entire cluster. These settings are overridden if specified on the specific NodePool object.
&quot;nodeConfigDefaults&quot;: { # Subset of NodeConfig message that has defaults. # Subset of NodeConfig message that has defaults.
},
},
&quot;nodePools&quot;: [ # The node pools associated with this cluster. This field should not be set if &quot;node_config&quot; or &quot;initial_node_count&quot; are specified.
{ # NodePool contains the name and configuration for a cluster&#x27;s node pool. Node pools are a set of nodes (i.e. VM&#x27;s), with a common configuration and specification, under the control of the cluster master. They may have a set of Kubernetes labels applied to them, which may be used to reference them during pod scheduling. They may also be resized up or down, to accommodate the workload.
&quot;autoscaling&quot;: { # NodePoolAutoscaling contains information required by cluster autoscaler to adjust the size of the node pool to the current cluster usage. # Autoscaler configuration for this NodePool. Autoscaler is enabled only if a valid configuration is present.
@@ -142,6 +142,21 @@ <h3>Method Details</h3>
&quot;validNodeVersions&quot;: [ # List of valid node upgrade target versions, in descending order.
&quot;A String&quot;,
],
&quot;windowsVersionMaps&quot;: { # Maps of Kubernetes version and supported Windows server versions.
&quot;a_key&quot;: { # Windows server versions.
&quot;windowsVersions&quot;: [ # List of Windows server versions.
{ # Windows server version.
&quot;imageType&quot;: &quot;A String&quot;, # Windows server image type
&quot;osVersion&quot;: &quot;A String&quot;, # Windows server build number
&quot;supportEndDate&quot;: { # Represents a whole or partial calendar date, such as a birthday. The time of day and time zone are either specified elsewhere or are insignificant. The date is relative to the Gregorian Calendar. This can represent one of the following: * A full date, with non-zero year, month, and day values * A month and day value, with a zero year, such as an anniversary * A year on its own, with zero month and day values * A year and month value, with a zero day, such as a credit card expiration date Related types are google.type.TimeOfDay and `google.protobuf.Timestamp`. # Mainstream support end date
&quot;day&quot;: 42, # Day of a month. Must be from 1 to 31 and valid for the year and month, or 0 to specify a year by itself or a year and month where the day isn&#x27;t significant.
&quot;month&quot;: 42, # Month of a year. Must be from 1 to 12, or 0 to specify a year without a month and day.
&quot;year&quot;: 42, # Year of the date. Must be from 1 to 9999, or 0 to specify a date without a year.
},
},
],
},
},
}</pre>
</div>

0 comments on commit 508c39f

Please sign in to comment.