RubyGems - google-apis-spanner_v1 - Versions diffs - 0.12.0 → 0.16.0 - Mend

google-apis-spanner_v1 0.12.0 → 0.16.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (6) hide show

checksums.yaml +4 -4
data/CHANGELOG.md +18 -0
data/lib/google/apis/spanner_v1/classes.rb +219 -192
data/lib/google/apis/spanner_v1/gem_version.rb +3 -3
data/lib/google/apis/spanner_v1/representations.rb +3 -0
metadata +13 -7

checksums.yaml CHANGED Viewed

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0d2fdc362ea9ccbcf33b9234e1128298167bfc5b681ed05c2b146892d4a12adf
-  data.tar.gz: 4652b768176472da6fa3742b6b947bed6682e460b85777c1f9ed569baa61dd58
+  metadata.gz: 6fbddcaa4658b3147d2258f83f732fdc5679b6d762e0c0aeeb120e6ad5f3726e
+  data.tar.gz: 3cd473218d291908672f0095738a11a7cd0ded8e15bc23edf465769340a9e710
 SHA512:
-  metadata.gz: 6112ac00d9e5f291b543d05a8dc1e92dbfc4ec4af92d25f17b8897f933ba39cf6dfd5c1b7ef4d9b8e2f162c89e38486981dfb52059900b6e62810cbc073a1002
-  data.tar.gz: 3505dbe22c9c699c1bc9ad822fe1841498ea3e4a54bd6e39b05baf789988661f2af638fbffa2c984d9f7db2b72f45d9b53b1a953365f399e0ef061098b14e868
+  metadata.gz: 22f24dbab2d23ac55ee2af9bf16a2f5e08ca79ce262a0d4debeddad921c6a7d9df01b621af41b15257761762e3e19eddc0be9844d002db75387761773099956d
+  data.tar.gz: 1c44606e7033bfb89ffa6651054412a552e4f05e3b4a66138135a19b32fc6c2d9149bc3ac519ca0b010607616fa08c88198774f96d9d9a31fd61f07a210fee60

data/CHANGELOG.md CHANGED Viewed

@@ -1,5 +1,23 @@
 # Release history for google-apis-spanner_v1
+### v0.16.0 (2021-07-31)
+* Regenerated from discovery document revision 20210723
+### v0.15.0 (2021-07-12)
+* Regenerated from discovery document revision 20210703
+### v0.14.0 (2021-07-03)
+* Regenerated from discovery document revision 20210624
+* Regenerated using generator version 0.4.0
+* Unspecified changes
+### v0.13.0 (2021-06-17)
+* Regenerated from discovery document revision 20210611
 ### v0.12.0 (2021-06-10)
 * Regenerated from discovery document revision 20210603

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

@@ -201,12 +201,12 @@ module Google
       class BeginTransactionRequest
         include Google::Apis::Core::Hashable
-        # # Transactions Each session can have at most one active transaction at a time (
+        # 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.
+        # 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
@@ -224,8 +224,8 @@ module Google
         # 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
+        # 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
@@ -234,7 +234,7 @@ module Google
         # 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
+        # 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
@@ -242,24 +242,24 @@ module Google
         # 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. Under some circumstances (
-        # e.g., 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 wall 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. In that case, the commit will fail with error
-        # `ABORTED`. If this behavior is undesirable, periodically executing a simple
-        # SQL query in the transaction (e.g., `SELECT 1`) prevents the transaction from
-        # becoming idle. ## Snapshot Read-Only Transactions Snapshot read-only
+        # 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. Under some circumstances (e.g., 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 wall 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. In that case, the commit will fail with error `
+        # ABORTED`. If this behavior is undesirable, periodically executing a simple SQL
+        # query in the transaction (e.g., `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
@@ -277,15 +277,15 @@ module Google
         # is geographically distributed, stale read-only transactions can execute more
         # quickly than strong or read-write transaction, 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,
+        # 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. See TransactionOptions.ReadOnly.
-        # strong. ## Exact Staleness These timestamp bounds execute reads at a user-
+        # 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 <= the read timestamp, and observe
@@ -297,8 +297,8 @@ module Google
         # 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
+        # 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
@@ -315,15 +315,15 @@ module Google
         # 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
+        # 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`. ##
-        # Partitioned DML Transactions Partitioned DML transactions are used to execute
+        # with too-old read timestamps fail with the error `FAILED_PRECONDITION`.
+        # 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
@@ -512,12 +512,12 @@ 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 (
+        # 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.
+        # 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
@@ -535,8 +535,8 @@ module Google
         # 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
+        # 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
@@ -545,7 +545,7 @@ module Google
         # 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
+        # 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
@@ -553,24 +553,24 @@ module Google
         # 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. Under some circumstances (
-        # e.g., 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 wall 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. In that case, the commit will fail with error
-        # `ABORTED`. If this behavior is undesirable, periodically executing a simple
-        # SQL query in the transaction (e.g., `SELECT 1`) prevents the transaction from
-        # becoming idle. ## Snapshot Read-Only Transactions Snapshot read-only
+        # 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. Under some circumstances (e.g., 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 wall 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. In that case, the commit will fail with error `
+        # ABORTED`. If this behavior is undesirable, periodically executing a simple SQL
+        # query in the transaction (e.g., `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
@@ -588,15 +588,15 @@ module Google
         # is geographically distributed, stale read-only transactions can execute more
         # quickly than strong or read-write transaction, 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,
+        # 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. See TransactionOptions.ReadOnly.
-        # strong. ## Exact Staleness These timestamp bounds execute reads at a user-
+        # 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 <= the read timestamp, and observe
@@ -608,8 +608,8 @@ module Google
         # 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
+        # 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
@@ -626,15 +626,15 @@ module Google
         # 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
+        # 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`. ##
-        # Partitioned DML Transactions Partitioned DML transactions are used to execute
+        # with too-old read timestamps fail with the error `FAILED_PRECONDITION`.
+        # 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
@@ -980,6 +980,14 @@ module Google
         # @return [String]
         attr_accessor :create_time
+        # Output only. The read-write region which contains the database's leader
+        # replicas. This is the same as the value of default_leader database option set
+        # using DatabaseAdmin.CreateDatabase or DatabaseAdmin.UpdateDatabaseDdl. If not
+        # explicitly set, this is empty.
+        # Corresponds to the JSON property `defaultLeader`
+        # @return [String]
+        attr_accessor :default_leader
         # Output only. Earliest timestamp at which older versions of the data can be
         # read. This value is continuously updated by Cloud Spanner and becomes stale
         # the moment it is queried. If you are using this value to recover data, make
@@ -1036,6 +1044,7 @@ module Google
         # Update properties of this object
         def update!(**args)
           @create_time = args[:create_time] if args.key?(:create_time)
+          @default_leader = args[:default_leader] if args.key?(:default_leader)
           @earliest_version_time = args[:earliest_version_time] if args.key?(:earliest_version_time)
           @encryption_config = args[:encryption_config] if args.key?(:encryption_config)
           @encryption_info = args[:encryption_info] if args.key?(:encryption_info)
@@ -1664,17 +1673,20 @@ module Google
         # @return [String]
         attr_accessor :name
-        # The number of nodes allocated to this instance. This may be zero in API
-        # responses for instances that are not yet in state `READY`. See [the
-        # documentation](https://cloud.google.com/spanner/docs/instances#node_count) for
-        # more information about nodes.
+        # The number of nodes allocated to this instance. At most one of either
+        # node_count or processing_units should be present in the message. This may be
+        # zero in API responses for instances that are not yet in state `READY`. See [
+        # the documentation](https://cloud.google.com/spanner/docs/compute-capacity) for
+        # more information about nodes and processing units.
         # Corresponds to the JSON property `nodeCount`
         # @return [Fixnum]
         attr_accessor :node_count
         # The number of processing units allocated to this instance. At most one of
         # processing_units or node_count should be present in the message. This may be
-        # zero in API responses for instances that are not yet in state `READY`.
+        # zero in API responses for instances that are not yet in state `READY`. See [
+        # the documentation](https://cloud.google.com/spanner/docs/compute-capacity) for
+        # more information about nodes and processing units.
         # Corresponds to the JSON property `processingUnits`
         # @return [Fixnum]
         attr_accessor :processing_units
@@ -1713,6 +1725,12 @@ module Google
         # @return [String]
         attr_accessor :display_name
+        # Allowed values of the “default_leader” schema option for databases in
+        # instances that use this instance configuration.
+        # Corresponds to the JSON property `leaderOptions`
+        # @return [Array<String>]
+        attr_accessor :leader_options
         # A unique identifier for the instance configuration. Values are of the form `
         # projects//instanceConfigs/a-z*`
         # Corresponds to the JSON property `name`
@@ -1732,6 +1750,7 @@ module Google
         # Update properties of this object
         def update!(**args)
           @display_name = args[:display_name] if args.key?(:display_name)
+          @leader_options = args[:leader_options] if args.key?(:leader_options)
           @name = args[:name] if args.key?(:name)
           @replicas = args[:replicas] if args.key?(:replicas)
         end
@@ -1847,6 +1866,11 @@ module Google
         # @return [Fixnum]
         attr_accessor :start_key_index
+        # The time offset. This is the time since the start of the time interval.
+        # Corresponds to the JSON property `timeOffset`
+        # @return [String]
+        attr_accessor :time_offset
         # A message representing a user-facing string whose value may need to be
         # translated before being displayed.
         # Corresponds to the JSON property `unit`
@@ -1870,6 +1894,7 @@ module Google
           @keys_count = args[:keys_count] if args.key?(:keys_count)
           @metric = args[:metric] if args.key?(:metric)
           @start_key_index = args[:start_key_index] if args.key?(:start_key_index)
+          @time_offset = args[:time_offset] if args.key?(:time_offset)
           @unit = args[:unit] if args.key?(:unit)
           @value = args[:value] if args.key?(:value)
         end
@@ -3313,7 +3338,8 @@ module Google
         # requests where it's not applicable (e.g. CommitRequest). Legal characters for `
         # request_tag` values are all printable characters (ASCII 32 - 126) and the
         # length of a request_tag is limited to 50 characters. Values that exceed this
-        # limit are truncated.
+        # limit are truncated. Any leading underscore (_) characters will be removed
+        # from the string.
         # Corresponds to the JSON property `requestTag`
         # @return [String]
         attr_accessor :request_tag
@@ -3325,7 +3351,8 @@ module Google
         # transaction, transaction_tag will be ignored. Legal characters for `
         # transaction_tag` values are all printable characters (ASCII 32 - 126) and the
         # length of a transaction_tag is limited to 50 characters. Values that exceed
-        # this limit are truncated.
+        # this limit are truncated. Any leading underscore (_) characters will be
+        # removed from the string.
         # Corresponds to the JSON property `transactionTag`
         # @return [String]
         attr_accessor :transaction_tag
@@ -3983,12 +4010,12 @@ module Google
         end
       end
-      # # Transactions Each session can have at most one active transaction at a time (
+      # 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.
+      # 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
@@ -4006,8 +4033,8 @@ module Google
       # 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
+      # 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
@@ -4016,7 +4043,7 @@ module Google
       # 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
+      # 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
@@ -4024,24 +4051,24 @@ module Google
       # 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. Under some circumstances (
-      # e.g., 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 wall 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. In that case, the commit will fail with error
-      # `ABORTED`. If this behavior is undesirable, periodically executing a simple
-      # SQL query in the transaction (e.g., `SELECT 1`) prevents the transaction from
-      # becoming idle. ## Snapshot Read-Only Transactions Snapshot read-only
+      # 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. Under some circumstances (e.g., 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 wall 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. In that case, the commit will fail with error `
+      # ABORTED`. If this behavior is undesirable, periodically executing a simple SQL
+      # query in the transaction (e.g., `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
@@ -4059,15 +4086,15 @@ module Google
       # is geographically distributed, stale read-only transactions can execute more
       # quickly than strong or read-write transaction, 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,
+      # 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. See TransactionOptions.ReadOnly.
-      # strong. ## Exact Staleness These timestamp bounds execute reads at a user-
+      # 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 <= the read timestamp, and observe
@@ -4079,8 +4106,8 @@ module Google
       # 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
+      # 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
@@ -4097,15 +4124,15 @@ module Google
       # 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
+      # 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`. ##
-      # Partitioned DML Transactions Partitioned DML transactions are used to execute
+      # with too-old read timestamps fail with the error `FAILED_PRECONDITION`.
+      # 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
@@ -4178,12 +4205,12 @@ module Google
       class TransactionSelector
         include Google::Apis::Core::Hashable
-        # # Transactions Each session can have at most one active transaction at a time (
+        # 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.
+        # 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
@@ -4201,8 +4228,8 @@ module Google
         # 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
+        # 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
@@ -4211,7 +4238,7 @@ module Google
         # 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
+        # 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
@@ -4219,24 +4246,24 @@ module Google
         # 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. Under some circumstances (
-        # e.g., 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 wall 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. In that case, the commit will fail with error
-        # `ABORTED`. If this behavior is undesirable, periodically executing a simple
-        # SQL query in the transaction (e.g., `SELECT 1`) prevents the transaction from
-        # becoming idle. ## Snapshot Read-Only Transactions Snapshot read-only
+        # 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. Under some circumstances (e.g., 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 wall 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. In that case, the commit will fail with error `
+        # ABORTED`. If this behavior is undesirable, periodically executing a simple SQL
+        # query in the transaction (e.g., `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
@@ -4254,15 +4281,15 @@ module Google
         # is geographically distributed, stale read-only transactions can execute more
         # quickly than strong or read-write transaction, 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,
+        # 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. See TransactionOptions.ReadOnly.
-        # strong. ## Exact Staleness These timestamp bounds execute reads at a user-
+        # 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 <= the read timestamp, and observe
@@ -4274,8 +4301,8 @@ module Google
         # 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
+        # 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
@@ -4292,15 +4319,15 @@ module Google
         # 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
+        # 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`. ##
-        # Partitioned DML Transactions Partitioned DML transactions are used to execute
+        # with too-old read timestamps fail with the error `FAILED_PRECONDITION`.
+        # 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
@@ -4347,12 +4374,12 @@ module Google
         # @return [String]
         attr_accessor :id
-        # # Transactions Each session can have at most one active transaction at a time (
+        # 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.
+        # 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
@@ -4370,8 +4397,8 @@ module Google
         # 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
+        # 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
@@ -4380,7 +4407,7 @@ module Google
         # 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
+        # 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
@@ -4388,24 +4415,24 @@ module Google
         # 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. Under some circumstances (
-        # e.g., 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 wall 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. In that case, the commit will fail with error
-        # `ABORTED`. If this behavior is undesirable, periodically executing a simple
-        # SQL query in the transaction (e.g., `SELECT 1`) prevents the transaction from
-        # becoming idle. ## Snapshot Read-Only Transactions Snapshot read-only
+        # 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. Under some circumstances (e.g., 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 wall 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. In that case, the commit will fail with error `
+        # ABORTED`. If this behavior is undesirable, periodically executing a simple SQL
+        # query in the transaction (e.g., `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
@@ -4423,15 +4450,15 @@ module Google
         # is geographically distributed, stale read-only transactions can execute more
         # quickly than strong or read-write transaction, 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,
+        # 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. See TransactionOptions.ReadOnly.
-        # strong. ## Exact Staleness These timestamp bounds execute reads at a user-
+        # 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 <= the read timestamp, and observe
@@ -4443,8 +4470,8 @@ module Google
         # 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
+        # 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
@@ -4461,15 +4488,15 @@ module Google
         # 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
+        # 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`. ##
-        # Partitioned DML Transactions Partitioned DML transactions are used to execute
+        # with too-old read timestamps fail with the error `FAILED_PRECONDITION`.
+        # 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

data/lib/google/apis/spanner_v1/gem_version.rb CHANGED Viewed

@@ -16,13 +16,13 @@ module Google
   module Apis
     module SpannerV1
       # Version of the google-apis-spanner_v1 gem
-      GEM_VERSION = "0.12.0"
+      GEM_VERSION = "0.16.0"
       # Version of the code generator used to generate this client
-      GENERATOR_VERSION = "0.3.0"
+      GENERATOR_VERSION = "0.4.0"
       # Revision of the discovery document this client was generated from
-      REVISION = "20210603"
+      REVISION = "20210723"
     end
   end
 end

data/lib/google/apis/spanner_v1/representations.rb CHANGED Viewed

@@ -807,6 +807,7 @@ module Google
         # @private
         class Representation < Google::Apis::Core::JsonRepresentation
           property :create_time, as: 'createTime'
+          property :default_leader, as: 'defaultLeader'
           property :earliest_version_time, as: 'earliestVersionTime'
           property :encryption_config, as: 'encryptionConfig', class: Google::Apis::SpannerV1::EncryptionConfig, decorator: Google::Apis::SpannerV1::EncryptionConfig::Representation
@@ -993,6 +994,7 @@ module Google
         # @private
         class Representation < Google::Apis::Core::JsonRepresentation
           property :display_name, as: 'displayName'
+          collection :leader_options, as: 'leaderOptions'
           property :name, as: 'name'
           collection :replicas, as: 'replicas', class: Google::Apis::SpannerV1::ReplicaInfo, decorator: Google::Apis::SpannerV1::ReplicaInfo::Representation
@@ -1021,6 +1023,7 @@ module Google
           property :metric, as: 'metric', class: Google::Apis::SpannerV1::LocalizedString, decorator: Google::Apis::SpannerV1::LocalizedString::Representation
           property :start_key_index, as: 'startKeyIndex'
+          property :time_offset, as: 'timeOffset'
           property :unit, as: 'unit', class: Google::Apis::SpannerV1::LocalizedString, decorator: Google::Apis::SpannerV1::LocalizedString::Representation
           property :value, as: 'value'

metadata CHANGED Viewed

@@ -1,29 +1,35 @@
 --- !ruby/object:Gem::Specification
 name: google-apis-spanner_v1
 version: !ruby/object:Gem::Version
-  version: 0.12.0
+  version: 0.16.0
 platform: ruby
 authors:
 - Google LLC
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2021-06-14 00:00:00.000000000 Z
+date: 2021-08-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: google-apis-core
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '0.1'
+        version: '0.4'
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: 2.a
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0.4'
+    - - "<"
       - !ruby/object:Gem::Version
-        version: '0.1'
+        version: 2.a
 description: This is the simple REST client for Cloud Spanner API V1. Simple REST
   clients are Ruby client libraries that provide access to Google services via their
   HTTP REST API endpoints. These libraries are generated and updated automatically
@@ -52,7 +58,7 @@ licenses:
 metadata:
   bug_tracker_uri: https://github.com/googleapis/google-api-ruby-client/issues
   changelog_uri: https://github.com/googleapis/google-api-ruby-client/tree/master/generated/google-apis-spanner_v1/CHANGELOG.md
-  documentation_uri: https://googleapis.dev/ruby/google-apis-spanner_v1/v0.12.0
+  documentation_uri: https://googleapis.dev/ruby/google-apis-spanner_v1/v0.16.0
   source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/master/generated/google-apis-spanner_v1
 post_install_message:
 rdoc_options: []