google-cloud-spanner-v1 0.8.1 → 0.9.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 93f09468179faf9a4c502c5a276716deea004350d4e929f949f6569c45461cea
-  data.tar.gz: 4b20dc3ee2b9271a1751424d3d7263e48805a9a83c89474c997375e3e7795bf7
+  metadata.gz: 107c7db85e616d72c82ff72eb07655d00ae1926f99c8002bfaf81eff4fb6caba
+  data.tar.gz: 42995b967b44b04c1b8effd91d090d05627cfa1df9c5ea01b1f6f9570cbefb07
 SHA512:
-  metadata.gz: ddb5ead04c9bc1692f10899ed8dae40443a2121851b8be4d3538e67887556168920e9e7d9d8ccd19668acd9e670cfdf30ed37e711b03748207f902cb5cbf0b69
-  data.tar.gz: 3bea006bc63c759c3c076cfcc1c935140115dcc64111e9c84e147381094c146064385ad858b91597ff024c3f48daf20053b513f81f4a34f069afe3f40e208b34
+  metadata.gz: a0f052167fd7a336f1566d4d9aefc9ff84e2e1b745b1c6999deae77d62900e82538943f7a25899390ddf6771ac08260ff0d1947cd10a8089eeabf73050156378
+  data.tar.gz: f0a3fed751f4d1af95465f51d4f94a6d423544fd28a6183b6ccfffe3ac423f2146f981b894a6600c2c8c214efa25f98828028cfa071cead7fa940bf77088fc83

data/README.md

@@ -69,6 +69,11 @@ module GRPC
 end
 ```
 
+
+## Google Cloud Samples
+
+To browse ready to use code samples check [Google Cloud Samples](https://cloud.google.com/docs/samples).
+
 ## Supported Ruby Versions
 
 This library is supported on Ruby 2.5+.

data/lib/google/cloud/spanner/v1/version.rb

@@ -21,7 +21,7 @@ module Google
   module Cloud
     module Spanner
       module V1
-        VERSION = "0.8.1"
+        VERSION = "0.9.0"
       end
     end
   end

data/lib/google/spanner/v1/commit_response_pb.rb

@@ -1,9 +1,10 @@
 # Generated by the protocol buffer compiler.  DO NOT EDIT!
 # source: google/spanner/v1/commit_response.proto
 
-require 'google/protobuf/timestamp_pb'
 require 'google/protobuf'
 
+require 'google/protobuf/timestamp_pb'
+
 Google::Protobuf::DescriptorPool.generated_pool.build do
   add_file("google/spanner/v1/commit_response.proto", :syntax => :proto3) do
     add_message "google.spanner.v1.CommitResponse" do

data/lib/google/spanner/v1/keys_pb.rb

@@ -1,9 +1,10 @@
 # Generated by the protocol buffer compiler.  DO NOT EDIT!
 # source: google/spanner/v1/keys.proto
 
-require 'google/protobuf/struct_pb'
 require 'google/protobuf'
 
+require 'google/protobuf/struct_pb'
+
 Google::Protobuf::DescriptorPool.generated_pool.build do
   add_file("google/spanner/v1/keys.proto", :syntax => :proto3) do
     add_message "google.spanner.v1.KeyRange" do

data/lib/google/spanner/v1/mutation_pb.rb

@@ -1,10 +1,11 @@
 # Generated by the protocol buffer compiler.  DO NOT EDIT!
 # source: google/spanner/v1/mutation.proto
 
+require 'google/protobuf'
+
 require 'google/api/field_behavior_pb'
 require 'google/protobuf/struct_pb'
 require 'google/spanner/v1/keys_pb'
-require 'google/protobuf'
 
 Google::Protobuf::DescriptorPool.generated_pool.build do
   add_file("google/spanner/v1/mutation.proto", :syntax => :proto3) do

data/lib/google/spanner/v1/query_plan_pb.rb

@@ -1,9 +1,10 @@
 # Generated by the protocol buffer compiler.  DO NOT EDIT!
 # source: google/spanner/v1/query_plan.proto
 
-require 'google/protobuf/struct_pb'
 require 'google/protobuf'
 
+require 'google/protobuf/struct_pb'
+
 Google::Protobuf::DescriptorPool.generated_pool.build do
   add_file("google/spanner/v1/query_plan.proto", :syntax => :proto3) do
     add_message "google.spanner.v1.PlanNode" do

data/lib/google/spanner/v1/result_set_pb.rb

@@ -1,12 +1,12 @@
 # Generated by the protocol buffer compiler.  DO NOT EDIT!
 # source: google/spanner/v1/result_set.proto
 
+require 'google/protobuf'
+
 require 'google/protobuf/struct_pb'
-require 'google/spanner/v1/commit_response_pb'
 require 'google/spanner/v1/query_plan_pb'
 require 'google/spanner/v1/transaction_pb'
 require 'google/spanner/v1/type_pb'
-require 'google/protobuf'
 
 Google::Protobuf::DescriptorPool.generated_pool.build do
   add_file("google/spanner/v1/result_set.proto", :syntax => :proto3) do

data/lib/google/spanner/v1/spanner_pb.rb

@@ -1,6 +1,8 @@
 # Generated by the protocol buffer compiler.  DO NOT EDIT!
 # source: google/spanner/v1/spanner.proto
 
+require 'google/protobuf'
+
 require 'google/api/annotations_pb'
 require 'google/api/client_pb'
 require 'google/api/field_behavior_pb'
@@ -15,7 +17,6 @@ require 'google/spanner/v1/mutation_pb'
 require 'google/spanner/v1/result_set_pb'
 require 'google/spanner/v1/transaction_pb'
 require 'google/spanner/v1/type_pb'
-require 'google/protobuf'
 
 Google::Protobuf::DescriptorPool.generated_pool.build do
   add_file("google/spanner/v1/spanner.proto", :syntax => :proto3) do
@@ -36,6 +37,7 @@ Google::Protobuf::DescriptorPool.generated_pool.build do
       map :labels, :string, :string, 2
       optional :create_time, :message, 3, "google.protobuf.Timestamp"
       optional :approximate_last_use_time, :message, 4, "google.protobuf.Timestamp"
+      optional :creator_role, :string, 5
     end
     add_message "google.spanner.v1.GetSessionRequest" do
       optional :name, :string, 1

data/lib/google/spanner/v1/transaction_pb.rb

@@ -1,9 +1,10 @@
 # Generated by the protocol buffer compiler.  DO NOT EDIT!
 # source: google/spanner/v1/transaction.proto
 
+require 'google/protobuf'
+
 require 'google/protobuf/duration_pb'
 require 'google/protobuf/timestamp_pb'
-require 'google/protobuf'
 
 Google::Protobuf::DescriptorPool.generated_pool.build do
   add_file("google/spanner/v1/transaction.proto", :syntax => :proto3) do

data/lib/google/spanner/v1/type_pb.rb

@@ -1,9 +1,10 @@
 # Generated by the protocol buffer compiler.  DO NOT EDIT!
 # source: google/spanner/v1/type.proto
 
-require 'google/api/field_behavior_pb'
 require 'google/protobuf'
 
+require 'google/api/field_behavior_pb'
+
 Google::Protobuf::DescriptorPool.generated_pool.build do
   add_file("google/spanner/v1/type.proto", :syntax => :proto3) do
     add_message "google.spanner.v1.Type" do

data/proto_docs/google/protobuf/any.rb

@@ -44,7 +44,7 @@ module Google
     #       foo = any.unpack(Foo.class);
     #     }
     #
-    #  Example 3: Pack and unpack a message in Python.
+    # Example 3: Pack and unpack a message in Python.
     #
     #     foo = Foo(...)
     #     any = Any()
@@ -54,7 +54,7 @@ module Google
     #       any.Unpack(foo)
     #       ...
     #
-    #  Example 4: Pack and unpack a message in Go
+    # Example 4: Pack and unpack a message in Go
     #
     #      foo := &pb.Foo{...}
     #      any, err := anypb.New(foo)
@@ -75,7 +75,7 @@ module Google
     #
     #
     # JSON
-    # ====
+    #
     # The JSON representation of an `Any` value uses the regular
     # representation of the deserialized, embedded message, with an
     # additional field `@type` which contains the type URL. Example:

data/proto_docs/google/protobuf/struct.rb

@@ -46,8 +46,8 @@ module Google
 
     # `Value` represents a dynamically typed value which can be either
     # null, a number, a string, a boolean, a recursive struct value, or a
-    # list of values. A producer of value is expected to set one of that
-    # variants, absence of any variant indicates an error.
+    # list of values. A producer of value is expected to set one of these
+    # variants. Absence of any variant indicates an error.
     #
     # The JSON representation for `Value` is JSON value.
     # @!attribute [rw] null_value

data/proto_docs/google/spanner/v1/spanner.rb

@@ -83,6 +83,9 @@ module Google
         #   @return [::Google::Protobuf::Timestamp]
         #     Output only. The approximate timestamp when the session is last used. It is
         #     typically earlier than the actual last use time.
+        # @!attribute [rw] creator_role
+        #   @return [::String]
+        #     The database role which created this session.
         class Session
           include ::Google::Protobuf::MessageExts
           extend ::Google::Protobuf::MessageExts::ClassMethods

data/proto_docs/google/spanner/v1/transaction.rb

@@ -29,7 +29,8 @@ module Google
         # 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:
+        # Transaction modes:
+        #
         # Cloud Spanner supports three transaction modes:
         #
         #   1. Locking read-write. This type of transaction is the only way
@@ -38,11 +39,18 @@ module Google
         #      Locking read-write transactions may abort, requiring the
         #      application to retry.
         #
-        #   2. Snapshot read-only. This transaction type provides guaranteed
-        #      consistency across several reads, but does not allow
-        #      writes. Snapshot read-only transactions can be configured to
-        #      read at timestamps in the past. Snapshot read-only
-        #      transactions do not need to be committed.
+        #   2. Snapshot read-only. Snapshot read-only transactions provide guaranteed
+        #      consistency across several reads, but do not allow
+        #      writes. Snapshot read-only transactions can be configured to read at
+        #      timestamps in the past, or configured to perform a strong read
+        #      (where Spanner will select a timestamp such that the read is
+        #      guaranteed to see the effects of all transactions that have committed
+        #      before the start of the read). Snapshot read-only transactions do not
+        #      need to be committed.
+        #
+        #      Queries on change streams must be performed with the snapshot read-only
+        #      transaction mode, specifying a strong read. Please see
+        #      {::Google::Cloud::Spanner::V1::TransactionOptions::ReadOnly#strong TransactionOptions.ReadOnly.strong} for more details.
         #
         #   3. Partitioned DML. This type of transaction is used to execute
         #      a single Partitioned DML statement. Partitioned DML partitions
@@ -57,11 +65,12 @@ module Google
         # not conflict with read-write transactions. As a consequence of not
         # taking locks, they also do not abort, so retry loops are not needed.
         #
-        # Transactions may only read/write data in a single database. They
-        # may, however, read/write data in different tables within that
+        # 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 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.
@@ -72,7 +81,7 @@ module Google
         # active as long as the transaction continues to do reads, and the
         # transaction has not been terminated by
         # {::Google::Cloud::Spanner::V1::Spanner::Client#commit Commit} or
-        # {::Google::Cloud::Spanner::V1::Spanner::Client#rollback Rollback}.  Long periods of
+        # {::Google::Cloud::Spanner::V1::Spanner::Client#rollback Rollback}. Long periods of
         # inactivity at the client may cause Cloud Spanner to release a
         # transaction's locks and abort it.
         #
@@ -84,6 +93,7 @@ module Google
         # 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
@@ -95,7 +105,8 @@ module Google
         # use Cloud Spanner locks for any sort of mutual exclusion other than
         # between Cloud Spanner transactions themselves.
         #
-        # Retrying Aborted Transactions:
+        # 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
@@ -110,7 +121,8 @@ module Google
         # instead, it is better to limit the total amount of time spent
         # retrying.
         #
-        # Idle Transactions:
+        # 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
@@ -121,7 +133,8 @@ module Google
         # SQL query in the transaction (for example, `SELECT 1`) prevents the
         # transaction from becoming idle.
         #
-        # Snapshot Read-Only Transactions:
+        # 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.
@@ -153,13 +166,12 @@ module Google
         #
         # If the Cloud Spanner database to be read is geographically distributed,
         # stale read-only transactions can execute more quickly than strong
-        # or read-write transaction, because they are able to execute far
+        # or read-write transactions, because they are able to execute far
         # from the leader replica.
         #
         # Each type of timestamp bound is discussed in detail below.
         #
-        # Strong:
-        # Strong reads are guaranteed to see the effects of all transactions
+        # 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
@@ -171,9 +183,13 @@ module Google
         # reads should be executed within a transaction or at an exact read
         # timestamp.
         #
+        # Queries on change streams (see below for more details) must also specify
+        # the strong read timestamp bound.
+        #
         # See {::Google::Cloud::Spanner::V1::TransactionOptions::ReadOnly#strong TransactionOptions.ReadOnly.strong}.
         #
-        # Exact Staleness:
+        # 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
@@ -194,7 +210,8 @@ module Google
         # See {::Google::Cloud::Spanner::V1::TransactionOptions::ReadOnly#read_timestamp TransactionOptions.ReadOnly.read_timestamp} and
         # {::Google::Cloud::Spanner::V1::TransactionOptions::ReadOnly#exact_staleness TransactionOptions.ReadOnly.exact_staleness}.
         #
-        # Bounded 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
@@ -223,7 +240,8 @@ module Google
         # See {::Google::Cloud::Spanner::V1::TransactionOptions::ReadOnly#max_staleness TransactionOptions.ReadOnly.max_staleness} and
         # {::Google::Cloud::Spanner::V1::TransactionOptions::ReadOnly#min_read_timestamp TransactionOptions.ReadOnly.min_read_timestamp}.
         #
-        # Old Read Timestamps and Garbage Collection:
+        # 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
@@ -233,7 +251,41 @@ module Google
         # timestamp become too old while executing. Reads and SQL queries with
         # too-old read timestamps fail with the error `FAILED_PRECONDITION`.
         #
-        # Partitioned DML Transactions:
+        # You can configure and extend the `VERSION_RETENTION_PERIOD` of a
+        # database up to a period as long as one week, which allows Cloud Spanner
+        # to perform reads up to one week in the past.
+        #
+        # Querying change Streams:
+        #
+        # A Change Stream is a schema object that can be configured to watch data
+        # changes on the entire database, a set of tables, or a set of columns
+        # in a database.
+        #
+        # When a change stream is created, Spanner automatically defines a
+        # corresponding SQL Table-Valued Function (TVF) that can be used to query
+        # the change records in the associated change stream using the
+        # ExecuteStreamingSql API. The name of the TVF for a change stream is
+        # generated from the name of the change stream: READ_<change_stream_name>.
+        #
+        # All queries on change stream TVFs must be executed using the
+        # ExecuteStreamingSql API with a single-use read-only transaction with a
+        # strong read-only timestamp_bound. The change stream TVF allows users to
+        # specify the start_timestamp and end_timestamp for the time range of
+        # interest. All change records within the retention period is accessible
+        # using the strong read-only timestamp_bound. All other TransactionOptions
+        # are invalid for change stream queries.
+        #
+        # In addition, if TransactionOptions.read_only.return_read_timestamp is set
+        # to true, a special value of 2^63 - 2 will be returned in the
+        # {::Google::Cloud::Spanner::V1::Transaction Transaction} message that describes the
+        # transaction, instead of a valid read timestamp. This special value should be
+        # discarded and not used for any subsequent queries.
+        #
+        # Please see https://cloud.google.com/spanner/docs/change-streams
+        # for more details on how to query the change stream TVFs.
+        #
+        # Partitioned DML transactions:
+        #
         # Partitioned DML transactions are used to execute DML statements with a
         # different execution strategy that provides different, and often better,
         # scalability properties for large, table-wide operations than DML in a

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: google-cloud-spanner-v1
 version: !ruby/object:Gem::Version
-  version: 0.8.1
+  version: 0.9.0
 platform: ruby
 authors:
 - Google LLC
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2022-03-22 00:00:00.000000000 Z
+date: 2022-06-09 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: gapic-common
@@ -221,7 +221,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.3.5
+rubygems_version: 3.3.14
 signing_key: 
 specification_version: 4
 summary: API Client library for the Cloud Spanner V1 API