@maxim_mazurok/gapi.client.bigquery-v2 0.0.20250427 → 0.0.20250511

package/index.d.ts

@@ -9,7 +9,7 @@
 // This file was generated by https://github.com/Maxim-Mazurok/google-api-typings-generator. Please do not edit it manually.
 // In case of any problems please post issue to https://github.com/Maxim-Mazurok/google-api-typings-generator
 // Generated from: https://bigquery.googleapis.com/$discovery/rest?version=v2
-// Revision: 20250427
+// Revision: 20250511
 
 /// <reference types="gapi.client" />
 
@@ -491,6 +491,8 @@ declare namespace gapi.client {
       datasets?: Array<{
         /** The dataset reference. Use this property to access specific parts of the dataset's ID, such as project ID or dataset ID. */
         datasetReference?: DatasetReference;
+        /** Output only. Reference to a read-only external dataset defined in data catalogs outside of BigQuery. Filled out when the dataset type is EXTERNAL. */
+        externalDatasetReference?: ExternalDatasetReference;
         /** An alternate name for the dataset. The friendly name is purely decorative in nature. */
         friendlyName?: string;
         /** The fully-qualified, unique, opaque ID of the dataset. */
@@ -1168,7 +1170,7 @@ declare namespace gapi.client {
       timeZone?: string;
       /** 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). */
       useAvroLogicalTypes?: boolean;
-      /** 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 data, removes the constraints and uses the schema from the load job. * 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. */
+      /** 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 data, removes the constraints and uses the schema from the load job. * WRITE_TRUNCATE_DATA: If the table already exists, BigQuery overwrites the data, but keeps the constraints and schema of the existing table. * 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. */
       writeDisposition?: string;
     }
     interface JobConfigurationQuery {
@@ -1224,7 +1226,7 @@ declare namespace gapi.client {
       useQueryCache?: boolean;
       /** Describes user-defined function resources used in the query. */
       userDefinedFunctionResources?: UserDefinedFunctionResource[];
-      /** 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 data, removes the constraints, and uses the schema from the query result. * 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. */
+      /** 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 data, removes the constraints, and uses the schema from the query result. * WRITE_TRUNCATE_DATA: If the table already exists, BigQuery overwrites the data, but keeps the constraints and schema of the existing table. * 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. */
       writeDisposition?: string;
       /** Optional. This is only supported for a SELECT query using a temporary table. If set, the query is allowed to write results incrementally to the temporary result table. This may incur a performance penalty. This option cannot be used with Legacy SQL. This feature is not yet available. */
       writeIncrementalResults?: boolean;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maxim_mazurok/gapi.client.bigquery-v2",
-  "version": "0.0.20250427",
+  "version": "0.0.20250511",
   "description": "TypeScript typings for BigQuery API v2",
   "repository": {
     "type": "git",