google-apis-spanner_v1 0.9.0 → 0.14.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f1243dcf90ea82fda1dae00b5a98f84e653b2610e887b6633aac5b573249cc70
-  data.tar.gz: f0db958321c5009cac506b1ee4fb9e798020ce6de390e8283ec354c27812781e
+  metadata.gz: c4e365d7961157ce00c492b5c328fa3c75dec95f6561ded7c8d039d1f9e10a76
+  data.tar.gz: b9c001b73c4739d5f9bc617a7ad516860e413858e27267746432178315cccb6b
 SHA512:
-  metadata.gz: '01860fbbfdb61ed4fb3da58328c6ab11769097d7ca2d52dbc5234eecb147fef348920a724138f6918d65c8e7bdbffd717fde36ee51e39a14d836f1324ede17aa'
-  data.tar.gz: bf892f11e0fa5beac035efccbb672c87d0a18d6de49c0fe0a0dbd1890a1c4a4ed0f9bb4c74ba52adb07d2e4227c09b49fb4847413ff8e4f3ba55f3d507d563d6
+  metadata.gz: 855b5dee0234ceec4ec8b23d29766e9a29032d37753385df1bdbd48868763c48202a8a98f3441e85764403a9232b7bff6130bbbc1397ca40d873900469bc3229
+  data.tar.gz: 4a6fad9130539418072cf2b8c60344d7c1d9767d5ca77ac8416c4b04a92310fb0decf60f8a3772e14cc42289b3a833e72464c780021faca87fba8bc12feeeab8

data/CHANGELOG.md

@@ -1,5 +1,29 @@
 # Release history for google-apis-spanner_v1
 
+### 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
+
+### v0.11.0 (2021-06-03)
+
+* Regenerated from discovery document revision 20210527
+* Regenerated using generator version 0.3.0
+
+### v0.10.0 (2021-05-22)
+
+* Regenerated from discovery document revision 20210517
+* Unspecified changes
+
 ### v0.9.0 (2021-04-17)
 
 * Regenerated from discovery document revision 20210405

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

@@ -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
@@ -727,11 +727,11 @@ module Google
         # The total number of mutations for the transaction. Knowing the `mutation_count`
         # value can help you maximize the number of mutations in a transaction and
         # minimize the number of API round trips. You can also monitor this value to
-        # prevent transactions from exceeding the system [limit](http://cloud.google.com/
-        # spanner/quotas#limits_for_creating_reading_updating_and_deleting_data). If the
-        # number of mutations exceeds the limit, the server returns [INVALID_ARGUMENT](
-        # http://cloud.google.com/spanner/docs/reference/rest/v1/Code#ENUM_VALUES.
-        # INVALID_ARGUMENT).
+        # prevent transactions from exceeding the system [limit](https://cloud.google.
+        # com/spanner/quotas#limits_for_creating_reading_updating_and_deleting_data). If
+        # the number of mutations exceeds the limit, the server returns [
+        # INVALID_ARGUMENT](https://cloud.google.com/spanner/docs/reference/rest/v1/Code#
+        # ENUM_VALUES.INVALID_ARGUMENT).
         # Corresponds to the JSON property `mutationCount`
         # @return [Fixnum]
         attr_accessor :mutation_count
@@ -746,6 +746,45 @@ module Google
         end
       end
       
+      # A message representing context for a KeyRangeInfo, including a label, value,
+      # unit, and severity.
+      class ContextValue
+        include Google::Apis::Core::Hashable
+      
+        # A message representing a user-facing string whose value may need to be
+        # translated before being displayed.
+        # Corresponds to the JSON property `label`
+        # @return [Google::Apis::SpannerV1::LocalizedString]
+        attr_accessor :label
+      
+        # The severity of this context.
+        # Corresponds to the JSON property `severity`
+        # @return [String]
+        attr_accessor :severity
+      
+        # The unit of the context value.
+        # Corresponds to the JSON property `unit`
+        # @return [String]
+        attr_accessor :unit
+      
+        # The value for the context.
+        # Corresponds to the JSON property `value`
+        # @return [Float]
+        attr_accessor :value
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @label = args[:label] if args.key?(:label)
+          @severity = args[:severity] if args.key?(:severity)
+          @unit = args[:unit] if args.key?(:unit)
+          @value = args[:value] if args.key?(:value)
+        end
+      end
+      
       # Metadata type for the operation returned by CreateBackup.
       class CreateBackupMetadata
         include Google::Apis::Core::Hashable
@@ -1036,6 +1075,85 @@ module Google
         end
       end
       
+      # A message representing a derived metric.
+      class DerivedMetric
+        include Google::Apis::Core::Hashable
+      
+        # A message representing a user-facing string whose value may need to be
+        # translated before being displayed.
+        # Corresponds to the JSON property `denominator`
+        # @return [Google::Apis::SpannerV1::LocalizedString]
+        attr_accessor :denominator
+      
+        # A message representing a user-facing string whose value may need to be
+        # translated before being displayed.
+        # Corresponds to the JSON property `numerator`
+        # @return [Google::Apis::SpannerV1::LocalizedString]
+        attr_accessor :numerator
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @denominator = args[:denominator] if args.key?(:denominator)
+          @numerator = args[:numerator] if args.key?(:numerator)
+        end
+      end
+      
+      # A message representing the key visualizer diagnostic messages.
+      class DiagnosticMessage
+        include Google::Apis::Core::Hashable
+      
+        # A message representing a user-facing string whose value may need to be
+        # translated before being displayed.
+        # Corresponds to the JSON property `info`
+        # @return [Google::Apis::SpannerV1::LocalizedString]
+        attr_accessor :info
+      
+        # A message representing a user-facing string whose value may need to be
+        # translated before being displayed.
+        # Corresponds to the JSON property `metric`
+        # @return [Google::Apis::SpannerV1::LocalizedString]
+        attr_accessor :metric
+      
+        # Whether this message is specific only for the current metric. By default
+        # Diagnostics are shown for all metrics, regardless which metric is the
+        # currently selected metric in the UI. However occasionally a metric will
+        # generate so many messages that the resulting visual clutter becomes
+        # overwhelming. In this case setting this to true, will show the diagnostic
+        # messages for that metric only if it is the currently selected metric.
+        # Corresponds to the JSON property `metricSpecific`
+        # @return [Boolean]
+        attr_accessor :metric_specific
+        alias_method :metric_specific?, :metric_specific
+      
+        # The severity of the diagnostic message.
+        # Corresponds to the JSON property `severity`
+        # @return [String]
+        attr_accessor :severity
+      
+        # A message representing a user-facing string whose value may need to be
+        # translated before being displayed.
+        # Corresponds to the JSON property `shortMessage`
+        # @return [Google::Apis::SpannerV1::LocalizedString]
+        attr_accessor :short_message
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @info = args[:info] if args.key?(:info)
+          @metric = args[:metric] if args.key?(:metric)
+          @metric_specific = args[:metric_specific] if args.key?(:metric_specific)
+          @severity = args[:severity] if args.key?(:severity)
+          @short_message = args[:short_message] if args.key?(:short_message)
+        end
+      end
+      
       # A generic empty message that you can re-use to avoid defining duplicated empty
       # messages in your APIs. A typical example is to use it as the request or the
       # response type of an API method. For instance: service Foo ` rpc Bar(google.
@@ -1454,6 +1572,49 @@ module Google
         end
       end
       
+      # A message representing a (sparse) collection of hot keys for specific key
+      # buckets.
+      class IndexedHotKey
+        include Google::Apis::Core::Hashable
+      
+        # A (sparse) mapping from key bucket index to the index of the specific hot row
+        # key for that key bucket. The index of the hot row key can be translated to the
+        # actual row key via the ScanData.VisualizationData.indexed_keys repeated field.
+        # Corresponds to the JSON property `sparseHotKeys`
+        # @return [Hash<String,Fixnum>]
+        attr_accessor :sparse_hot_keys
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @sparse_hot_keys = args[:sparse_hot_keys] if args.key?(:sparse_hot_keys)
+        end
+      end
+      
+      # A message representing a (sparse) collection of KeyRangeInfos for specific key
+      # buckets.
+      class IndexedKeyRangeInfos
+        include Google::Apis::Core::Hashable
+      
+        # A (sparse) mapping from key bucket index to the KeyRangeInfos for that key
+        # bucket.
+        # Corresponds to the JSON property `keyRangeInfos`
+        # @return [Hash<String,Google::Apis::SpannerV1::KeyRangeInfos>]
+        attr_accessor :key_range_infos
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @key_range_infos = args[:key_range_infos] if args.key?(:key_range_infos)
+        end
+      end
+      
       # An isolated set of Cloud Spanner resources on which databases can be hosted.
       class Instance
         include Google::Apis::Core::Hashable
@@ -1511,6 +1672,13 @@ module Google
         # @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`.
+        # Corresponds to the JSON property `processingUnits`
+        # @return [Fixnum]
+        attr_accessor :processing_units
+      
         # Output only. The current instance state. For CreateInstance, the state must be
         # either omitted or set to `CREATING`. For UpdateInstance, the state must be
         # either omitted or set to `READY`.
@@ -1530,6 +1698,7 @@ module Google
           @labels = args[:labels] if args.key?(:labels)
           @name = args[:name] if args.key?(:name)
           @node_count = args[:node_count] if args.key?(:node_count)
+          @processing_units = args[:processing_units] if args.key?(:processing_units)
           @state = args[:state] if args.key?(:state)
         end
       end
@@ -1642,6 +1811,103 @@ module Google
         end
       end
       
+      # A message representing information for a key range (possibly one key).
+      class KeyRangeInfo
+        include Google::Apis::Core::Hashable
+      
+        # The list of context values for this key range.
+        # Corresponds to the JSON property `contextValues`
+        # @return [Array<Google::Apis::SpannerV1::ContextValue>]
+        attr_accessor :context_values
+      
+        # The index of the end key in indexed_keys.
+        # Corresponds to the JSON property `endKeyIndex`
+        # @return [Fixnum]
+        attr_accessor :end_key_index
+      
+        # A message representing a user-facing string whose value may need to be
+        # translated before being displayed.
+        # Corresponds to the JSON property `info`
+        # @return [Google::Apis::SpannerV1::LocalizedString]
+        attr_accessor :info
+      
+        # The number of keys this range covers.
+        # Corresponds to the JSON property `keysCount`
+        # @return [Fixnum]
+        attr_accessor :keys_count
+      
+        # A message representing a user-facing string whose value may need to be
+        # translated before being displayed.
+        # Corresponds to the JSON property `metric`
+        # @return [Google::Apis::SpannerV1::LocalizedString]
+        attr_accessor :metric
+      
+        # The index of the start key in indexed_keys.
+        # Corresponds to the JSON property `startKeyIndex`
+        # @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`
+        # @return [Google::Apis::SpannerV1::LocalizedString]
+        attr_accessor :unit
+      
+        # The value of the metric.
+        # Corresponds to the JSON property `value`
+        # @return [Float]
+        attr_accessor :value
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @context_values = args[:context_values] if args.key?(:context_values)
+          @end_key_index = args[:end_key_index] if args.key?(:end_key_index)
+          @info = args[:info] if args.key?(:info)
+          @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
+      end
+      
+      # A message representing a list of specific information for multiple key ranges.
+      class KeyRangeInfos
+        include Google::Apis::Core::Hashable
+      
+        # The list individual KeyRangeInfos.
+        # Corresponds to the JSON property `infos`
+        # @return [Array<Google::Apis::SpannerV1::KeyRangeInfo>]
+        attr_accessor :infos
+      
+        # The total size of the list of all KeyRangeInfos. This may be larger than the
+        # number of repeated messages above. If that is the case, this number may be
+        # used to determine how many are not being shown.
+        # Corresponds to the JSON property `totalSize`
+        # @return [Fixnum]
+        attr_accessor :total_size
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @infos = args[:infos] if args.key?(:infos)
+          @total_size = args[:total_size] if args.key?(:total_size)
+        end
+      end
+      
       # `KeySet` defines a collection of Cloud Spanner keys and/or key ranges. All the
       # keys are expected to be in the same table or index. The keys need not be
       # sorted in any particular way. If the same key is specified multiple times in
@@ -1879,6 +2145,32 @@ module Google
         end
       end
       
+      # Response method from the ListScans method.
+      class ListScansResponse
+        include Google::Apis::Core::Hashable
+      
+        # Token to retrieve the next page of results, or empty if there are no more
+        # results in the list.
+        # Corresponds to the JSON property `nextPageToken`
+        # @return [String]
+        attr_accessor :next_page_token
+      
+        # Available scans based on the list query parameters.
+        # Corresponds to the JSON property `scans`
+        # @return [Array<Google::Apis::SpannerV1::Scan>]
+        attr_accessor :scans
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @next_page_token = args[:next_page_token] if args.key?(:next_page_token)
+          @scans = args[:scans] if args.key?(:scans)
+        end
+      end
+      
       # The response for ListSessions.
       class ListSessionsResponse
         include Google::Apis::Core::Hashable
@@ -1905,6 +2197,179 @@ module Google
         end
       end
       
+      # A message representing a user-facing string whose value may need to be
+      # translated before being displayed.
+      class LocalizedString
+        include Google::Apis::Core::Hashable
+      
+        # A map of arguments used when creating the localized message. Keys represent
+        # parameter names which may be used by the localized version when substituting
+        # dynamic values.
+        # Corresponds to the JSON property `args`
+        # @return [Hash<String,String>]
+        attr_accessor :args
+      
+        # The canonical English version of this message. If no token is provided or the
+        # front-end has no message associated with the token, this text will be
+        # displayed as-is.
+        # Corresponds to the JSON property `message`
+        # @return [String]
+        attr_accessor :message
+      
+        # The token identifying the message, e.g. 'METRIC_READ_CPU'. This should be
+        # unique within the service.
+        # Corresponds to the JSON property `token`
+        # @return [String]
+        attr_accessor :token
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @args = args[:args] if args.key?(:args)
+          @message = args[:message] if args.key?(:message)
+          @token = args[:token] if args.key?(:token)
+        end
+      end
+      
+      # A message representing the actual monitoring data, values for each key bucket
+      # over time, of a metric.
+      class Metric
+        include Google::Apis::Core::Hashable
+      
+        # The aggregation function used to aggregate each key bucket
+        # Corresponds to the JSON property `aggregation`
+        # @return [String]
+        attr_accessor :aggregation
+      
+        # A message representing a user-facing string whose value may need to be
+        # translated before being displayed.
+        # Corresponds to the JSON property `category`
+        # @return [Google::Apis::SpannerV1::LocalizedString]
+        attr_accessor :category
+      
+        # A message representing a derived metric.
+        # Corresponds to the JSON property `derived`
+        # @return [Google::Apis::SpannerV1::DerivedMetric]
+        attr_accessor :derived
+      
+        # A message representing a user-facing string whose value may need to be
+        # translated before being displayed.
+        # Corresponds to the JSON property `displayLabel`
+        # @return [Google::Apis::SpannerV1::LocalizedString]
+        attr_accessor :display_label
+      
+        # Whether the metric has any non-zero data.
+        # Corresponds to the JSON property `hasNonzeroData`
+        # @return [Boolean]
+        attr_accessor :has_nonzero_data
+        alias_method :has_nonzero_data?, :has_nonzero_data
+      
+        # The value that is considered hot for the metric. On a per metric basis hotness
+        # signals high utilization and something that might potentially be a cause for
+        # concern by the end user. hot_value is used to calibrate and scale visual color
+        # scales.
+        # Corresponds to the JSON property `hotValue`
+        # @return [Float]
+        attr_accessor :hot_value
+      
+        # The (sparse) mapping from time index to an IndexedHotKey message, representing
+        # those time intervals for which there are hot keys.
+        # Corresponds to the JSON property `indexedHotKeys`
+        # @return [Hash<String,Google::Apis::SpannerV1::IndexedHotKey>]
+        attr_accessor :indexed_hot_keys
+      
+        # The (sparse) mapping from time interval index to an IndexedKeyRangeInfos
+        # message, representing those time intervals for which there are informational
+        # messages concerning key ranges.
+        # Corresponds to the JSON property `indexedKeyRangeInfos`
+        # @return [Hash<String,Google::Apis::SpannerV1::IndexedKeyRangeInfos>]
+        attr_accessor :indexed_key_range_infos
+      
+        # A message representing a user-facing string whose value may need to be
+        # translated before being displayed.
+        # Corresponds to the JSON property `info`
+        # @return [Google::Apis::SpannerV1::LocalizedString]
+        attr_accessor :info
+      
+        # A message representing a matrix of floats.
+        # Corresponds to the JSON property `matrix`
+        # @return [Google::Apis::SpannerV1::MetricMatrix]
+        attr_accessor :matrix
+      
+        # A message representing a user-facing string whose value may need to be
+        # translated before being displayed.
+        # Corresponds to the JSON property `unit`
+        # @return [Google::Apis::SpannerV1::LocalizedString]
+        attr_accessor :unit
+      
+        # Whether the metric is visible to the end user.
+        # Corresponds to the JSON property `visible`
+        # @return [Boolean]
+        attr_accessor :visible
+        alias_method :visible?, :visible
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @aggregation = args[:aggregation] if args.key?(:aggregation)
+          @category = args[:category] if args.key?(:category)
+          @derived = args[:derived] if args.key?(:derived)
+          @display_label = args[:display_label] if args.key?(:display_label)
+          @has_nonzero_data = args[:has_nonzero_data] if args.key?(:has_nonzero_data)
+          @hot_value = args[:hot_value] if args.key?(:hot_value)
+          @indexed_hot_keys = args[:indexed_hot_keys] if args.key?(:indexed_hot_keys)
+          @indexed_key_range_infos = args[:indexed_key_range_infos] if args.key?(:indexed_key_range_infos)
+          @info = args[:info] if args.key?(:info)
+          @matrix = args[:matrix] if args.key?(:matrix)
+          @unit = args[:unit] if args.key?(:unit)
+          @visible = args[:visible] if args.key?(:visible)
+        end
+      end
+      
+      # A message representing a matrix of floats.
+      class MetricMatrix
+        include Google::Apis::Core::Hashable
+      
+        # The rows of the matrix.
+        # Corresponds to the JSON property `rows`
+        # @return [Array<Google::Apis::SpannerV1::MetricMatrixRow>]
+        attr_accessor :rows
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @rows = args[:rows] if args.key?(:rows)
+        end
+      end
+      
+      # A message representing a row of a matrix of floats.
+      class MetricMatrixRow
+        include Google::Apis::Core::Hashable
+      
+        # The columns of the row.
+        # Corresponds to the JSON property `cols`
+        # @return [Array<Float>]
+        attr_accessor :cols
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @cols = args[:cols] if args.key?(:cols)
+        end
+      end
+      
       # A modification to one or more Cloud Spanner rows. Mutations can be applied to
       # a Cloud Spanner database by sending them in a Commit call.
       class Mutation
@@ -2513,6 +2978,55 @@ module Google
         end
       end
       
+      # A message representing a key prefix node in the key prefix hierarchy. for eg.
+      # Bigtable keyspaces are lexicographically ordered mappings of keys to values.
+      # Keys often have a shared prefix structure where users use the keys to organize
+      # data. Eg ///employee In this case Keysight will possibly use one node for a
+      # company and reuse it for all employees that fall under the company. Doing so
+      # improves legibility in the UI.
+      class PrefixNode
+        include Google::Apis::Core::Hashable
+      
+        # Whether this corresponds to a data_source name.
+        # Corresponds to the JSON property `dataSourceNode`
+        # @return [Boolean]
+        attr_accessor :data_source_node
+        alias_method :data_source_node?, :data_source_node
+      
+        # The depth in the prefix hierarchy.
+        # Corresponds to the JSON property `depth`
+        # @return [Fixnum]
+        attr_accessor :depth
+      
+        # The index of the end key bucket of the range that this node spans.
+        # Corresponds to the JSON property `endIndex`
+        # @return [Fixnum]
+        attr_accessor :end_index
+      
+        # The index of the start key bucket of the range that this node spans.
+        # Corresponds to the JSON property `startIndex`
+        # @return [Fixnum]
+        attr_accessor :start_index
+      
+        # The string represented by the prefix node.
+        # Corresponds to the JSON property `word`
+        # @return [String]
+        attr_accessor :word
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @data_source_node = args[:data_source_node] if args.key?(:data_source_node)
+          @depth = args[:depth] if args.key?(:depth)
+          @end_index = args[:end_index] if args.key?(:end_index)
+          @start_index = args[:start_index] if args.key?(:start_index)
+          @word = args[:word] if args.key?(:word)
+        end
+      end
+      
       # Query optimizer configuration.
       class QueryOptions
         include Google::Apis::Core::Hashable
@@ -3104,6 +3618,87 @@ module Google
         end
       end
       
+      # Scan is a structure which describes Cloud Key Visualizer scan information.
+      class Scan
+        include Google::Apis::Core::Hashable
+      
+        # Additional information provided by the implementer.
+        # Corresponds to the JSON property `details`
+        # @return [Hash<String,Object>]
+        attr_accessor :details
+      
+        # The upper bound for when the scan is defined.
+        # Corresponds to the JSON property `endTime`
+        # @return [String]
+        attr_accessor :end_time
+      
+        # The unique name of the scan, specific to the Database service implementing
+        # this interface.
+        # Corresponds to the JSON property `name`
+        # @return [String]
+        attr_accessor :name
+      
+        # ScanData contains Cloud Key Visualizer scan data used by the caller to
+        # construct a visualization.
+        # Corresponds to the JSON property `scanData`
+        # @return [Google::Apis::SpannerV1::ScanData]
+        attr_accessor :scan_data
+      
+        # A range of time (inclusive) for when the scan is defined. The lower bound for
+        # when the scan is defined.
+        # Corresponds to the JSON property `startTime`
+        # @return [String]
+        attr_accessor :start_time
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @details = args[:details] if args.key?(:details)
+          @end_time = args[:end_time] if args.key?(:end_time)
+          @name = args[:name] if args.key?(:name)
+          @scan_data = args[:scan_data] if args.key?(:scan_data)
+          @start_time = args[:start_time] if args.key?(:start_time)
+        end
+      end
+      
+      # ScanData contains Cloud Key Visualizer scan data used by the caller to
+      # construct a visualization.
+      class ScanData
+        include Google::Apis::Core::Hashable
+      
+        # Cloud Key Visualizer scan data. The range of time this information covers is
+        # captured via the above time range fields. Note, this field is not available to
+        # the ListScans method.
+        # Corresponds to the JSON property `data`
+        # @return [Google::Apis::SpannerV1::VisualizationData]
+        attr_accessor :data
+      
+        # The upper bound for when the contained data is defined.
+        # Corresponds to the JSON property `endTime`
+        # @return [String]
+        attr_accessor :end_time
+      
+        # A range of time (inclusive) for when the contained data is defined. The lower
+        # bound for when the contained data is defined.
+        # Corresponds to the JSON property `startTime`
+        # @return [String]
+        attr_accessor :start_time
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @data = args[:data] if args.key?(:data)
+          @end_time = args[:end_time] if args.key?(:end_time)
+          @start_time = args[:start_time] if args.key?(:start_time)
+        end
+      end
+      
       # A session in the Cloud Spanner API.
       class Session
         include Google::Apis::Core::Hashable
@@ -3394,12 +3989,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
@@ -3417,8 +4012,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
@@ -3427,7 +4022,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
@@ -3435,24 +4030,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
@@ -3470,15 +4065,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
@@ -3490,8 +4085,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
@@ -3508,15 +4103,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
@@ -3589,12 +4184,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
@@ -3612,8 +4207,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
@@ -3622,7 +4217,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
@@ -3630,24 +4225,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
@@ -3665,15 +4260,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
@@ -3685,8 +4280,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
@@ -3703,15 +4298,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
@@ -3758,12 +4353,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
@@ -3781,8 +4376,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
@@ -3791,7 +4386,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
@@ -3799,24 +4394,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
@@ -3834,15 +4429,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
@@ -3854,8 +4449,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
@@ -3872,15 +4467,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
@@ -4130,6 +4725,84 @@ module Google
         end
       end
       
+      # 
+      class VisualizationData
+        include Google::Apis::Core::Hashable
+      
+        # The token signifying the end of a data_source.
+        # Corresponds to the JSON property `dataSourceEndToken`
+        # @return [String]
+        attr_accessor :data_source_end_token
+      
+        # The token delimiting a datasource name from the rest of a key in a data_source.
+        # Corresponds to the JSON property `dataSourceSeparatorToken`
+        # @return [String]
+        attr_accessor :data_source_separator_token
+      
+        # The list of messages (info, alerts, ...)
+        # Corresponds to the JSON property `diagnosticMessages`
+        # @return [Array<Google::Apis::SpannerV1::DiagnosticMessage>]
+        attr_accessor :diagnostic_messages
+      
+        # We discretize the entire keyspace into buckets. Assuming each bucket has an
+        # inclusive keyrange and covers keys from k(i) ... k(n). In this case k(n) would
+        # be an end key for a given range. end_key_string is the collection of all such
+        # end keys
+        # Corresponds to the JSON property `endKeyStrings`
+        # @return [Array<String>]
+        attr_accessor :end_key_strings
+      
+        # Whether this scan contains PII.
+        # Corresponds to the JSON property `hasPii`
+        # @return [Boolean]
+        attr_accessor :has_pii
+        alias_method :has_pii?, :has_pii
+      
+        # Keys of key ranges that contribute significantly to a given metric Can be
+        # thought of as heavy hitters.
+        # Corresponds to the JSON property `indexedKeys`
+        # @return [Array<String>]
+        attr_accessor :indexed_keys
+      
+        # The token delimiting the key prefixes.
+        # Corresponds to the JSON property `keySeparator`
+        # @return [String]
+        attr_accessor :key_separator
+      
+        # The unit for the key: e.g. 'key' or 'chunk'.
+        # Corresponds to the JSON property `keyUnit`
+        # @return [String]
+        attr_accessor :key_unit
+      
+        # The list of data objects for each metric.
+        # Corresponds to the JSON property `metrics`
+        # @return [Array<Google::Apis::SpannerV1::Metric>]
+        attr_accessor :metrics
+      
+        # The list of extracted key prefix nodes used in the key prefix hierarchy.
+        # Corresponds to the JSON property `prefixNodes`
+        # @return [Array<Google::Apis::SpannerV1::PrefixNode>]
+        attr_accessor :prefix_nodes
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @data_source_end_token = args[:data_source_end_token] if args.key?(:data_source_end_token)
+          @data_source_separator_token = args[:data_source_separator_token] if args.key?(:data_source_separator_token)
+          @diagnostic_messages = args[:diagnostic_messages] if args.key?(:diagnostic_messages)
+          @end_key_strings = args[:end_key_strings] if args.key?(:end_key_strings)
+          @has_pii = args[:has_pii] if args.key?(:has_pii)
+          @indexed_keys = args[:indexed_keys] if args.key?(:indexed_keys)
+          @key_separator = args[:key_separator] if args.key?(:key_separator)
+          @key_unit = args[:key_unit] if args.key?(:key_unit)
+          @metrics = args[:metrics] if args.key?(:metrics)
+          @prefix_nodes = args[:prefix_nodes] if args.key?(:prefix_nodes)
+        end
+      end
+      
       # Arguments to insert, update, insert_or_update, and replace operations.
       class Write
         include Google::Apis::Core::Hashable