google-apis-spanner_v1 0.41.0 → 0.43.0

data/lib/google/apis/spanner_v1/classes.rb

@@ -105,8 +105,8 @@ module Google
       
         # Optional. A user-supplied tag associated with the split points. For example, "
         # initial_data_load", "special_event_1". Defaults to "CloudAddSplitPointsAPI" if
-        # not specified. The length of the tag must not exceed 50 characters,else will
-        # be trimmed. Only valid UTF8 characters are allowed.
+        # not specified. The length of the tag must not exceed 50 characters, or else it
+        # is trimmed. Only valid UTF8 characters are allowed.
         # Corresponds to the JSON property `initiator`
         # @return [String]
         attr_accessor :initiator
@@ -797,198 +797,7 @@ module Google
         # @return [Google::Apis::SpannerV1::Mutation]
         attr_accessor :mutation_key
       
-        # Transactions: Each session can have at most one active transaction at a time (
-        # note that standalone reads and queries use a transaction internally and do
-        # count towards the one transaction limit). After the active transaction is
-        # completed, the session can immediately be re-used for the next transaction. It
-        # is not necessary to create a new session for each transaction. Transaction
-        # modes: Cloud Spanner supports three transaction modes: 1. Locking read-write.
-        # This type of transaction is the only way to write data into Cloud Spanner.
-        # These transactions rely on pessimistic locking and, if necessary, two-phase
-        # commit. Locking read-write transactions may abort, requiring the application
-        # to retry. 2. Snapshot read-only. Snapshot read-only transactions provide
-        # guaranteed consistency across several reads, but do not allow writes. Snapshot
-        # read-only transactions can be configured to read at timestamps in the past, or
-        # configured to perform a strong read (where Spanner will select a timestamp
-        # such that the read is guaranteed to see the effects of all transactions that
-        # have committed before the start of the read). Snapshot read-only transactions
-        # do not need to be committed. Queries on change streams must be performed with
-        # the snapshot read-only transaction mode, specifying a strong read. See
-        # TransactionOptions.ReadOnly.strong for more details. 3. Partitioned DML. This
-        # type of transaction is used to execute a single Partitioned DML statement.
-        # Partitioned DML partitions the key space and runs the DML statement over each
-        # partition in parallel using separate, internal transactions that commit
-        # independently. Partitioned DML transactions do not need to be committed. For
-        # transactions that only read, snapshot read-only transactions provide simpler
-        # semantics and are almost always faster. In particular, read-only transactions
-        # do not take locks, so they do not conflict with read-write transactions. As a
-        # consequence of not taking locks, they also do not abort, so retry loops are
-        # not needed. Transactions may only read-write data in a single database. They
-        # may, however, read-write data in different tables within that database.
-        # Locking read-write transactions: Locking transactions may be used to
-        # atomically read-modify-write data anywhere in a database. This type of
-        # transaction is externally consistent. Clients should attempt to minimize the
-        # amount of time a transaction is active. Faster transactions commit with higher
-        # probability and cause less contention. Cloud Spanner attempts to keep read
-        # locks active as long as the transaction continues to do reads, and the
-        # transaction has not been terminated by Commit or Rollback. Long periods of
-        # inactivity at the client may cause Cloud Spanner to release a transaction's
-        # locks and abort it. Conceptually, a read-write transaction consists of zero or
-        # more reads or SQL statements followed by Commit. At any time before Commit,
-        # the client can send a Rollback request to abort the transaction. Semantics:
-        # Cloud Spanner can commit the transaction if all read locks it acquired are
-        # still valid at commit time, and it is able to acquire write locks for all
-        # writes. Cloud Spanner can abort the transaction for any reason. If a commit
-        # attempt returns `ABORTED`, Cloud Spanner guarantees that the transaction has
-        # not modified any user data in Cloud Spanner. Unless the transaction commits,
-        # Cloud Spanner makes no guarantees about how long the transaction's locks were
-        # held for. It is an error to use Cloud Spanner locks for any sort of mutual
-        # exclusion other than between Cloud Spanner transactions themselves. Retrying
-        # aborted transactions: When a transaction aborts, the application can choose to
-        # retry the whole transaction again. To maximize the chances of successfully
-        # committing the retry, the client should execute the retry in the same session
-        # as the original attempt. The original session's lock priority increases with
-        # each consecutive abort, meaning that each attempt has a slightly better chance
-        # of success than the previous. Note that the lock priority is preserved per
-        # session (not per transaction). Lock priority is set by the first read or write
-        # in the first attempt of a read-write transaction. If the application starts a
-        # new session to retry the whole transaction, the transaction loses its original
-        # lock priority. Moreover, the lock priority is only preserved if the
-        # transaction fails with an `ABORTED` error. Under some circumstances (for
-        # example, many transactions attempting to modify the same row(s)), a
-        # transaction can abort many times in a short period before successfully
-        # committing. Thus, it is not a good idea to cap the number of retries a
-        # transaction can attempt; instead, it is better to limit the total amount of
-        # time spent retrying. Idle transactions: A transaction is considered idle if it
-        # has no outstanding reads or SQL queries and has not started a read or SQL
-        # query within the last 10 seconds. Idle transactions can be aborted by Cloud
-        # Spanner so that they don't hold on to locks indefinitely. If an idle
-        # transaction is aborted, the commit will fail with error `ABORTED`. If this
-        # behavior is undesirable, periodically executing a simple SQL query in the
-        # transaction (for example, `SELECT 1`) prevents the transaction from becoming
-        # idle. Snapshot read-only transactions: Snapshot read-only transactions
-        # provides a simpler method than locking read-write transactions for doing
-        # several consistent reads. However, this type of transaction does not support
-        # writes. Snapshot transactions do not take locks. Instead, they work by
-        # choosing a Cloud Spanner timestamp, then executing all reads at that timestamp.
-        # Since they do not acquire locks, they do not block concurrent read-write
-        # transactions. Unlike locking read-write transactions, snapshot read-only
-        # transactions never abort. They can fail if the chosen read timestamp is
-        # garbage collected; however, the default garbage collection policy is generous
-        # enough that most applications do not need to worry about this in practice.
-        # Snapshot read-only transactions do not need to call Commit or Rollback (and in
-        # fact are not permitted to do so). To execute a snapshot transaction, the
-        # client specifies a timestamp bound, which tells Cloud Spanner how to choose a
-        # read timestamp. The types of timestamp bound are: - Strong (the default). -
-        # Bounded staleness. - Exact staleness. If the Cloud Spanner database to be read
-        # is geographically distributed, stale read-only transactions can execute more
-        # quickly than strong or read-write transactions, because they are able to
-        # execute far from the leader replica. Each type of timestamp bound is discussed
-        # in detail below. Strong: Strong reads are guaranteed to see the effects of all
-        # transactions that have committed before the start of the read. Furthermore,
-        # all rows yielded by a single read are consistent with each other -- if any
-        # part of the read observes a transaction, all parts of the read see the
-        # transaction. Strong reads are not repeatable: two consecutive strong read-only
-        # transactions might return inconsistent results if there are concurrent writes.
-        # If consistency across reads is required, the reads should be executed within a
-        # transaction or at an exact read timestamp. Queries on change streams (see
-        # below for more details) must also specify the strong read timestamp bound. See
-        # TransactionOptions.ReadOnly.strong. Exact staleness: These timestamp bounds
-        # execute reads at a user-specified timestamp. Reads at a timestamp are
-        # guaranteed to see a consistent prefix of the global transaction history: they
-        # observe modifications done by all transactions with a commit timestamp less
-        # than or equal to the read timestamp, and observe none of the modifications
-        # done by transactions with a larger commit timestamp. They will block until all
-        # conflicting transactions that may be assigned commit timestamps <= the read
-        # timestamp have finished. The timestamp can either be expressed as an absolute
-        # Cloud Spanner commit timestamp or a staleness relative to the current time.
-        # These modes do not require a "negotiation phase" to pick a timestamp. As a
-        # result, they execute slightly faster than the equivalent boundedly stale
-        # concurrency modes. On the other hand, boundedly stale reads usually return
-        # fresher results. See TransactionOptions.ReadOnly.read_timestamp and
-        # TransactionOptions.ReadOnly.exact_staleness. Bounded staleness: Bounded
-        # staleness modes allow Cloud Spanner to pick the read timestamp, subject to a
-        # user-provided staleness bound. Cloud Spanner chooses the newest timestamp
-        # within the staleness bound that allows execution of the reads at the closest
-        # available replica without blocking. All rows yielded are consistent with each
-        # other -- if any part of the read observes a transaction, all parts of the read
-        # see the transaction. Boundedly stale reads are not repeatable: two stale reads,
-        # even if they use the same staleness bound, can execute at different
-        # timestamps and thus return inconsistent results. Boundedly stale reads execute
-        # in two phases: the first phase negotiates a timestamp among all replicas
-        # needed to serve the read. In the second phase, reads are executed at the
-        # negotiated timestamp. As a result of the two phase execution, bounded
-        # staleness reads are usually a little slower than comparable exact staleness
-        # reads. However, they are typically able to return fresher results, and are
-        # more likely to execute at the closest replica. Because the timestamp
-        # negotiation requires up-front knowledge of which rows will be read, it can
-        # only be used with single-use read-only transactions. See TransactionOptions.
-        # ReadOnly.max_staleness and TransactionOptions.ReadOnly.min_read_timestamp. Old
-        # read timestamps and garbage collection: Cloud Spanner continuously garbage
-        # collects deleted and overwritten data in the background to reclaim storage
-        # space. This process is known as "version GC". By default, version GC reclaims
-        # versions after they are one hour old. Because of this, Cloud Spanner cannot
-        # perform reads at read timestamps more than one hour in the past. This
-        # restriction also applies to in-progress reads and/or SQL queries whose
-        # timestamp become too old while executing. Reads and SQL queries with too-old
-        # read timestamps fail with the error `FAILED_PRECONDITION`. You can configure
-        # and extend the `VERSION_RETENTION_PERIOD` of a database up to a period as long
-        # as one week, which allows Cloud Spanner to perform reads up to one week in the
-        # past. Querying change Streams: A Change Stream is a schema object that can be
-        # configured to watch data changes on the entire database, a set of tables, or a
-        # set of columns in a database. When a change stream is created, Spanner
-        # automatically defines a corresponding SQL Table-Valued Function (TVF) that can
-        # be used to query the change records in the associated change stream using the
-        # ExecuteStreamingSql API. The name of the TVF for a change stream is generated
-        # from the name of the change stream: READ_. All queries on change stream TVFs
-        # must be executed using the ExecuteStreamingSql API with a single-use read-only
-        # transaction with a strong read-only timestamp_bound. The change stream TVF
-        # allows users to specify the start_timestamp and end_timestamp for the time
-        # range of interest. All change records within the retention period is
-        # accessible using the strong read-only timestamp_bound. All other
-        # TransactionOptions are invalid for change stream queries. In addition, if
-        # TransactionOptions.read_only.return_read_timestamp is set to true, a special
-        # value of 2^63 - 2 will be returned in the Transaction message that describes
-        # the transaction, instead of a valid read timestamp. This special value should
-        # be discarded and not used for any subsequent queries. Please see https://cloud.
-        # google.com/spanner/docs/change-streams for more details on how to query the
-        # change stream TVFs. Partitioned DML transactions: Partitioned DML transactions
-        # are used to execute DML statements with a different execution strategy that
-        # provides different, and often better, scalability properties for large, table-
-        # wide operations than DML in a ReadWrite transaction. Smaller scoped statements,
-        # such as an OLTP workload, should prefer using ReadWrite transactions.
-        # Partitioned DML partitions the keyspace and runs the DML statement on each
-        # partition in separate, internal transactions. These transactions commit
-        # automatically when complete, and run independently from one another. To reduce
-        # lock contention, this execution strategy only acquires read locks on rows that
-        # match the WHERE clause of the statement. Additionally, the smaller per-
-        # partition transactions hold locks for less time. That said, Partitioned DML is
-        # not a drop-in replacement for standard DML used in ReadWrite transactions. -
-        # The DML statement must be fully-partitionable. Specifically, the statement
-        # must be expressible as the union of many statements which each access only a
-        # single row of the table. - The statement is not applied atomically to all rows
-        # of the table. Rather, the statement is applied atomically to partitions of the
-        # table, in independent transactions. Secondary index rows are updated
-        # atomically with the base table rows. - Partitioned DML does not guarantee
-        # exactly-once execution semantics against a partition. The statement is applied
-        # at least once to each partition. It is strongly recommended that the DML
-        # statement should be idempotent to avoid unexpected results. For instance, it
-        # is potentially dangerous to run a statement such as `UPDATE table SET column =
-        # column + 1` as it could be run multiple times against some rows. - The
-        # partitions are committed automatically - there is no support for Commit or
-        # Rollback. If the call returns an error, or if the client issuing the
-        # ExecuteSql call dies, it is possible that some rows had the statement executed
-        # on them successfully. It is also possible that statement was never executed
-        # against other rows. - Partitioned DML transactions may only contain the
-        # execution of a single DML statement via ExecuteSql or ExecuteStreamingSql. -
-        # If any error is encountered during the execution of the partitioned DML
-        # operation (for instance, a UNIQUE INDEX violation, division by zero, or a
-        # value that cannot be stored due to schema constraints), then the operation is
-        # stopped at that point and an error is returned. It is possible that at this
-        # point, some partitions have been committed (or even committed multiple times),
-        # and other partitions have not been run at all. Given the above, Partitioned
-        # DML is good fit for large, database-wide, operations that are idempotent, such
-        # as deleting old rows from a very large table.
+        # Options to use for transactions.
         # Corresponds to the JSON property `options`
         # @return [Google::Apis::SpannerV1::TransactionOptions]
         attr_accessor :options
@@ -1179,6 +988,79 @@ module Google
         end
       end
       
+      # Spanner Change Streams enable customers to capture and stream out changes to
+      # their Spanner databases in real-time. A change stream can be created with
+      # option partition_mode='IMMUTABLE_KEY_RANGE' or partition_mode='
+      # MUTABLE_KEY_RANGE'. This message is only used in Change Streams created with
+      # the option partition_mode='MUTABLE_KEY_RANGE'. Spanner automatically creates a
+      # special Table-Valued Function (TVF) along with each Change Streams. The
+      # function provides access to the change stream's records. The function is named
+      # READ_ (where is the name of the change stream), and it returns a table with
+      # only one column called ChangeRecord.
+      class ChangeStreamRecord
+        include Google::Apis::Core::Hashable
+      
+        # A data change record contains a set of changes to a table with the same
+        # modification type (insert, update, or delete) committed at the same commit
+        # timestamp in one change stream partition for the same transaction. Multiple
+        # data change records can be returned for the same transaction across multiple
+        # change stream partitions.
+        # Corresponds to the JSON property `dataChangeRecord`
+        # @return [Google::Apis::SpannerV1::DataChangeRecord]
+        attr_accessor :data_change_record
+      
+        # A heartbeat record is returned as a progress indicator, when there are no data
+        # changes or any other partition record types in the change stream partition.
+        # Corresponds to the JSON property `heartbeatRecord`
+        # @return [Google::Apis::SpannerV1::HeartbeatRecord]
+        attr_accessor :heartbeat_record
+      
+        # A partition end record serves as a notification that the client should stop
+        # reading the partition. No further records are expected to be retrieved on it.
+        # Corresponds to the JSON property `partitionEndRecord`
+        # @return [Google::Apis::SpannerV1::PartitionEndRecord]
+        attr_accessor :partition_end_record
+      
+        # A partition event record describes key range changes for a change stream
+        # partition. The changes to a row defined by its primary key can be captured in
+        # one change stream partition for a specific time range, and then be captured in
+        # a different change stream partition for a different time range. This movement
+        # of key ranges across change stream partitions is a reflection of activities,
+        # such as Spanner's dynamic splitting and load balancing, etc. Processing this
+        # event is needed if users want to guarantee processing of the changes for any
+        # key in timestamp order. If time ordered processing of changes for a primary
+        # key is not needed, this event can be ignored. To guarantee time ordered
+        # processing for each primary key, if the event describes move-ins, the reader
+        # of this partition needs to wait until the readers of the source partitions
+        # have processed all records with timestamps <= this PartitionEventRecord.
+        # commit_timestamp, before advancing beyond this PartitionEventRecord. If the
+        # event describes move-outs, the reader can notify the readers of the
+        # destination partitions that they can continue processing.
+        # Corresponds to the JSON property `partitionEventRecord`
+        # @return [Google::Apis::SpannerV1::PartitionEventRecord]
+        attr_accessor :partition_event_record
+      
+        # A partition start record serves as a notification that the client should
+        # schedule the partitions to be queried. PartitionStartRecord returns
+        # information about one or more partitions.
+        # Corresponds to the JSON property `partitionStartRecord`
+        # @return [Google::Apis::SpannerV1::PartitionStartRecord]
+        attr_accessor :partition_start_record
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @data_change_record = args[:data_change_record] if args.key?(:data_change_record)
+          @heartbeat_record = args[:heartbeat_record] if args.key?(:heartbeat_record)
+          @partition_end_record = args[:partition_end_record] if args.key?(:partition_end_record)
+          @partition_event_record = args[:partition_event_record] if args.key?(:partition_event_record)
+          @partition_start_record = args[:partition_start_record] if args.key?(:partition_start_record)
+        end
+      end
+      
       # Metadata associated with a parent-child relationship appearing in a PlanNode.
       class ChildLink
         include Google::Apis::Core::Hashable
@@ -1218,6 +1100,46 @@ module Google
         end
       end
       
+      # Metadata for a column.
+      class ColumnMetadata
+        include Google::Apis::Core::Hashable
+      
+        # Indicates whether the column is a primary key column.
+        # Corresponds to the JSON property `isPrimaryKey`
+        # @return [Boolean]
+        attr_accessor :is_primary_key
+        alias_method :is_primary_key?, :is_primary_key
+      
+        # Name of the column.
+        # Corresponds to the JSON property `name`
+        # @return [String]
+        attr_accessor :name
+      
+        # Ordinal position of the column based on the original table definition in the
+        # schema starting with a value of 1.
+        # Corresponds to the JSON property `ordinalPosition`
+        # @return [Fixnum]
+        attr_accessor :ordinal_position
+      
+        # `Type` indicates the type of a Cloud Spanner value, as might be stored in a
+        # table cell or returned from an SQL query.
+        # Corresponds to the JSON property `type`
+        # @return [Google::Apis::SpannerV1::Type]
+        attr_accessor :type
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @is_primary_key = args[:is_primary_key] if args.key?(:is_primary_key)
+          @name = args[:name] if args.key?(:name)
+          @ordinal_position = args[:ordinal_position] if args.key?(:ordinal_position)
+          @type = args[:type] if args.key?(:type)
+        end
+      end
+      
       # The request for Commit.
       class CommitRequest
         include Google::Apis::Core::Hashable
@@ -1256,198 +1178,7 @@ module Google
         attr_accessor :return_commit_stats
         alias_method :return_commit_stats?, :return_commit_stats
       
-        # Transactions: Each session can have at most one active transaction at a time (
-        # note that standalone reads and queries use a transaction internally and do
-        # count towards the one transaction limit). After the active transaction is
-        # completed, the session can immediately be re-used for the next transaction. It
-        # is not necessary to create a new session for each transaction. Transaction
-        # modes: Cloud Spanner supports three transaction modes: 1. Locking read-write.
-        # This type of transaction is the only way to write data into Cloud Spanner.
-        # These transactions rely on pessimistic locking and, if necessary, two-phase
-        # commit. Locking read-write transactions may abort, requiring the application
-        # to retry. 2. Snapshot read-only. Snapshot read-only transactions provide
-        # guaranteed consistency across several reads, but do not allow writes. Snapshot
-        # read-only transactions can be configured to read at timestamps in the past, or
-        # configured to perform a strong read (where Spanner will select a timestamp
-        # such that the read is guaranteed to see the effects of all transactions that
-        # have committed before the start of the read). Snapshot read-only transactions
-        # do not need to be committed. Queries on change streams must be performed with
-        # the snapshot read-only transaction mode, specifying a strong read. See
-        # TransactionOptions.ReadOnly.strong for more details. 3. Partitioned DML. This
-        # type of transaction is used to execute a single Partitioned DML statement.
-        # Partitioned DML partitions the key space and runs the DML statement over each
-        # partition in parallel using separate, internal transactions that commit
-        # independently. Partitioned DML transactions do not need to be committed. For
-        # transactions that only read, snapshot read-only transactions provide simpler
-        # semantics and are almost always faster. In particular, read-only transactions
-        # do not take locks, so they do not conflict with read-write transactions. As a
-        # consequence of not taking locks, they also do not abort, so retry loops are
-        # not needed. Transactions may only read-write data in a single database. They
-        # may, however, read-write data in different tables within that database.
-        # Locking read-write transactions: Locking transactions may be used to
-        # atomically read-modify-write data anywhere in a database. This type of
-        # transaction is externally consistent. Clients should attempt to minimize the
-        # amount of time a transaction is active. Faster transactions commit with higher
-        # probability and cause less contention. Cloud Spanner attempts to keep read
-        # locks active as long as the transaction continues to do reads, and the
-        # transaction has not been terminated by Commit or Rollback. Long periods of
-        # inactivity at the client may cause Cloud Spanner to release a transaction's
-        # locks and abort it. Conceptually, a read-write transaction consists of zero or
-        # more reads or SQL statements followed by Commit. At any time before Commit,
-        # the client can send a Rollback request to abort the transaction. Semantics:
-        # Cloud Spanner can commit the transaction if all read locks it acquired are
-        # still valid at commit time, and it is able to acquire write locks for all
-        # writes. Cloud Spanner can abort the transaction for any reason. If a commit
-        # attempt returns `ABORTED`, Cloud Spanner guarantees that the transaction has
-        # not modified any user data in Cloud Spanner. Unless the transaction commits,
-        # Cloud Spanner makes no guarantees about how long the transaction's locks were
-        # held for. It is an error to use Cloud Spanner locks for any sort of mutual
-        # exclusion other than between Cloud Spanner transactions themselves. Retrying
-        # aborted transactions: When a transaction aborts, the application can choose to
-        # retry the whole transaction again. To maximize the chances of successfully
-        # committing the retry, the client should execute the retry in the same session
-        # as the original attempt. The original session's lock priority increases with
-        # each consecutive abort, meaning that each attempt has a slightly better chance
-        # of success than the previous. Note that the lock priority is preserved per
-        # session (not per transaction). Lock priority is set by the first read or write
-        # in the first attempt of a read-write transaction. If the application starts a
-        # new session to retry the whole transaction, the transaction loses its original
-        # lock priority. Moreover, the lock priority is only preserved if the
-        # transaction fails with an `ABORTED` error. Under some circumstances (for
-        # example, many transactions attempting to modify the same row(s)), a
-        # transaction can abort many times in a short period before successfully
-        # committing. Thus, it is not a good idea to cap the number of retries a
-        # transaction can attempt; instead, it is better to limit the total amount of
-        # time spent retrying. Idle transactions: A transaction is considered idle if it
-        # has no outstanding reads or SQL queries and has not started a read or SQL
-        # query within the last 10 seconds. Idle transactions can be aborted by Cloud
-        # Spanner so that they don't hold on to locks indefinitely. If an idle
-        # transaction is aborted, the commit will fail with error `ABORTED`. If this
-        # behavior is undesirable, periodically executing a simple SQL query in the
-        # transaction (for example, `SELECT 1`) prevents the transaction from becoming
-        # idle. Snapshot read-only transactions: Snapshot read-only transactions
-        # provides a simpler method than locking read-write transactions for doing
-        # several consistent reads. However, this type of transaction does not support
-        # writes. Snapshot transactions do not take locks. Instead, they work by
-        # choosing a Cloud Spanner timestamp, then executing all reads at that timestamp.
-        # Since they do not acquire locks, they do not block concurrent read-write
-        # transactions. Unlike locking read-write transactions, snapshot read-only
-        # transactions never abort. They can fail if the chosen read timestamp is
-        # garbage collected; however, the default garbage collection policy is generous
-        # enough that most applications do not need to worry about this in practice.
-        # Snapshot read-only transactions do not need to call Commit or Rollback (and in
-        # fact are not permitted to do so). To execute a snapshot transaction, the
-        # client specifies a timestamp bound, which tells Cloud Spanner how to choose a
-        # read timestamp. The types of timestamp bound are: - Strong (the default). -
-        # Bounded staleness. - Exact staleness. If the Cloud Spanner database to be read
-        # is geographically distributed, stale read-only transactions can execute more
-        # quickly than strong or read-write transactions, because they are able to
-        # execute far from the leader replica. Each type of timestamp bound is discussed
-        # in detail below. Strong: Strong reads are guaranteed to see the effects of all
-        # transactions that have committed before the start of the read. Furthermore,
-        # all rows yielded by a single read are consistent with each other -- if any
-        # part of the read observes a transaction, all parts of the read see the
-        # transaction. Strong reads are not repeatable: two consecutive strong read-only
-        # transactions might return inconsistent results if there are concurrent writes.
-        # If consistency across reads is required, the reads should be executed within a
-        # transaction or at an exact read timestamp. Queries on change streams (see
-        # below for more details) must also specify the strong read timestamp bound. See
-        # TransactionOptions.ReadOnly.strong. Exact staleness: These timestamp bounds
-        # execute reads at a user-specified timestamp. Reads at a timestamp are
-        # guaranteed to see a consistent prefix of the global transaction history: they
-        # observe modifications done by all transactions with a commit timestamp less
-        # than or equal to the read timestamp, and observe none of the modifications
-        # done by transactions with a larger commit timestamp. They will block until all
-        # conflicting transactions that may be assigned commit timestamps <= the read
-        # timestamp have finished. The timestamp can either be expressed as an absolute
-        # Cloud Spanner commit timestamp or a staleness relative to the current time.
-        # These modes do not require a "negotiation phase" to pick a timestamp. As a
-        # result, they execute slightly faster than the equivalent boundedly stale
-        # concurrency modes. On the other hand, boundedly stale reads usually return
-        # fresher results. See TransactionOptions.ReadOnly.read_timestamp and
-        # TransactionOptions.ReadOnly.exact_staleness. Bounded staleness: Bounded
-        # staleness modes allow Cloud Spanner to pick the read timestamp, subject to a
-        # user-provided staleness bound. Cloud Spanner chooses the newest timestamp
-        # within the staleness bound that allows execution of the reads at the closest
-        # available replica without blocking. All rows yielded are consistent with each
-        # other -- if any part of the read observes a transaction, all parts of the read
-        # see the transaction. Boundedly stale reads are not repeatable: two stale reads,
-        # even if they use the same staleness bound, can execute at different
-        # timestamps and thus return inconsistent results. Boundedly stale reads execute
-        # in two phases: the first phase negotiates a timestamp among all replicas
-        # needed to serve the read. In the second phase, reads are executed at the
-        # negotiated timestamp. As a result of the two phase execution, bounded
-        # staleness reads are usually a little slower than comparable exact staleness
-        # reads. However, they are typically able to return fresher results, and are
-        # more likely to execute at the closest replica. Because the timestamp
-        # negotiation requires up-front knowledge of which rows will be read, it can
-        # only be used with single-use read-only transactions. See TransactionOptions.
-        # ReadOnly.max_staleness and TransactionOptions.ReadOnly.min_read_timestamp. Old
-        # read timestamps and garbage collection: Cloud Spanner continuously garbage
-        # collects deleted and overwritten data in the background to reclaim storage
-        # space. This process is known as "version GC". By default, version GC reclaims
-        # versions after they are one hour old. Because of this, Cloud Spanner cannot
-        # perform reads at read timestamps more than one hour in the past. This
-        # restriction also applies to in-progress reads and/or SQL queries whose
-        # timestamp become too old while executing. Reads and SQL queries with too-old
-        # read timestamps fail with the error `FAILED_PRECONDITION`. You can configure
-        # and extend the `VERSION_RETENTION_PERIOD` of a database up to a period as long
-        # as one week, which allows Cloud Spanner to perform reads up to one week in the
-        # past. Querying change Streams: A Change Stream is a schema object that can be
-        # configured to watch data changes on the entire database, a set of tables, or a
-        # set of columns in a database. When a change stream is created, Spanner
-        # automatically defines a corresponding SQL Table-Valued Function (TVF) that can
-        # be used to query the change records in the associated change stream using the
-        # ExecuteStreamingSql API. The name of the TVF for a change stream is generated
-        # from the name of the change stream: READ_. All queries on change stream TVFs
-        # must be executed using the ExecuteStreamingSql API with a single-use read-only
-        # transaction with a strong read-only timestamp_bound. The change stream TVF
-        # allows users to specify the start_timestamp and end_timestamp for the time
-        # range of interest. All change records within the retention period is
-        # accessible using the strong read-only timestamp_bound. All other
-        # TransactionOptions are invalid for change stream queries. In addition, if
-        # TransactionOptions.read_only.return_read_timestamp is set to true, a special
-        # value of 2^63 - 2 will be returned in the Transaction message that describes
-        # the transaction, instead of a valid read timestamp. This special value should
-        # be discarded and not used for any subsequent queries. Please see https://cloud.
-        # google.com/spanner/docs/change-streams for more details on how to query the
-        # change stream TVFs. Partitioned DML transactions: Partitioned DML transactions
-        # are used to execute DML statements with a different execution strategy that
-        # provides different, and often better, scalability properties for large, table-
-        # wide operations than DML in a ReadWrite transaction. Smaller scoped statements,
-        # such as an OLTP workload, should prefer using ReadWrite transactions.
-        # Partitioned DML partitions the keyspace and runs the DML statement on each
-        # partition in separate, internal transactions. These transactions commit
-        # automatically when complete, and run independently from one another. To reduce
-        # lock contention, this execution strategy only acquires read locks on rows that
-        # match the WHERE clause of the statement. Additionally, the smaller per-
-        # partition transactions hold locks for less time. That said, Partitioned DML is
-        # not a drop-in replacement for standard DML used in ReadWrite transactions. -
-        # The DML statement must be fully-partitionable. Specifically, the statement
-        # must be expressible as the union of many statements which each access only a
-        # single row of the table. - The statement is not applied atomically to all rows
-        # of the table. Rather, the statement is applied atomically to partitions of the
-        # table, in independent transactions. Secondary index rows are updated
-        # atomically with the base table rows. - Partitioned DML does not guarantee
-        # exactly-once execution semantics against a partition. The statement is applied
-        # at least once to each partition. It is strongly recommended that the DML
-        # statement should be idempotent to avoid unexpected results. For instance, it
-        # is potentially dangerous to run a statement such as `UPDATE table SET column =
-        # column + 1` as it could be run multiple times against some rows. - The
-        # partitions are committed automatically - there is no support for Commit or
-        # Rollback. If the call returns an error, or if the client issuing the
-        # ExecuteSql call dies, it is possible that some rows had the statement executed
-        # on them successfully. It is also possible that statement was never executed
-        # against other rows. - Partitioned DML transactions may only contain the
-        # execution of a single DML statement via ExecuteSql or ExecuteStreamingSql. -
-        # If any error is encountered during the execution of the partitioned DML
-        # operation (for instance, a UNIQUE INDEX violation, division by zero, or a
-        # value that cannot be stored due to schema constraints), then the operation is
-        # stopped at that point and an error is returned. It is possible that at this
-        # point, some partitions have been committed (or even committed multiple times),
-        # and other partitions have not been run at all. Given the above, Partitioned
-        # DML is good fit for large, database-wide, operations that are idempotent, such
-        # as deleting old rows from a very large table.
+        # Options to use for transactions.
         # Corresponds to the JSON property `singleUseTransaction`
         # @return [Google::Apis::SpannerV1::TransactionOptions]
         attr_accessor :single_use_transaction
@@ -2152,6 +1883,125 @@ module Google
         end
       end
       
+      # A data change record contains a set of changes to a table with the same
+      # modification type (insert, update, or delete) committed at the same commit
+      # timestamp in one change stream partition for the same transaction. Multiple
+      # data change records can be returned for the same transaction across multiple
+      # change stream partitions.
+      class DataChangeRecord
+        include Google::Apis::Core::Hashable
+      
+        # Provides metadata describing the columns associated with the mods listed below.
+        # Corresponds to the JSON property `columnMetadata`
+        # @return [Array<Google::Apis::SpannerV1::ColumnMetadata>]
+        attr_accessor :column_metadata
+      
+        # Indicates the timestamp in which the change was committed. DataChangeRecord.
+        # commit_timestamps, PartitionStartRecord.start_timestamps, PartitionEventRecord.
+        # commit_timestamps, and PartitionEndRecord.end_timestamps can have the same
+        # value in the same partition.
+        # Corresponds to the JSON property `commitTimestamp`
+        # @return [String]
+        attr_accessor :commit_timestamp
+      
+        # Indicates whether this is the last record for a transaction in the current
+        # partition. Clients can use this field to determine when all records for a
+        # transaction in the current partition have been received.
+        # Corresponds to the JSON property `isLastRecordInTransactionInPartition`
+        # @return [Boolean]
+        attr_accessor :is_last_record_in_transaction_in_partition
+        alias_method :is_last_record_in_transaction_in_partition?, :is_last_record_in_transaction_in_partition
+      
+        # Indicates whether the transaction is a system transaction. System transactions
+        # include those issued by time-to-live (TTL), column backfill, etc.
+        # Corresponds to the JSON property `isSystemTransaction`
+        # @return [Boolean]
+        attr_accessor :is_system_transaction
+        alias_method :is_system_transaction?, :is_system_transaction
+      
+        # Describes the type of change.
+        # Corresponds to the JSON property `modType`
+        # @return [String]
+        attr_accessor :mod_type
+      
+        # Describes the changes that were made.
+        # Corresponds to the JSON property `mods`
+        # @return [Array<Google::Apis::SpannerV1::Mod>]
+        attr_accessor :mods
+      
+        # Indicates the number of partitions that return data change records for this
+        # transaction. This value can be helpful in assembling all records associated
+        # with a particular transaction.
+        # Corresponds to the JSON property `numberOfPartitionsInTransaction`
+        # @return [Fixnum]
+        attr_accessor :number_of_partitions_in_transaction
+      
+        # Indicates the number of data change records that are part of this transaction
+        # across all change stream partitions. This value can be used to assemble all
+        # the records associated with a particular transaction.
+        # Corresponds to the JSON property `numberOfRecordsInTransaction`
+        # @return [Fixnum]
+        attr_accessor :number_of_records_in_transaction
+      
+        # Record sequence numbers are unique and monotonically increasing (but not
+        # necessarily contiguous) for a specific timestamp across record types in the
+        # same partition. To guarantee ordered processing, the reader should process
+        # records (of potentially different types) in record_sequence order for a
+        # specific timestamp in the same partition. The record sequence number ordering
+        # across partitions is only meaningful in the context of a specific transaction.
+        # Record sequence numbers are unique across partitions for a specific
+        # transaction. Sort the DataChangeRecords for the same server_transaction_id by
+        # record_sequence to reconstruct the ordering of the changes within the
+        # transaction.
+        # Corresponds to the JSON property `recordSequence`
+        # @return [String]
+        attr_accessor :record_sequence
+      
+        # Provides a globally unique string that represents the transaction in which the
+        # change was committed. Multiple transactions can have the same commit timestamp,
+        # but each transaction has a unique server_transaction_id.
+        # Corresponds to the JSON property `serverTransactionId`
+        # @return [String]
+        attr_accessor :server_transaction_id
+      
+        # Name of the table affected by the change.
+        # Corresponds to the JSON property `table`
+        # @return [String]
+        attr_accessor :table
+      
+        # Indicates the transaction tag associated with this transaction.
+        # Corresponds to the JSON property `transactionTag`
+        # @return [String]
+        attr_accessor :transaction_tag
+      
+        # Describes the value capture type that was specified in the change stream
+        # configuration when this change was captured.
+        # Corresponds to the JSON property `valueCaptureType`
+        # @return [String]
+        attr_accessor :value_capture_type
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @column_metadata = args[:column_metadata] if args.key?(:column_metadata)
+          @commit_timestamp = args[:commit_timestamp] if args.key?(:commit_timestamp)
+          @is_last_record_in_transaction_in_partition = args[:is_last_record_in_transaction_in_partition] if args.key?(:is_last_record_in_transaction_in_partition)
+          @is_system_transaction = args[:is_system_transaction] if args.key?(:is_system_transaction)
+          @mod_type = args[:mod_type] if args.key?(:mod_type)
+          @mods = args[:mods] if args.key?(:mods)
+          @number_of_partitions_in_transaction = args[:number_of_partitions_in_transaction] if args.key?(:number_of_partitions_in_transaction)
+          @number_of_records_in_transaction = args[:number_of_records_in_transaction] if args.key?(:number_of_records_in_transaction)
+          @record_sequence = args[:record_sequence] if args.key?(:record_sequence)
+          @server_transaction_id = args[:server_transaction_id] if args.key?(:server_transaction_id)
+          @table = args[:table] if args.key?(:table)
+          @transaction_tag = args[:transaction_tag] if args.key?(:transaction_tag)
+          @value_capture_type = args[:value_capture_type] if args.key?(:value_capture_type)
+        end
+      end
+      
       # A Cloud Spanner database.
       class Database
         include Google::Apis::Core::Hashable
@@ -2267,6 +2117,33 @@ module Google
         end
       end
       
+      # The configuration for each database in the target instance configuration.
+      class DatabaseMoveConfig
+        include Google::Apis::Core::Hashable
+      
+        # 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.
+        # Corresponds to the JSON property `databaseId`
+        # @return [String]
+        attr_accessor :database_id
+      
+        # Encryption configuration for a Cloud Spanner database.
+        # Corresponds to the JSON property `encryptionConfig`
+        # @return [Google::Apis::SpannerV1::InstanceEncryptionConfig]
+        attr_accessor :encryption_config
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @database_id = args[:database_id] if args.key?(:database_id)
+          @encryption_config = args[:encryption_config] if args.key?(:encryption_config)
+        end
+      end
+      
       # A Cloud Spanner database role.
       class DatabaseRole
         include Google::Apis::Core::Hashable
@@ -3053,6 +2930,29 @@ module Google
         end
       end
       
+      # A heartbeat record is returned as a progress indicator, when there are no data
+      # changes or any other partition record types in the change stream partition.
+      class HeartbeatRecord
+        include Google::Apis::Core::Hashable
+      
+        # Indicates the timestamp at which the query has returned all the records in the
+        # change stream partition with timestamp <= heartbeat timestamp. The heartbeat
+        # timestamp will not be the same as the timestamps of other record types in the
+        # same partition.
+        # Corresponds to the JSON property `timestamp`
+        # @return [String]
+        attr_accessor :timestamp
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @timestamp = args[:timestamp] if args.key?(:timestamp)
+        end
+      end
+      
       # An `IncludeReplicas` contains a repeated set of `ReplicaSelection` which
       # indicates the order in which replicas should be considered.
       class IncludeReplicas
@@ -3468,6 +3368,48 @@ module Google
         end
       end
       
+      # Encryption configuration for a Cloud Spanner database.
+      class InstanceEncryptionConfig
+        include Google::Apis::Core::Hashable
+      
+        # Optional. This field is maintained for backwards compatibility. For new
+        # callers, we recommend using `kms_key_names` to specify the KMS key. `
+        # kms_key_name` should only be used if the location of the KMS key matches the
+        # database instance’s configuration (location) exactly. E.g. The KMS location is
+        # in us-central1 or nam3 and the database instance is also in us-central1 or
+        # nam3. The Cloud KMS key to be used for encrypting and decrypting the database.
+        # Values are of the form `projects//locations//keyRings//cryptoKeys/`.
+        # Corresponds to the JSON property `kmsKeyName`
+        # @return [String]
+        attr_accessor :kms_key_name
+      
+        # Optional. Specifies the KMS configuration for one or more keys used to encrypt
+        # the database. Values are of the form `projects//locations//keyRings//
+        # cryptoKeys/`. The keys referenced by `kms_key_names` must fully cover all
+        # regions of the database's instance configuration. Some examples: * For
+        # regional (single-region) instance configurations, specify a regional location
+        # KMS key. * For multi-region instance configurations of type `GOOGLE_MANAGED`,
+        # either specify a multi-region location KMS key or multiple regional location
+        # KMS keys that cover all regions in the instance configuration. * For an
+        # instance configuration of type `USER_MANAGED`, specify only regional location
+        # KMS keys to cover each region in the instance configuration. Multi-region
+        # location KMS keys aren't supported for `USER_MANAGED` type instance
+        # configurations.
+        # Corresponds to the JSON property `kmsKeyNames`
+        # @return [Array<String>]
+        attr_accessor :kms_key_names
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @kms_key_name = args[:kms_key_name] if args.key?(:kms_key_name)
+          @kms_key_names = args[:kms_key_names] if args.key?(:kms_key_names)
+        end
+      end
+      
       # Encapsulates progress related information for a Cloud Spanner long running
       # instance operations.
       class InstanceOperationProgress
@@ -4430,6 +4372,92 @@ module Google
         end
       end
       
+      # A mod describes all data changes in a watched table row.
+      class Mod
+        include Google::Apis::Core::Hashable
+      
+        # Returns the value of the primary key of the modified row.
+        # Corresponds to the JSON property `keys`
+        # @return [Array<Google::Apis::SpannerV1::ModValue>]
+        attr_accessor :keys
+      
+        # Returns the new values after the change for the modified columns. Always empty
+        # for DELETE.
+        # Corresponds to the JSON property `newValues`
+        # @return [Array<Google::Apis::SpannerV1::ModValue>]
+        attr_accessor :new_values
+      
+        # Returns the old values before the change for the modified columns. Always
+        # empty for INSERT, or if old values are not being captured specified by
+        # value_capture_type.
+        # Corresponds to the JSON property `oldValues`
+        # @return [Array<Google::Apis::SpannerV1::ModValue>]
+        attr_accessor :old_values
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @keys = args[:keys] if args.key?(:keys)
+          @new_values = args[:new_values] if args.key?(:new_values)
+          @old_values = args[:old_values] if args.key?(:old_values)
+        end
+      end
+      
+      # Returns the value and associated metadata for a particular field of the Mod.
+      class ModValue
+        include Google::Apis::Core::Hashable
+      
+        # Index within the repeated column_metadata field, to obtain the column metadata
+        # for the column that was modified.
+        # Corresponds to the JSON property `columnMetadataIndex`
+        # @return [Fixnum]
+        attr_accessor :column_metadata_index
+      
+        # The value of the column.
+        # Corresponds to the JSON property `value`
+        # @return [Object]
+        attr_accessor :value
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @column_metadata_index = args[:column_metadata_index] if args.key?(:column_metadata_index)
+          @value = args[:value] if args.key?(:value)
+        end
+      end
+      
+      # Describes move-in of the key ranges into the change stream partition
+      # identified by partition_token. To maintain processing the changes for a
+      # particular key in timestamp order, the query processing the change stream
+      # partition identified by partition_token should not advance beyond the
+      # partition event record commit timestamp until the queries processing the
+      # source change stream partitions have processed all change stream records with
+      # timestamps <= the partition event record commit timestamp.
+      class MoveInEvent
+        include Google::Apis::Core::Hashable
+      
+        # An unique partition identifier describing the source change stream partition
+        # that recorded changes for the key range that is moving into this partition.
+        # Corresponds to the JSON property `sourcePartitionToken`
+        # @return [String]
+        attr_accessor :source_partition_token
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @source_partition_token = args[:source_partition_token] if args.key?(:source_partition_token)
+        end
+      end
+      
       # The request for MoveInstance.
       class MoveInstanceRequest
         include Google::Apis::Core::Hashable
@@ -4440,6 +4468,12 @@ module Google
         # @return [String]
         attr_accessor :target_config
       
+        # Optional. The configuration for each database in the target instance
+        # configuration.
+        # Corresponds to the JSON property `targetDatabaseMoveConfigs`
+        # @return [Array<Google::Apis::SpannerV1::DatabaseMoveConfig>]
+        attr_accessor :target_database_move_configs
+      
         def initialize(**args)
            update!(**args)
         end
@@ -4447,6 +4481,33 @@ module Google
         # Update properties of this object
         def update!(**args)
           @target_config = args[:target_config] if args.key?(:target_config)
+          @target_database_move_configs = args[:target_database_move_configs] if args.key?(:target_database_move_configs)
+        end
+      end
+      
+      # Describes move-out of the key ranges out of the change stream partition
+      # identified by partition_token. To maintain processing the changes for a
+      # particular key in timestamp order, the query processing the MoveOutEvent in
+      # the partition identified by partition_token should inform the queries
+      # processing the destination partitions that they can unblock and proceed
+      # processing records past the commit_timestamp.
+      class MoveOutEvent
+        include Google::Apis::Core::Hashable
+      
+        # An unique partition identifier describing the destination change stream
+        # partition that will record changes for the key range that is moving out of
+        # this partition.
+        # Corresponds to the JSON property `destinationPartitionToken`
+        # @return [String]
+        attr_accessor :destination_partition_token
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @destination_partition_token = args[:destination_partition_token] if args.key?(:destination_partition_token)
         end
       end
       
@@ -4795,6 +4856,137 @@ module Google
         end
       end
       
+      # A partition end record serves as a notification that the client should stop
+      # reading the partition. No further records are expected to be retrieved on it.
+      class PartitionEndRecord
+        include Google::Apis::Core::Hashable
+      
+        # End timestamp at which the change stream partition is terminated. All changes
+        # generated by this partition will have timestamps <= end_timestamp.
+        # DataChangeRecord.commit_timestamps, PartitionStartRecord.start_timestamps,
+        # PartitionEventRecord.commit_timestamps, and PartitionEndRecord.end_timestamps
+        # can have the same value in the same partition. PartitionEndRecord is the last
+        # record returned for a partition.
+        # Corresponds to the JSON property `endTimestamp`
+        # @return [String]
+        attr_accessor :end_timestamp
+      
+        # Unique partition identifier describing the terminated change stream partition.
+        # partition_token is equal to the partition token of the change stream partition
+        # currently queried to return this PartitionEndRecord.
+        # Corresponds to the JSON property `partitionToken`
+        # @return [String]
+        attr_accessor :partition_token
+      
+        # Record sequence numbers are unique and monotonically increasing (but not
+        # necessarily contiguous) for a specific timestamp across record types in the
+        # same partition. To guarantee ordered processing, the reader should process
+        # records (of potentially different types) in record_sequence order for a
+        # specific timestamp in the same partition.
+        # Corresponds to the JSON property `recordSequence`
+        # @return [String]
+        attr_accessor :record_sequence
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @end_timestamp = args[:end_timestamp] if args.key?(:end_timestamp)
+          @partition_token = args[:partition_token] if args.key?(:partition_token)
+          @record_sequence = args[:record_sequence] if args.key?(:record_sequence)
+        end
+      end
+      
+      # A partition event record describes key range changes for a change stream
+      # partition. The changes to a row defined by its primary key can be captured in
+      # one change stream partition for a specific time range, and then be captured in
+      # a different change stream partition for a different time range. This movement
+      # of key ranges across change stream partitions is a reflection of activities,
+      # such as Spanner's dynamic splitting and load balancing, etc. Processing this
+      # event is needed if users want to guarantee processing of the changes for any
+      # key in timestamp order. If time ordered processing of changes for a primary
+      # key is not needed, this event can be ignored. To guarantee time ordered
+      # processing for each primary key, if the event describes move-ins, the reader
+      # of this partition needs to wait until the readers of the source partitions
+      # have processed all records with timestamps <= this PartitionEventRecord.
+      # commit_timestamp, before advancing beyond this PartitionEventRecord. If the
+      # event describes move-outs, the reader can notify the readers of the
+      # destination partitions that they can continue processing.
+      class PartitionEventRecord
+        include Google::Apis::Core::Hashable
+      
+        # Indicates the commit timestamp at which the key range change occurred.
+        # DataChangeRecord.commit_timestamps, PartitionStartRecord.start_timestamps,
+        # PartitionEventRecord.commit_timestamps, and PartitionEndRecord.end_timestamps
+        # can have the same value in the same partition.
+        # Corresponds to the JSON property `commitTimestamp`
+        # @return [String]
+        attr_accessor :commit_timestamp
+      
+        # Set when one or more key ranges are moved into the change stream partition
+        # identified by partition_token. Example: Two key ranges are moved into
+        # partition (P1) from partition (P2) and partition (P3) in a single transaction
+        # at timestamp T. The PartitionEventRecord returned in P1 will reflect the move
+        # as: PartitionEventRecord ` commit_timestamp: T partition_token: "P1"
+        # move_in_events ` source_partition_token: "P2" ` move_in_events `
+        # source_partition_token: "P3" ` ` The PartitionEventRecord returned in P2 will
+        # reflect the move as: PartitionEventRecord ` commit_timestamp: T
+        # partition_token: "P2" move_out_events ` destination_partition_token: "P1" ` `
+        # The PartitionEventRecord returned in P3 will reflect the move as:
+        # PartitionEventRecord ` commit_timestamp: T partition_token: "P3"
+        # move_out_events ` destination_partition_token: "P1" ` `
+        # Corresponds to the JSON property `moveInEvents`
+        # @return [Array<Google::Apis::SpannerV1::MoveInEvent>]
+        attr_accessor :move_in_events
+      
+        # Set when one or more key ranges are moved out of the change stream partition
+        # identified by partition_token. Example: Two key ranges are moved out of
+        # partition (P1) to partition (P2) and partition (P3) in a single transaction at
+        # timestamp T. The PartitionEventRecord returned in P1 will reflect the move as:
+        # PartitionEventRecord ` commit_timestamp: T partition_token: "P1"
+        # move_out_events ` destination_partition_token: "P2" ` move_out_events `
+        # destination_partition_token: "P3" ` ` The PartitionEventRecord returned in P2
+        # will reflect the move as: PartitionEventRecord ` commit_timestamp: T
+        # partition_token: "P2" move_in_events ` source_partition_token: "P1" ` ` The
+        # PartitionEventRecord returned in P3 will reflect the move as:
+        # PartitionEventRecord ` commit_timestamp: T partition_token: "P3"
+        # move_in_events ` source_partition_token: "P1" ` `
+        # Corresponds to the JSON property `moveOutEvents`
+        # @return [Array<Google::Apis::SpannerV1::MoveOutEvent>]
+        attr_accessor :move_out_events
+      
+        # Unique partition identifier describing the partition this event occurred on.
+        # partition_token is equal to the partition token of the change stream partition
+        # currently queried to return this PartitionEventRecord.
+        # Corresponds to the JSON property `partitionToken`
+        # @return [String]
+        attr_accessor :partition_token
+      
+        # Record sequence numbers are unique and monotonically increasing (but not
+        # necessarily contiguous) for a specific timestamp across record types in the
+        # same partition. To guarantee ordered processing, the reader should process
+        # records (of potentially different types) in record_sequence order for a
+        # specific timestamp in the same partition.
+        # Corresponds to the JSON property `recordSequence`
+        # @return [String]
+        attr_accessor :record_sequence
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @commit_timestamp = args[:commit_timestamp] if args.key?(:commit_timestamp)
+          @move_in_events = args[:move_in_events] if args.key?(:move_in_events)
+          @move_out_events = args[:move_out_events] if args.key?(:move_out_events)
+          @partition_token = args[:partition_token] if args.key?(:partition_token)
+          @record_sequence = args[:record_sequence] if args.key?(:record_sequence)
+        end
+      end
+      
       # Options for a `PartitionQueryRequest` and `PartitionReadRequest`.
       class PartitionOptions
         include Google::Apis::Core::Hashable
@@ -4971,6 +5163,47 @@ module Google
         end
       end
       
+      # A partition start record serves as a notification that the client should
+      # schedule the partitions to be queried. PartitionStartRecord returns
+      # information about one or more partitions.
+      class PartitionStartRecord
+        include Google::Apis::Core::Hashable
+      
+        # Unique partition identifiers to be used in queries.
+        # Corresponds to the JSON property `partitionTokens`
+        # @return [Array<String>]
+        attr_accessor :partition_tokens
+      
+        # Record sequence numbers are unique and monotonically increasing (but not
+        # necessarily contiguous) for a specific timestamp across record types in the
+        # same partition. To guarantee ordered processing, the reader should process
+        # records (of potentially different types) in record_sequence order for a
+        # specific timestamp in the same partition.
+        # Corresponds to the JSON property `recordSequence`
+        # @return [String]
+        attr_accessor :record_sequence
+      
+        # Start timestamp at which the partitions should be queried to return change
+        # stream records with timestamps >= start_timestamp. DataChangeRecord.
+        # commit_timestamps, PartitionStartRecord.start_timestamps, PartitionEventRecord.
+        # commit_timestamps, and PartitionEndRecord.end_timestamps can have the same
+        # value in the same partition.
+        # Corresponds to the JSON property `startTimestamp`
+        # @return [String]
+        attr_accessor :start_timestamp
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @partition_tokens = args[:partition_tokens] if args.key?(:partition_tokens)
+          @record_sequence = args[:record_sequence] if args.key?(:record_sequence)
+          @start_timestamp = args[:start_timestamp] if args.key?(:start_timestamp)
+        end
+      end
+      
       # Message type to initiate a Partitioned DML transaction.
       class PartitionedDml
         include Google::Apis::Core::Hashable
@@ -5385,7 +5618,7 @@ module Google
       
         # Executes all reads at the given timestamp. Unlike other modes, reads at a
         # specific timestamp are repeatable; the same read at the same timestamp always
-        # returns the same data. If the timestamp is in the future, the read will block
+        # returns the same data. If the timestamp is in the future, the read is blocked
         # until the specified timestamp, modulo the read's deadline. Useful for large
         # scale consistent reads such as mapreduces, or for coordinating many reads
         # against a consistent snapshot of the data. A timestamp in RFC3339 UTC \"Zulu\"
@@ -6260,7 +6493,7 @@ module Google
         end
       end
       
-      # The split points of a table/index.
+      # The split points of a table or an index.
       class SplitPoints
         include Google::Apis::Core::Hashable
       
@@ -6277,7 +6510,7 @@ module Google
         # @return [String]
         attr_accessor :index
       
-        # Required. The list of split keys, i.e., the split boundaries.
+        # Required. The list of split keys. In essence, the split boundaries.
         # Corresponds to the JSON property `keys`
         # @return [Array<Google::Apis::SpannerV1::Key>]
         attr_accessor :keys
@@ -6482,212 +6715,21 @@ module Google
         end
       end
       
-      # Transactions: Each session can have at most one active transaction at a time (
-      # note that standalone reads and queries use a transaction internally and do
-      # count towards the one transaction limit). After the active transaction is
-      # completed, the session can immediately be re-used for the next transaction. It
-      # is not necessary to create a new session for each transaction. Transaction
-      # modes: Cloud Spanner supports three transaction modes: 1. Locking read-write.
-      # This type of transaction is the only way to write data into Cloud Spanner.
-      # These transactions rely on pessimistic locking and, if necessary, two-phase
-      # commit. Locking read-write transactions may abort, requiring the application
-      # to retry. 2. Snapshot read-only. Snapshot read-only transactions provide
-      # guaranteed consistency across several reads, but do not allow writes. Snapshot
-      # read-only transactions can be configured to read at timestamps in the past, or
-      # configured to perform a strong read (where Spanner will select a timestamp
-      # such that the read is guaranteed to see the effects of all transactions that
-      # have committed before the start of the read). Snapshot read-only transactions
-      # do not need to be committed. Queries on change streams must be performed with
-      # the snapshot read-only transaction mode, specifying a strong read. See
-      # TransactionOptions.ReadOnly.strong for more details. 3. Partitioned DML. This
-      # type of transaction is used to execute a single Partitioned DML statement.
-      # Partitioned DML partitions the key space and runs the DML statement over each
-      # partition in parallel using separate, internal transactions that commit
-      # independently. Partitioned DML transactions do not need to be committed. For
-      # transactions that only read, snapshot read-only transactions provide simpler
-      # semantics and are almost always faster. In particular, read-only transactions
-      # do not take locks, so they do not conflict with read-write transactions. As a
-      # consequence of not taking locks, they also do not abort, so retry loops are
-      # not needed. Transactions may only read-write data in a single database. They
-      # may, however, read-write data in different tables within that database.
-      # Locking read-write transactions: Locking transactions may be used to
-      # atomically read-modify-write data anywhere in a database. This type of
-      # transaction is externally consistent. Clients should attempt to minimize the
-      # amount of time a transaction is active. Faster transactions commit with higher
-      # probability and cause less contention. Cloud Spanner attempts to keep read
-      # locks active as long as the transaction continues to do reads, and the
-      # transaction has not been terminated by Commit or Rollback. Long periods of
-      # inactivity at the client may cause Cloud Spanner to release a transaction's
-      # locks and abort it. Conceptually, a read-write transaction consists of zero or
-      # more reads or SQL statements followed by Commit. At any time before Commit,
-      # the client can send a Rollback request to abort the transaction. Semantics:
-      # Cloud Spanner can commit the transaction if all read locks it acquired are
-      # still valid at commit time, and it is able to acquire write locks for all
-      # writes. Cloud Spanner can abort the transaction for any reason. If a commit
-      # attempt returns `ABORTED`, Cloud Spanner guarantees that the transaction has
-      # not modified any user data in Cloud Spanner. Unless the transaction commits,
-      # Cloud Spanner makes no guarantees about how long the transaction's locks were
-      # held for. It is an error to use Cloud Spanner locks for any sort of mutual
-      # exclusion other than between Cloud Spanner transactions themselves. Retrying
-      # aborted transactions: When a transaction aborts, the application can choose to
-      # retry the whole transaction again. To maximize the chances of successfully
-      # committing the retry, the client should execute the retry in the same session
-      # as the original attempt. The original session's lock priority increases with
-      # each consecutive abort, meaning that each attempt has a slightly better chance
-      # of success than the previous. Note that the lock priority is preserved per
-      # session (not per transaction). Lock priority is set by the first read or write
-      # in the first attempt of a read-write transaction. If the application starts a
-      # new session to retry the whole transaction, the transaction loses its original
-      # lock priority. Moreover, the lock priority is only preserved if the
-      # transaction fails with an `ABORTED` error. Under some circumstances (for
-      # example, many transactions attempting to modify the same row(s)), a
-      # transaction can abort many times in a short period before successfully
-      # committing. Thus, it is not a good idea to cap the number of retries a
-      # transaction can attempt; instead, it is better to limit the total amount of
-      # time spent retrying. Idle transactions: A transaction is considered idle if it
-      # has no outstanding reads or SQL queries and has not started a read or SQL
-      # query within the last 10 seconds. Idle transactions can be aborted by Cloud
-      # Spanner so that they don't hold on to locks indefinitely. If an idle
-      # transaction is aborted, the commit will fail with error `ABORTED`. If this
-      # behavior is undesirable, periodically executing a simple SQL query in the
-      # transaction (for example, `SELECT 1`) prevents the transaction from becoming
-      # idle. Snapshot read-only transactions: Snapshot read-only transactions
-      # provides a simpler method than locking read-write transactions for doing
-      # several consistent reads. However, this type of transaction does not support
-      # writes. Snapshot transactions do not take locks. Instead, they work by
-      # choosing a Cloud Spanner timestamp, then executing all reads at that timestamp.
-      # Since they do not acquire locks, they do not block concurrent read-write
-      # transactions. Unlike locking read-write transactions, snapshot read-only
-      # transactions never abort. They can fail if the chosen read timestamp is
-      # garbage collected; however, the default garbage collection policy is generous
-      # enough that most applications do not need to worry about this in practice.
-      # Snapshot read-only transactions do not need to call Commit or Rollback (and in
-      # fact are not permitted to do so). To execute a snapshot transaction, the
-      # client specifies a timestamp bound, which tells Cloud Spanner how to choose a
-      # read timestamp. The types of timestamp bound are: - Strong (the default). -
-      # Bounded staleness. - Exact staleness. If the Cloud Spanner database to be read
-      # is geographically distributed, stale read-only transactions can execute more
-      # quickly than strong or read-write transactions, because they are able to
-      # execute far from the leader replica. Each type of timestamp bound is discussed
-      # in detail below. Strong: Strong reads are guaranteed to see the effects of all
-      # transactions that have committed before the start of the read. Furthermore,
-      # all rows yielded by a single read are consistent with each other -- if any
-      # part of the read observes a transaction, all parts of the read see the
-      # transaction. Strong reads are not repeatable: two consecutive strong read-only
-      # transactions might return inconsistent results if there are concurrent writes.
-      # If consistency across reads is required, the reads should be executed within a
-      # transaction or at an exact read timestamp. Queries on change streams (see
-      # below for more details) must also specify the strong read timestamp bound. See
-      # TransactionOptions.ReadOnly.strong. Exact staleness: These timestamp bounds
-      # execute reads at a user-specified timestamp. Reads at a timestamp are
-      # guaranteed to see a consistent prefix of the global transaction history: they
-      # observe modifications done by all transactions with a commit timestamp less
-      # than or equal to the read timestamp, and observe none of the modifications
-      # done by transactions with a larger commit timestamp. They will block until all
-      # conflicting transactions that may be assigned commit timestamps <= the read
-      # timestamp have finished. The timestamp can either be expressed as an absolute
-      # Cloud Spanner commit timestamp or a staleness relative to the current time.
-      # These modes do not require a "negotiation phase" to pick a timestamp. As a
-      # result, they execute slightly faster than the equivalent boundedly stale
-      # concurrency modes. On the other hand, boundedly stale reads usually return
-      # fresher results. See TransactionOptions.ReadOnly.read_timestamp and
-      # TransactionOptions.ReadOnly.exact_staleness. Bounded staleness: Bounded
-      # staleness modes allow Cloud Spanner to pick the read timestamp, subject to a
-      # user-provided staleness bound. Cloud Spanner chooses the newest timestamp
-      # within the staleness bound that allows execution of the reads at the closest
-      # available replica without blocking. All rows yielded are consistent with each
-      # other -- if any part of the read observes a transaction, all parts of the read
-      # see the transaction. Boundedly stale reads are not repeatable: two stale reads,
-      # even if they use the same staleness bound, can execute at different
-      # timestamps and thus return inconsistent results. Boundedly stale reads execute
-      # in two phases: the first phase negotiates a timestamp among all replicas
-      # needed to serve the read. In the second phase, reads are executed at the
-      # negotiated timestamp. As a result of the two phase execution, bounded
-      # staleness reads are usually a little slower than comparable exact staleness
-      # reads. However, they are typically able to return fresher results, and are
-      # more likely to execute at the closest replica. Because the timestamp
-      # negotiation requires up-front knowledge of which rows will be read, it can
-      # only be used with single-use read-only transactions. See TransactionOptions.
-      # ReadOnly.max_staleness and TransactionOptions.ReadOnly.min_read_timestamp. Old
-      # read timestamps and garbage collection: Cloud Spanner continuously garbage
-      # collects deleted and overwritten data in the background to reclaim storage
-      # space. This process is known as "version GC". By default, version GC reclaims
-      # versions after they are one hour old. Because of this, Cloud Spanner cannot
-      # perform reads at read timestamps more than one hour in the past. This
-      # restriction also applies to in-progress reads and/or SQL queries whose
-      # timestamp become too old while executing. Reads and SQL queries with too-old
-      # read timestamps fail with the error `FAILED_PRECONDITION`. You can configure
-      # and extend the `VERSION_RETENTION_PERIOD` of a database up to a period as long
-      # as one week, which allows Cloud Spanner to perform reads up to one week in the
-      # past. Querying change Streams: A Change Stream is a schema object that can be
-      # configured to watch data changes on the entire database, a set of tables, or a
-      # set of columns in a database. When a change stream is created, Spanner
-      # automatically defines a corresponding SQL Table-Valued Function (TVF) that can
-      # be used to query the change records in the associated change stream using the
-      # ExecuteStreamingSql API. The name of the TVF for a change stream is generated
-      # from the name of the change stream: READ_. All queries on change stream TVFs
-      # must be executed using the ExecuteStreamingSql API with a single-use read-only
-      # transaction with a strong read-only timestamp_bound. The change stream TVF
-      # allows users to specify the start_timestamp and end_timestamp for the time
-      # range of interest. All change records within the retention period is
-      # accessible using the strong read-only timestamp_bound. All other
-      # TransactionOptions are invalid for change stream queries. In addition, if
-      # TransactionOptions.read_only.return_read_timestamp is set to true, a special
-      # value of 2^63 - 2 will be returned in the Transaction message that describes
-      # the transaction, instead of a valid read timestamp. This special value should
-      # be discarded and not used for any subsequent queries. Please see https://cloud.
-      # google.com/spanner/docs/change-streams for more details on how to query the
-      # change stream TVFs. Partitioned DML transactions: Partitioned DML transactions
-      # are used to execute DML statements with a different execution strategy that
-      # provides different, and often better, scalability properties for large, table-
-      # wide operations than DML in a ReadWrite transaction. Smaller scoped statements,
-      # such as an OLTP workload, should prefer using ReadWrite transactions.
-      # Partitioned DML partitions the keyspace and runs the DML statement on each
-      # partition in separate, internal transactions. These transactions commit
-      # automatically when complete, and run independently from one another. To reduce
-      # lock contention, this execution strategy only acquires read locks on rows that
-      # match the WHERE clause of the statement. Additionally, the smaller per-
-      # partition transactions hold locks for less time. That said, Partitioned DML is
-      # not a drop-in replacement for standard DML used in ReadWrite transactions. -
-      # The DML statement must be fully-partitionable. Specifically, the statement
-      # must be expressible as the union of many statements which each access only a
-      # single row of the table. - The statement is not applied atomically to all rows
-      # of the table. Rather, the statement is applied atomically to partitions of the
-      # table, in independent transactions. Secondary index rows are updated
-      # atomically with the base table rows. - Partitioned DML does not guarantee
-      # exactly-once execution semantics against a partition. The statement is applied
-      # at least once to each partition. It is strongly recommended that the DML
-      # statement should be idempotent to avoid unexpected results. For instance, it
-      # is potentially dangerous to run a statement such as `UPDATE table SET column =
-      # column + 1` as it could be run multiple times against some rows. - The
-      # partitions are committed automatically - there is no support for Commit or
-      # Rollback. If the call returns an error, or if the client issuing the
-      # ExecuteSql call dies, it is possible that some rows had the statement executed
-      # on them successfully. It is also possible that statement was never executed
-      # against other rows. - Partitioned DML transactions may only contain the
-      # execution of a single DML statement via ExecuteSql or ExecuteStreamingSql. -
-      # If any error is encountered during the execution of the partitioned DML
-      # operation (for instance, a UNIQUE INDEX violation, division by zero, or a
-      # value that cannot be stored due to schema constraints), then the operation is
-      # stopped at that point and an error is returned. It is possible that at this
-      # point, some partitions have been committed (or even committed multiple times),
-      # and other partitions have not been run at all. Given the above, Partitioned
-      # DML is good fit for large, database-wide, operations that are idempotent, such
-      # as deleting old rows from a very large table.
+      # Options to use for transactions.
       class TransactionOptions
         include Google::Apis::Core::Hashable
       
-        # When `exclude_txn_from_change_streams` is set to `true`: * Modifications from
-        # this transaction will not be recorded in change streams with DDL option `
-        # allow_txn_exclusion=true` that are tracking columns modified by these
-        # transactions. * Modifications from this transaction will be 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 this transaction will be recorded in all change streams that are tracking
-        # columns modified by these transactions. `exclude_txn_from_change_streams` may
-        # only be specified for read-write or partitioned-dml transactions, otherwise
-        # the API will return an `INVALID_ARGUMENT` error.
+        # When `exclude_txn_from_change_streams` is set to `true`, it prevents read or
+        # write transactions from being tracked in change streams. * If the DDL option `
+        # allow_txn_exclusion` is set to `true`, then the updates made within this
+        # transaction aren't recorded in the change stream. * If you don't set the DDL
+        # option `allow_txn_exclusion` or if it's set to `false`, then the updates made
+        # within this transaction are recorded in the change stream. When `
+        # exclude_txn_from_change_streams` is set to `false` or not set, modifications
+        # from this transaction are recorded in all change streams that are tracking
+        # columns modified by these transactions. The `exclude_txn_from_change_streams`
+        # option can only be specified for read-write or partitioned DML transactions,
+        # otherwise the API returns an `INVALID_ARGUMENT` error.
         # Corresponds to the JSON property `excludeTxnFromChangeStreams`
         # @return [Boolean]
         attr_accessor :exclude_txn_from_change_streams
@@ -6733,198 +6775,7 @@ module Google
       class TransactionSelector
         include Google::Apis::Core::Hashable
       
-        # Transactions: Each session can have at most one active transaction at a time (
-        # note that standalone reads and queries use a transaction internally and do
-        # count towards the one transaction limit). After the active transaction is
-        # completed, the session can immediately be re-used for the next transaction. It
-        # is not necessary to create a new session for each transaction. Transaction
-        # modes: Cloud Spanner supports three transaction modes: 1. Locking read-write.
-        # This type of transaction is the only way to write data into Cloud Spanner.
-        # These transactions rely on pessimistic locking and, if necessary, two-phase
-        # commit. Locking read-write transactions may abort, requiring the application
-        # to retry. 2. Snapshot read-only. Snapshot read-only transactions provide
-        # guaranteed consistency across several reads, but do not allow writes. Snapshot
-        # read-only transactions can be configured to read at timestamps in the past, or
-        # configured to perform a strong read (where Spanner will select a timestamp
-        # such that the read is guaranteed to see the effects of all transactions that
-        # have committed before the start of the read). Snapshot read-only transactions
-        # do not need to be committed. Queries on change streams must be performed with
-        # the snapshot read-only transaction mode, specifying a strong read. See
-        # TransactionOptions.ReadOnly.strong for more details. 3. Partitioned DML. This
-        # type of transaction is used to execute a single Partitioned DML statement.
-        # Partitioned DML partitions the key space and runs the DML statement over each
-        # partition in parallel using separate, internal transactions that commit
-        # independently. Partitioned DML transactions do not need to be committed. For
-        # transactions that only read, snapshot read-only transactions provide simpler
-        # semantics and are almost always faster. In particular, read-only transactions
-        # do not take locks, so they do not conflict with read-write transactions. As a
-        # consequence of not taking locks, they also do not abort, so retry loops are
-        # not needed. Transactions may only read-write data in a single database. They
-        # may, however, read-write data in different tables within that database.
-        # Locking read-write transactions: Locking transactions may be used to
-        # atomically read-modify-write data anywhere in a database. This type of
-        # transaction is externally consistent. Clients should attempt to minimize the
-        # amount of time a transaction is active. Faster transactions commit with higher
-        # probability and cause less contention. Cloud Spanner attempts to keep read
-        # locks active as long as the transaction continues to do reads, and the
-        # transaction has not been terminated by Commit or Rollback. Long periods of
-        # inactivity at the client may cause Cloud Spanner to release a transaction's
-        # locks and abort it. Conceptually, a read-write transaction consists of zero or
-        # more reads or SQL statements followed by Commit. At any time before Commit,
-        # the client can send a Rollback request to abort the transaction. Semantics:
-        # Cloud Spanner can commit the transaction if all read locks it acquired are
-        # still valid at commit time, and it is able to acquire write locks for all
-        # writes. Cloud Spanner can abort the transaction for any reason. If a commit
-        # attempt returns `ABORTED`, Cloud Spanner guarantees that the transaction has
-        # not modified any user data in Cloud Spanner. Unless the transaction commits,
-        # Cloud Spanner makes no guarantees about how long the transaction's locks were
-        # held for. It is an error to use Cloud Spanner locks for any sort of mutual
-        # exclusion other than between Cloud Spanner transactions themselves. Retrying
-        # aborted transactions: When a transaction aborts, the application can choose to
-        # retry the whole transaction again. To maximize the chances of successfully
-        # committing the retry, the client should execute the retry in the same session
-        # as the original attempt. The original session's lock priority increases with
-        # each consecutive abort, meaning that each attempt has a slightly better chance
-        # of success than the previous. Note that the lock priority is preserved per
-        # session (not per transaction). Lock priority is set by the first read or write
-        # in the first attempt of a read-write transaction. If the application starts a
-        # new session to retry the whole transaction, the transaction loses its original
-        # lock priority. Moreover, the lock priority is only preserved if the
-        # transaction fails with an `ABORTED` error. Under some circumstances (for
-        # example, many transactions attempting to modify the same row(s)), a
-        # transaction can abort many times in a short period before successfully
-        # committing. Thus, it is not a good idea to cap the number of retries a
-        # transaction can attempt; instead, it is better to limit the total amount of
-        # time spent retrying. Idle transactions: A transaction is considered idle if it
-        # has no outstanding reads or SQL queries and has not started a read or SQL
-        # query within the last 10 seconds. Idle transactions can be aborted by Cloud
-        # Spanner so that they don't hold on to locks indefinitely. If an idle
-        # transaction is aborted, the commit will fail with error `ABORTED`. If this
-        # behavior is undesirable, periodically executing a simple SQL query in the
-        # transaction (for example, `SELECT 1`) prevents the transaction from becoming
-        # idle. Snapshot read-only transactions: Snapshot read-only transactions
-        # provides a simpler method than locking read-write transactions for doing
-        # several consistent reads. However, this type of transaction does not support
-        # writes. Snapshot transactions do not take locks. Instead, they work by
-        # choosing a Cloud Spanner timestamp, then executing all reads at that timestamp.
-        # Since they do not acquire locks, they do not block concurrent read-write
-        # transactions. Unlike locking read-write transactions, snapshot read-only
-        # transactions never abort. They can fail if the chosen read timestamp is
-        # garbage collected; however, the default garbage collection policy is generous
-        # enough that most applications do not need to worry about this in practice.
-        # Snapshot read-only transactions do not need to call Commit or Rollback (and in
-        # fact are not permitted to do so). To execute a snapshot transaction, the
-        # client specifies a timestamp bound, which tells Cloud Spanner how to choose a
-        # read timestamp. The types of timestamp bound are: - Strong (the default). -
-        # Bounded staleness. - Exact staleness. If the Cloud Spanner database to be read
-        # is geographically distributed, stale read-only transactions can execute more
-        # quickly than strong or read-write transactions, because they are able to
-        # execute far from the leader replica. Each type of timestamp bound is discussed
-        # in detail below. Strong: Strong reads are guaranteed to see the effects of all
-        # transactions that have committed before the start of the read. Furthermore,
-        # all rows yielded by a single read are consistent with each other -- if any
-        # part of the read observes a transaction, all parts of the read see the
-        # transaction. Strong reads are not repeatable: two consecutive strong read-only
-        # transactions might return inconsistent results if there are concurrent writes.
-        # If consistency across reads is required, the reads should be executed within a
-        # transaction or at an exact read timestamp. Queries on change streams (see
-        # below for more details) must also specify the strong read timestamp bound. See
-        # TransactionOptions.ReadOnly.strong. Exact staleness: These timestamp bounds
-        # execute reads at a user-specified timestamp. Reads at a timestamp are
-        # guaranteed to see a consistent prefix of the global transaction history: they
-        # observe modifications done by all transactions with a commit timestamp less
-        # than or equal to the read timestamp, and observe none of the modifications
-        # done by transactions with a larger commit timestamp. They will block until all
-        # conflicting transactions that may be assigned commit timestamps <= the read
-        # timestamp have finished. The timestamp can either be expressed as an absolute
-        # Cloud Spanner commit timestamp or a staleness relative to the current time.
-        # These modes do not require a "negotiation phase" to pick a timestamp. As a
-        # result, they execute slightly faster than the equivalent boundedly stale
-        # concurrency modes. On the other hand, boundedly stale reads usually return
-        # fresher results. See TransactionOptions.ReadOnly.read_timestamp and
-        # TransactionOptions.ReadOnly.exact_staleness. Bounded staleness: Bounded
-        # staleness modes allow Cloud Spanner to pick the read timestamp, subject to a
-        # user-provided staleness bound. Cloud Spanner chooses the newest timestamp
-        # within the staleness bound that allows execution of the reads at the closest
-        # available replica without blocking. All rows yielded are consistent with each
-        # other -- if any part of the read observes a transaction, all parts of the read
-        # see the transaction. Boundedly stale reads are not repeatable: two stale reads,
-        # even if they use the same staleness bound, can execute at different
-        # timestamps and thus return inconsistent results. Boundedly stale reads execute
-        # in two phases: the first phase negotiates a timestamp among all replicas
-        # needed to serve the read. In the second phase, reads are executed at the
-        # negotiated timestamp. As a result of the two phase execution, bounded
-        # staleness reads are usually a little slower than comparable exact staleness
-        # reads. However, they are typically able to return fresher results, and are
-        # more likely to execute at the closest replica. Because the timestamp
-        # negotiation requires up-front knowledge of which rows will be read, it can
-        # only be used with single-use read-only transactions. See TransactionOptions.
-        # ReadOnly.max_staleness and TransactionOptions.ReadOnly.min_read_timestamp. Old
-        # read timestamps and garbage collection: Cloud Spanner continuously garbage
-        # collects deleted and overwritten data in the background to reclaim storage
-        # space. This process is known as "version GC". By default, version GC reclaims
-        # versions after they are one hour old. Because of this, Cloud Spanner cannot
-        # perform reads at read timestamps more than one hour in the past. This
-        # restriction also applies to in-progress reads and/or SQL queries whose
-        # timestamp become too old while executing. Reads and SQL queries with too-old
-        # read timestamps fail with the error `FAILED_PRECONDITION`. You can configure
-        # and extend the `VERSION_RETENTION_PERIOD` of a database up to a period as long
-        # as one week, which allows Cloud Spanner to perform reads up to one week in the
-        # past. Querying change Streams: A Change Stream is a schema object that can be
-        # configured to watch data changes on the entire database, a set of tables, or a
-        # set of columns in a database. When a change stream is created, Spanner
-        # automatically defines a corresponding SQL Table-Valued Function (TVF) that can
-        # be used to query the change records in the associated change stream using the
-        # ExecuteStreamingSql API. The name of the TVF for a change stream is generated
-        # from the name of the change stream: READ_. All queries on change stream TVFs
-        # must be executed using the ExecuteStreamingSql API with a single-use read-only
-        # transaction with a strong read-only timestamp_bound. The change stream TVF
-        # allows users to specify the start_timestamp and end_timestamp for the time
-        # range of interest. All change records within the retention period is
-        # accessible using the strong read-only timestamp_bound. All other
-        # TransactionOptions are invalid for change stream queries. In addition, if
-        # TransactionOptions.read_only.return_read_timestamp is set to true, a special
-        # value of 2^63 - 2 will be returned in the Transaction message that describes
-        # the transaction, instead of a valid read timestamp. This special value should
-        # be discarded and not used for any subsequent queries. Please see https://cloud.
-        # google.com/spanner/docs/change-streams for more details on how to query the
-        # change stream TVFs. Partitioned DML transactions: Partitioned DML transactions
-        # are used to execute DML statements with a different execution strategy that
-        # provides different, and often better, scalability properties for large, table-
-        # wide operations than DML in a ReadWrite transaction. Smaller scoped statements,
-        # such as an OLTP workload, should prefer using ReadWrite transactions.
-        # Partitioned DML partitions the keyspace and runs the DML statement on each
-        # partition in separate, internal transactions. These transactions commit
-        # automatically when complete, and run independently from one another. To reduce
-        # lock contention, this execution strategy only acquires read locks on rows that
-        # match the WHERE clause of the statement. Additionally, the smaller per-
-        # partition transactions hold locks for less time. That said, Partitioned DML is
-        # not a drop-in replacement for standard DML used in ReadWrite transactions. -
-        # The DML statement must be fully-partitionable. Specifically, the statement
-        # must be expressible as the union of many statements which each access only a
-        # single row of the table. - The statement is not applied atomically to all rows
-        # of the table. Rather, the statement is applied atomically to partitions of the
-        # table, in independent transactions. Secondary index rows are updated
-        # atomically with the base table rows. - Partitioned DML does not guarantee
-        # exactly-once execution semantics against a partition. The statement is applied
-        # at least once to each partition. It is strongly recommended that the DML
-        # statement should be idempotent to avoid unexpected results. For instance, it
-        # is potentially dangerous to run a statement such as `UPDATE table SET column =
-        # column + 1` as it could be run multiple times against some rows. - The
-        # partitions are committed automatically - there is no support for Commit or
-        # Rollback. If the call returns an error, or if the client issuing the
-        # ExecuteSql call dies, it is possible that some rows had the statement executed
-        # on them successfully. It is also possible that statement was never executed
-        # against other rows. - Partitioned DML transactions may only contain the
-        # execution of a single DML statement via ExecuteSql or ExecuteStreamingSql. -
-        # If any error is encountered during the execution of the partitioned DML
-        # operation (for instance, a UNIQUE INDEX violation, division by zero, or a
-        # value that cannot be stored due to schema constraints), then the operation is
-        # stopped at that point and an error is returned. It is possible that at this
-        # point, some partitions have been committed (or even committed multiple times),
-        # and other partitions have not been run at all. Given the above, Partitioned
-        # DML is good fit for large, database-wide, operations that are idempotent, such
-        # as deleting old rows from a very large table.
+        # Options to use for transactions.
         # Corresponds to the JSON property `begin`
         # @return [Google::Apis::SpannerV1::TransactionOptions]
         attr_accessor :begin
@@ -6935,198 +6786,7 @@ module Google
         # @return [String]
         attr_accessor :id
       
-        # Transactions: Each session can have at most one active transaction at a time (
-        # note that standalone reads and queries use a transaction internally and do
-        # count towards the one transaction limit). After the active transaction is
-        # completed, the session can immediately be re-used for the next transaction. It
-        # is not necessary to create a new session for each transaction. Transaction
-        # modes: Cloud Spanner supports three transaction modes: 1. Locking read-write.
-        # This type of transaction is the only way to write data into Cloud Spanner.
-        # These transactions rely on pessimistic locking and, if necessary, two-phase
-        # commit. Locking read-write transactions may abort, requiring the application
-        # to retry. 2. Snapshot read-only. Snapshot read-only transactions provide
-        # guaranteed consistency across several reads, but do not allow writes. Snapshot
-        # read-only transactions can be configured to read at timestamps in the past, or
-        # configured to perform a strong read (where Spanner will select a timestamp
-        # such that the read is guaranteed to see the effects of all transactions that
-        # have committed before the start of the read). Snapshot read-only transactions
-        # do not need to be committed. Queries on change streams must be performed with
-        # the snapshot read-only transaction mode, specifying a strong read. See
-        # TransactionOptions.ReadOnly.strong for more details. 3. Partitioned DML. This
-        # type of transaction is used to execute a single Partitioned DML statement.
-        # Partitioned DML partitions the key space and runs the DML statement over each
-        # partition in parallel using separate, internal transactions that commit
-        # independently. Partitioned DML transactions do not need to be committed. For
-        # transactions that only read, snapshot read-only transactions provide simpler
-        # semantics and are almost always faster. In particular, read-only transactions
-        # do not take locks, so they do not conflict with read-write transactions. As a
-        # consequence of not taking locks, they also do not abort, so retry loops are
-        # not needed. Transactions may only read-write data in a single database. They
-        # may, however, read-write data in different tables within that database.
-        # Locking read-write transactions: Locking transactions may be used to
-        # atomically read-modify-write data anywhere in a database. This type of
-        # transaction is externally consistent. Clients should attempt to minimize the
-        # amount of time a transaction is active. Faster transactions commit with higher
-        # probability and cause less contention. Cloud Spanner attempts to keep read
-        # locks active as long as the transaction continues to do reads, and the
-        # transaction has not been terminated by Commit or Rollback. Long periods of
-        # inactivity at the client may cause Cloud Spanner to release a transaction's
-        # locks and abort it. Conceptually, a read-write transaction consists of zero or
-        # more reads or SQL statements followed by Commit. At any time before Commit,
-        # the client can send a Rollback request to abort the transaction. Semantics:
-        # Cloud Spanner can commit the transaction if all read locks it acquired are
-        # still valid at commit time, and it is able to acquire write locks for all
-        # writes. Cloud Spanner can abort the transaction for any reason. If a commit
-        # attempt returns `ABORTED`, Cloud Spanner guarantees that the transaction has
-        # not modified any user data in Cloud Spanner. Unless the transaction commits,
-        # Cloud Spanner makes no guarantees about how long the transaction's locks were
-        # held for. It is an error to use Cloud Spanner locks for any sort of mutual
-        # exclusion other than between Cloud Spanner transactions themselves. Retrying
-        # aborted transactions: When a transaction aborts, the application can choose to
-        # retry the whole transaction again. To maximize the chances of successfully
-        # committing the retry, the client should execute the retry in the same session
-        # as the original attempt. The original session's lock priority increases with
-        # each consecutive abort, meaning that each attempt has a slightly better chance
-        # of success than the previous. Note that the lock priority is preserved per
-        # session (not per transaction). Lock priority is set by the first read or write
-        # in the first attempt of a read-write transaction. If the application starts a
-        # new session to retry the whole transaction, the transaction loses its original
-        # lock priority. Moreover, the lock priority is only preserved if the
-        # transaction fails with an `ABORTED` error. Under some circumstances (for
-        # example, many transactions attempting to modify the same row(s)), a
-        # transaction can abort many times in a short period before successfully
-        # committing. Thus, it is not a good idea to cap the number of retries a
-        # transaction can attempt; instead, it is better to limit the total amount of
-        # time spent retrying. Idle transactions: A transaction is considered idle if it
-        # has no outstanding reads or SQL queries and has not started a read or SQL
-        # query within the last 10 seconds. Idle transactions can be aborted by Cloud
-        # Spanner so that they don't hold on to locks indefinitely. If an idle
-        # transaction is aborted, the commit will fail with error `ABORTED`. If this
-        # behavior is undesirable, periodically executing a simple SQL query in the
-        # transaction (for example, `SELECT 1`) prevents the transaction from becoming
-        # idle. Snapshot read-only transactions: Snapshot read-only transactions
-        # provides a simpler method than locking read-write transactions for doing
-        # several consistent reads. However, this type of transaction does not support
-        # writes. Snapshot transactions do not take locks. Instead, they work by
-        # choosing a Cloud Spanner timestamp, then executing all reads at that timestamp.
-        # Since they do not acquire locks, they do not block concurrent read-write
-        # transactions. Unlike locking read-write transactions, snapshot read-only
-        # transactions never abort. They can fail if the chosen read timestamp is
-        # garbage collected; however, the default garbage collection policy is generous
-        # enough that most applications do not need to worry about this in practice.
-        # Snapshot read-only transactions do not need to call Commit or Rollback (and in
-        # fact are not permitted to do so). To execute a snapshot transaction, the
-        # client specifies a timestamp bound, which tells Cloud Spanner how to choose a
-        # read timestamp. The types of timestamp bound are: - Strong (the default). -
-        # Bounded staleness. - Exact staleness. If the Cloud Spanner database to be read
-        # is geographically distributed, stale read-only transactions can execute more
-        # quickly than strong or read-write transactions, because they are able to
-        # execute far from the leader replica. Each type of timestamp bound is discussed
-        # in detail below. Strong: Strong reads are guaranteed to see the effects of all
-        # transactions that have committed before the start of the read. Furthermore,
-        # all rows yielded by a single read are consistent with each other -- if any
-        # part of the read observes a transaction, all parts of the read see the
-        # transaction. Strong reads are not repeatable: two consecutive strong read-only
-        # transactions might return inconsistent results if there are concurrent writes.
-        # If consistency across reads is required, the reads should be executed within a
-        # transaction or at an exact read timestamp. Queries on change streams (see
-        # below for more details) must also specify the strong read timestamp bound. See
-        # TransactionOptions.ReadOnly.strong. Exact staleness: These timestamp bounds
-        # execute reads at a user-specified timestamp. Reads at a timestamp are
-        # guaranteed to see a consistent prefix of the global transaction history: they
-        # observe modifications done by all transactions with a commit timestamp less
-        # than or equal to the read timestamp, and observe none of the modifications
-        # done by transactions with a larger commit timestamp. They will block until all
-        # conflicting transactions that may be assigned commit timestamps <= the read
-        # timestamp have finished. The timestamp can either be expressed as an absolute
-        # Cloud Spanner commit timestamp or a staleness relative to the current time.
-        # These modes do not require a "negotiation phase" to pick a timestamp. As a
-        # result, they execute slightly faster than the equivalent boundedly stale
-        # concurrency modes. On the other hand, boundedly stale reads usually return
-        # fresher results. See TransactionOptions.ReadOnly.read_timestamp and
-        # TransactionOptions.ReadOnly.exact_staleness. Bounded staleness: Bounded
-        # staleness modes allow Cloud Spanner to pick the read timestamp, subject to a
-        # user-provided staleness bound. Cloud Spanner chooses the newest timestamp
-        # within the staleness bound that allows execution of the reads at the closest
-        # available replica without blocking. All rows yielded are consistent with each
-        # other -- if any part of the read observes a transaction, all parts of the read
-        # see the transaction. Boundedly stale reads are not repeatable: two stale reads,
-        # even if they use the same staleness bound, can execute at different
-        # timestamps and thus return inconsistent results. Boundedly stale reads execute
-        # in two phases: the first phase negotiates a timestamp among all replicas
-        # needed to serve the read. In the second phase, reads are executed at the
-        # negotiated timestamp. As a result of the two phase execution, bounded
-        # staleness reads are usually a little slower than comparable exact staleness
-        # reads. However, they are typically able to return fresher results, and are
-        # more likely to execute at the closest replica. Because the timestamp
-        # negotiation requires up-front knowledge of which rows will be read, it can
-        # only be used with single-use read-only transactions. See TransactionOptions.
-        # ReadOnly.max_staleness and TransactionOptions.ReadOnly.min_read_timestamp. Old
-        # read timestamps and garbage collection: Cloud Spanner continuously garbage
-        # collects deleted and overwritten data in the background to reclaim storage
-        # space. This process is known as "version GC". By default, version GC reclaims
-        # versions after they are one hour old. Because of this, Cloud Spanner cannot
-        # perform reads at read timestamps more than one hour in the past. This
-        # restriction also applies to in-progress reads and/or SQL queries whose
-        # timestamp become too old while executing. Reads and SQL queries with too-old
-        # read timestamps fail with the error `FAILED_PRECONDITION`. You can configure
-        # and extend the `VERSION_RETENTION_PERIOD` of a database up to a period as long
-        # as one week, which allows Cloud Spanner to perform reads up to one week in the
-        # past. Querying change Streams: A Change Stream is a schema object that can be
-        # configured to watch data changes on the entire database, a set of tables, or a
-        # set of columns in a database. When a change stream is created, Spanner
-        # automatically defines a corresponding SQL Table-Valued Function (TVF) that can
-        # be used to query the change records in the associated change stream using the
-        # ExecuteStreamingSql API. The name of the TVF for a change stream is generated
-        # from the name of the change stream: READ_. All queries on change stream TVFs
-        # must be executed using the ExecuteStreamingSql API with a single-use read-only
-        # transaction with a strong read-only timestamp_bound. The change stream TVF
-        # allows users to specify the start_timestamp and end_timestamp for the time
-        # range of interest. All change records within the retention period is
-        # accessible using the strong read-only timestamp_bound. All other
-        # TransactionOptions are invalid for change stream queries. In addition, if
-        # TransactionOptions.read_only.return_read_timestamp is set to true, a special
-        # value of 2^63 - 2 will be returned in the Transaction message that describes
-        # the transaction, instead of a valid read timestamp. This special value should
-        # be discarded and not used for any subsequent queries. Please see https://cloud.
-        # google.com/spanner/docs/change-streams for more details on how to query the
-        # change stream TVFs. Partitioned DML transactions: Partitioned DML transactions
-        # are used to execute DML statements with a different execution strategy that
-        # provides different, and often better, scalability properties for large, table-
-        # wide operations than DML in a ReadWrite transaction. Smaller scoped statements,
-        # such as an OLTP workload, should prefer using ReadWrite transactions.
-        # Partitioned DML partitions the keyspace and runs the DML statement on each
-        # partition in separate, internal transactions. These transactions commit
-        # automatically when complete, and run independently from one another. To reduce
-        # lock contention, this execution strategy only acquires read locks on rows that
-        # match the WHERE clause of the statement. Additionally, the smaller per-
-        # partition transactions hold locks for less time. That said, Partitioned DML is
-        # not a drop-in replacement for standard DML used in ReadWrite transactions. -
-        # The DML statement must be fully-partitionable. Specifically, the statement
-        # must be expressible as the union of many statements which each access only a
-        # single row of the table. - The statement is not applied atomically to all rows
-        # of the table. Rather, the statement is applied atomically to partitions of the
-        # table, in independent transactions. Secondary index rows are updated
-        # atomically with the base table rows. - Partitioned DML does not guarantee
-        # exactly-once execution semantics against a partition. The statement is applied
-        # at least once to each partition. It is strongly recommended that the DML
-        # statement should be idempotent to avoid unexpected results. For instance, it
-        # is potentially dangerous to run a statement such as `UPDATE table SET column =
-        # column + 1` as it could be run multiple times against some rows. - The
-        # partitions are committed automatically - there is no support for Commit or
-        # Rollback. If the call returns an error, or if the client issuing the
-        # ExecuteSql call dies, it is possible that some rows had the statement executed
-        # on them successfully. It is also possible that statement was never executed
-        # against other rows. - Partitioned DML transactions may only contain the
-        # execution of a single DML statement via ExecuteSql or ExecuteStreamingSql. -
-        # If any error is encountered during the execution of the partitioned DML
-        # operation (for instance, a UNIQUE INDEX violation, division by zero, or a
-        # value that cannot be stored due to schema constraints), then the operation is
-        # stopped at that point and an error is returned. It is possible that at this
-        # point, some partitions have been committed (or even committed multiple times),
-        # and other partitions have not been run at all. Given the above, Partitioned
-        # DML is good fit for large, database-wide, operations that are idempotent, such
-        # as deleting old rows from a very large table.
+        # Options to use for transactions.
         # Corresponds to the JSON property `singleUse`
         # @return [Google::Apis::SpannerV1::TransactionOptions]
         attr_accessor :single_use