@googleapis/spanner 9.1.0 → 9.1.1

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## [9.1.1](https://github.com/googleapis/google-api-nodejs-client/compare/spanner-v9.1.0...spanner-v9.1.1) (2025-07-15)
+
+
+### Bug Fixes
+
+* **spanner:** update the API ([d77e9d5](https://github.com/googleapis/google-api-nodejs-client/commit/d77e9d510f53a8fdccd63451191482343ecfdb59))
+
 ## [9.1.0](https://github.com/googleapis/google-api-nodejs-client/compare/spanner-v9.0.0...spanner-v9.1.0) (2025-07-08)
 
 

package/build/v1.d.ts

@@ -390,7 +390,7 @@ export declare namespace spanner_v1 {
      */
     export interface Schema$BatchWriteRequest {
         /**
-         * Optional. When `exclude_txn_from_change_streams` is set to `true`: * Modifications from all transactions in this batch write operation are not be recorded in change streams with DDL option `allow_txn_exclusion=true` that are tracking columns modified by these transactions. * Modifications from all transactions in this batch write operation are recorded in change streams with DDL option `allow_txn_exclusion=false or not set` that are tracking columns modified by these transactions. When `exclude_txn_from_change_streams` is set to `false` or not set, Modifications from all transactions in this batch write operation are recorded in all change streams that are tracking columns modified by these transactions.
+         * Optional. If you don't set the `exclude_txn_from_change_streams` option or if it's set to `false`, then any change streams monitoring columns modified by transactions will capture the updates made within that transaction.
          */
         excludeTxnFromChangeStreams?: boolean | null;
         /**
@@ -955,11 +955,11 @@ export declare namespace spanner_v1 {
      */
     export interface Schema$DatabaseMoveConfig {
         /**
-         * Required. The unique identifier of the database resource in the Instance. For example if the database uri is projects/foo/instances/bar/databases/baz, the id to supply here is baz.
+         * Required. The unique identifier of the database resource in the Instance. For example, if the database uri is `projects/foo/instances/bar/databases/baz`, then the id to supply here is baz.
          */
         databaseId?: string | null;
         /**
-         * Optional. Encryption configuration to be used for the database in target configuration. Should be specified for every database which currently uses CMEK encryption. If a database currently uses GOOGLE_MANAGED encryption and a target encryption config is not specified, it defaults to GOOGLE_MANAGED. If a database currently uses Google-managed encryption and a target encryption config is specified, the request is rejected. If a database currently uses CMEK encryption, a target encryption config must be specified. You cannot move a CMEK database to a Google-managed encryption database by MoveInstance.
+         * Optional. Encryption configuration to be used for the database in the target configuration. The encryption configuration must be specified for every database which currently uses CMEK encryption. If a database currently uses Google-managed encryption and a target encryption configuration is not specified, then the database defaults to Google-managed encryption. If a database currently uses Google-managed encryption and a target CMEK encryption is specified, the request is rejected. If a database currently uses CMEK encryption, then a target encryption configuration must be specified. You can't move a CMEK database to a Google-managed encryption database using the MoveInstance API.
          */
         encryptionConfig?: Schema$InstanceEncryptionConfig;
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@googleapis/spanner",
-  "version": "9.1.0",
+  "version": "9.1.1",
   "description": "spanner",
   "main": "build/index.js",
   "types": "build/index.d.ts",

package/v1.ts

@@ -439,7 +439,7 @@ export namespace spanner_v1 {
    */
   export interface Schema$BatchWriteRequest {
     /**
-     * Optional. When `exclude_txn_from_change_streams` is set to `true`: * Modifications from all transactions in this batch write operation are not be recorded in change streams with DDL option `allow_txn_exclusion=true` that are tracking columns modified by these transactions. * Modifications from all transactions in this batch write operation are recorded in change streams with DDL option `allow_txn_exclusion=false or not set` that are tracking columns modified by these transactions. When `exclude_txn_from_change_streams` is set to `false` or not set, Modifications from all transactions in this batch write operation are recorded in all change streams that are tracking columns modified by these transactions.
+     * Optional. If you don't set the `exclude_txn_from_change_streams` option or if it's set to `false`, then any change streams monitoring columns modified by transactions will capture the updates made within that transaction.
      */
     excludeTxnFromChangeStreams?: boolean | null;
     /**
@@ -1004,11 +1004,11 @@ export namespace spanner_v1 {
    */
   export interface Schema$DatabaseMoveConfig {
     /**
-     * Required. The unique identifier of the database resource in the Instance. For example if the database uri is projects/foo/instances/bar/databases/baz, the id to supply here is baz.
+     * Required. The unique identifier of the database resource in the Instance. For example, if the database uri is `projects/foo/instances/bar/databases/baz`, then the id to supply here is baz.
      */
     databaseId?: string | null;
     /**
-     * Optional. Encryption configuration to be used for the database in target configuration. Should be specified for every database which currently uses CMEK encryption. If a database currently uses GOOGLE_MANAGED encryption and a target encryption config is not specified, it defaults to GOOGLE_MANAGED. If a database currently uses Google-managed encryption and a target encryption config is specified, the request is rejected. If a database currently uses CMEK encryption, a target encryption config must be specified. You cannot move a CMEK database to a Google-managed encryption database by MoveInstance.
+     * Optional. Encryption configuration to be used for the database in the target configuration. The encryption configuration must be specified for every database which currently uses CMEK encryption. If a database currently uses Google-managed encryption and a target encryption configuration is not specified, then the database defaults to Google-managed encryption. If a database currently uses Google-managed encryption and a target CMEK encryption is specified, the request is rejected. If a database currently uses CMEK encryption, then a target encryption configuration must be specified. You can't move a CMEK database to a Google-managed encryption database using the MoveInstance API.
      */
     encryptionConfig?: Schema$InstanceEncryptionConfig;
   }