google-cloud-spanner-v1 0.8.0 → 0.10.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +10 -5
- data/lib/google/cloud/spanner/v1/spanner/client.rb +1 -1
- data/lib/google/cloud/spanner/v1/version.rb +1 -1
- data/lib/google/cloud/spanner/v1.rb +2 -0
- data/lib/google/spanner/v1/commit_response_pb.rb +2 -3
- data/lib/google/spanner/v1/keys_pb.rb +2 -2
- data/lib/google/spanner/v1/mutation_pb.rb +3 -2
- data/lib/google/spanner/v1/query_plan_pb.rb +2 -2
- data/lib/google/spanner/v1/result_set_pb.rb +2 -3
- data/lib/google/spanner/v1/spanner_pb.rb +3 -1
- data/lib/google/spanner/v1/transaction_pb.rb +2 -2
- data/lib/google/spanner/v1/type_pb.rb +2 -2
- data/proto_docs/google/protobuf/any.rb +3 -3
- data/proto_docs/google/protobuf/struct.rb +2 -2
- data/proto_docs/google/spanner/v1/spanner.rb +4 -1
- data/proto_docs/google/spanner/v1/transaction.rb +72 -20
- metadata +12 -12
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 91e76cd39a90f6e719e44cd63c03643eb529b9c25f1a76b4aef3c98d2865cd77
|
4
|
+
data.tar.gz: 2ed992519fd3f919483035d21e49ff7aa156d6948809f63ffd1ecf760e9d7363
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 1354e2699e8c0a8fa4ec909e2c25a35048e2f1a6a958a74c45cadf2553eb68e5c9020285443e1b136c829e4acad70608a2d274c65d1962411e3284f7c0ee7a73
|
7
|
+
data.tar.gz: 463a1418ff65f61f8eb4d7ed4c3501015627cc60b46d98adef361c170110e1cd784434e43923949d9a66137f30c8f785f4e612fb7276c7b0a0359f6f8b0a8eea
|
data/README.md
CHANGED
@@ -69,16 +69,21 @@ module GRPC
|
|
69
69
|
end
|
70
70
|
```
|
71
71
|
|
72
|
+
|
73
|
+
## Google Cloud Samples
|
74
|
+
|
75
|
+
To browse ready to use code samples check [Google Cloud Samples](https://cloud.google.com/docs/samples).
|
76
|
+
|
72
77
|
## Supported Ruby Versions
|
73
78
|
|
74
|
-
This library is supported on Ruby 2.
|
79
|
+
This library is supported on Ruby 2.6+.
|
75
80
|
|
76
81
|
Google provides official support for Ruby versions that are actively supported
|
77
82
|
by Ruby Core—that is, Ruby versions that are either in normal maintenance or
|
78
|
-
in security maintenance, and not end of life.
|
79
|
-
|
80
|
-
|
81
|
-
|
83
|
+
in security maintenance, and not end of life. Older versions of Ruby _may_
|
84
|
+
still work, but are unsupported and not recommended. See
|
85
|
+
https://www.ruby-lang.org/en/downloads/branches/ for details about the Ruby
|
86
|
+
support schedule.
|
82
87
|
|
83
88
|
## Which client should I use?
|
84
89
|
|
@@ -255,7 +255,7 @@ module Google
|
|
255
255
|
# @param database [::String]
|
256
256
|
# Required. The database in which the new session is created.
|
257
257
|
# @param session [::Google::Cloud::Spanner::V1::Session, ::Hash]
|
258
|
-
# The session to create.
|
258
|
+
# Required. The session to create.
|
259
259
|
#
|
260
260
|
# @yield [response, operation] Access the result along with the RPC operation
|
261
261
|
# @yieldparam response [::Google::Cloud::Spanner::V1::Session]
|
@@ -1,11 +1,10 @@
|
|
1
1
|
# Generated by the protocol buffer compiler. DO NOT EDIT!
|
2
2
|
# source: google/spanner/v1/commit_response.proto
|
3
3
|
|
4
|
-
require 'google/api/annotations_pb'
|
5
|
-
require 'google/protobuf/duration_pb'
|
6
|
-
require 'google/protobuf/timestamp_pb'
|
7
4
|
require 'google/protobuf'
|
8
5
|
|
6
|
+
require 'google/protobuf/timestamp_pb'
|
7
|
+
|
9
8
|
Google::Protobuf::DescriptorPool.generated_pool.build do
|
10
9
|
add_file("google/spanner/v1/commit_response.proto", :syntax => :proto3) do
|
11
10
|
add_message "google.spanner.v1.CommitResponse" do
|
@@ -1,10 +1,10 @@
|
|
1
1
|
# Generated by the protocol buffer compiler. DO NOT EDIT!
|
2
2
|
# source: google/spanner/v1/keys.proto
|
3
3
|
|
4
|
-
require 'google/api/annotations_pb'
|
5
|
-
require 'google/protobuf/struct_pb'
|
6
4
|
require 'google/protobuf'
|
7
5
|
|
6
|
+
require 'google/protobuf/struct_pb'
|
7
|
+
|
8
8
|
Google::Protobuf::DescriptorPool.generated_pool.build do
|
9
9
|
add_file("google/spanner/v1/keys.proto", :syntax => :proto3) do
|
10
10
|
add_message "google.spanner.v1.KeyRange" do
|
@@ -1,10 +1,11 @@
|
|
1
1
|
# Generated by the protocol buffer compiler. DO NOT EDIT!
|
2
2
|
# source: google/spanner/v1/mutation.proto
|
3
3
|
|
4
|
-
require 'google/
|
4
|
+
require 'google/protobuf'
|
5
|
+
|
6
|
+
require 'google/api/field_behavior_pb'
|
5
7
|
require 'google/protobuf/struct_pb'
|
6
8
|
require 'google/spanner/v1/keys_pb'
|
7
|
-
require 'google/protobuf'
|
8
9
|
|
9
10
|
Google::Protobuf::DescriptorPool.generated_pool.build do
|
10
11
|
add_file("google/spanner/v1/mutation.proto", :syntax => :proto3) do
|
@@ -1,10 +1,10 @@
|
|
1
1
|
# Generated by the protocol buffer compiler. DO NOT EDIT!
|
2
2
|
# source: google/spanner/v1/query_plan.proto
|
3
3
|
|
4
|
-
require 'google/api/annotations_pb'
|
5
|
-
require 'google/protobuf/struct_pb'
|
6
4
|
require 'google/protobuf'
|
7
5
|
|
6
|
+
require 'google/protobuf/struct_pb'
|
7
|
+
|
8
8
|
Google::Protobuf::DescriptorPool.generated_pool.build do
|
9
9
|
add_file("google/spanner/v1/query_plan.proto", :syntax => :proto3) do
|
10
10
|
add_message "google.spanner.v1.PlanNode" do
|
@@ -1,13 +1,12 @@
|
|
1
1
|
# Generated by the protocol buffer compiler. DO NOT EDIT!
|
2
2
|
# source: google/spanner/v1/result_set.proto
|
3
3
|
|
4
|
-
require 'google/
|
4
|
+
require 'google/protobuf'
|
5
|
+
|
5
6
|
require 'google/protobuf/struct_pb'
|
6
|
-
require 'google/spanner/v1/commit_response_pb'
|
7
7
|
require 'google/spanner/v1/query_plan_pb'
|
8
8
|
require 'google/spanner/v1/transaction_pb'
|
9
9
|
require 'google/spanner/v1/type_pb'
|
10
|
-
require 'google/protobuf'
|
11
10
|
|
12
11
|
Google::Protobuf::DescriptorPool.generated_pool.build do
|
13
12
|
add_file("google/spanner/v1/result_set.proto", :syntax => :proto3) do
|
@@ -1,6 +1,8 @@
|
|
1
1
|
# Generated by the protocol buffer compiler. DO NOT EDIT!
|
2
2
|
# source: google/spanner/v1/spanner.proto
|
3
3
|
|
4
|
+
require 'google/protobuf'
|
5
|
+
|
4
6
|
require 'google/api/annotations_pb'
|
5
7
|
require 'google/api/client_pb'
|
6
8
|
require 'google/api/field_behavior_pb'
|
@@ -15,7 +17,6 @@ require 'google/spanner/v1/mutation_pb'
|
|
15
17
|
require 'google/spanner/v1/result_set_pb'
|
16
18
|
require 'google/spanner/v1/transaction_pb'
|
17
19
|
require 'google/spanner/v1/type_pb'
|
18
|
-
require 'google/protobuf'
|
19
20
|
|
20
21
|
Google::Protobuf::DescriptorPool.generated_pool.build do
|
21
22
|
add_file("google/spanner/v1/spanner.proto", :syntax => :proto3) do
|
@@ -36,6 +37,7 @@ Google::Protobuf::DescriptorPool.generated_pool.build do
|
|
36
37
|
map :labels, :string, :string, 2
|
37
38
|
optional :create_time, :message, 3, "google.protobuf.Timestamp"
|
38
39
|
optional :approximate_last_use_time, :message, 4, "google.protobuf.Timestamp"
|
40
|
+
optional :creator_role, :string, 5
|
39
41
|
end
|
40
42
|
add_message "google.spanner.v1.GetSessionRequest" do
|
41
43
|
optional :name, :string, 1
|
@@ -1,10 +1,10 @@
|
|
1
1
|
# Generated by the protocol buffer compiler. DO NOT EDIT!
|
2
2
|
# source: google/spanner/v1/transaction.proto
|
3
3
|
|
4
|
-
require 'google/
|
4
|
+
require 'google/protobuf'
|
5
|
+
|
5
6
|
require 'google/protobuf/duration_pb'
|
6
7
|
require 'google/protobuf/timestamp_pb'
|
7
|
-
require 'google/protobuf'
|
8
8
|
|
9
9
|
Google::Protobuf::DescriptorPool.generated_pool.build do
|
10
10
|
add_file("google/spanner/v1/transaction.proto", :syntax => :proto3) do
|
@@ -1,10 +1,10 @@
|
|
1
1
|
# Generated by the protocol buffer compiler. DO NOT EDIT!
|
2
2
|
# source: google/spanner/v1/type.proto
|
3
3
|
|
4
|
-
require 'google/api/annotations_pb'
|
5
|
-
require 'google/api/field_behavior_pb'
|
6
4
|
require 'google/protobuf'
|
7
5
|
|
6
|
+
require 'google/api/field_behavior_pb'
|
7
|
+
|
8
8
|
Google::Protobuf::DescriptorPool.generated_pool.build do
|
9
9
|
add_file("google/spanner/v1/type.proto", :syntax => :proto3) do
|
10
10
|
add_message "google.spanner.v1.Type" do
|
@@ -44,7 +44,7 @@ module Google
|
|
44
44
|
# foo = any.unpack(Foo.class);
|
45
45
|
# }
|
46
46
|
#
|
47
|
-
#
|
47
|
+
# Example 3: Pack and unpack a message in Python.
|
48
48
|
#
|
49
49
|
# foo = Foo(...)
|
50
50
|
# any = Any()
|
@@ -54,7 +54,7 @@ module Google
|
|
54
54
|
# any.Unpack(foo)
|
55
55
|
# ...
|
56
56
|
#
|
57
|
-
#
|
57
|
+
# Example 4: Pack and unpack a message in Go
|
58
58
|
#
|
59
59
|
# foo := &pb.Foo{...}
|
60
60
|
# any, err := anypb.New(foo)
|
@@ -75,7 +75,7 @@ module Google
|
|
75
75
|
#
|
76
76
|
#
|
77
77
|
# JSON
|
78
|
-
#
|
78
|
+
#
|
79
79
|
# The JSON representation of an `Any` value uses the regular
|
80
80
|
# representation of the deserialized, embedded message, with an
|
81
81
|
# additional field `@type` which contains the type URL. Example:
|
@@ -46,8 +46,8 @@ module Google
|
|
46
46
|
|
47
47
|
# `Value` represents a dynamically typed value which can be either
|
48
48
|
# null, a number, a string, a boolean, a recursive struct value, or a
|
49
|
-
# list of values. A producer of value is expected to set one of
|
50
|
-
# variants
|
49
|
+
# list of values. A producer of value is expected to set one of these
|
50
|
+
# variants. Absence of any variant indicates an error.
|
51
51
|
#
|
52
52
|
# The JSON representation for `Value` is JSON value.
|
53
53
|
# @!attribute [rw] null_value
|
@@ -27,7 +27,7 @@ module Google
|
|
27
27
|
# Required. The database in which the new session is created.
|
28
28
|
# @!attribute [rw] session
|
29
29
|
# @return [::Google::Cloud::Spanner::V1::Session]
|
30
|
-
# The session to create.
|
30
|
+
# Required. The session to create.
|
31
31
|
class CreateSessionRequest
|
32
32
|
include ::Google::Protobuf::MessageExts
|
33
33
|
extend ::Google::Protobuf::MessageExts::ClassMethods
|
@@ -83,6 +83,9 @@ module Google
|
|
83
83
|
# @return [::Google::Protobuf::Timestamp]
|
84
84
|
# Output only. The approximate timestamp when the session is last used. It is
|
85
85
|
# typically earlier than the actual last use time.
|
86
|
+
# @!attribute [rw] creator_role
|
87
|
+
# @return [::String]
|
88
|
+
# The database role which created this session.
|
86
89
|
class Session
|
87
90
|
include ::Google::Protobuf::MessageExts
|
88
91
|
extend ::Google::Protobuf::MessageExts::ClassMethods
|
@@ -29,7 +29,8 @@ module Google
|
|
29
29
|
# completed, the session can immediately be re-used for the next transaction.
|
30
30
|
# It is not necessary to create a new session for each transaction.
|
31
31
|
#
|
32
|
-
# Transaction
|
32
|
+
# Transaction modes:
|
33
|
+
#
|
33
34
|
# Cloud Spanner supports three transaction modes:
|
34
35
|
#
|
35
36
|
# 1. Locking read-write. This type of transaction is the only way
|
@@ -38,11 +39,18 @@ module Google
|
|
38
39
|
# Locking read-write transactions may abort, requiring the
|
39
40
|
# application to retry.
|
40
41
|
#
|
41
|
-
# 2. Snapshot read-only.
|
42
|
-
# consistency across several reads, but
|
43
|
-
# writes. Snapshot read-only transactions can be configured to
|
44
|
-
#
|
45
|
-
#
|
42
|
+
# 2. Snapshot read-only. Snapshot read-only transactions provide guaranteed
|
43
|
+
# consistency across several reads, but do not allow
|
44
|
+
# writes. Snapshot read-only transactions can be configured to read at
|
45
|
+
# timestamps in the past, or configured to perform a strong read
|
46
|
+
# (where Spanner will select a timestamp such that the read is
|
47
|
+
# guaranteed to see the effects of all transactions that have committed
|
48
|
+
# before the start of the read). Snapshot read-only transactions do not
|
49
|
+
# need to be committed.
|
50
|
+
#
|
51
|
+
# Queries on change streams must be performed with the snapshot read-only
|
52
|
+
# transaction mode, specifying a strong read. Please see
|
53
|
+
# {::Google::Cloud::Spanner::V1::TransactionOptions::ReadOnly#strong TransactionOptions.ReadOnly.strong} for more details.
|
46
54
|
#
|
47
55
|
# 3. Partitioned DML. This type of transaction is used to execute
|
48
56
|
# a single Partitioned DML statement. Partitioned DML partitions
|
@@ -57,11 +65,12 @@ module Google
|
|
57
65
|
# not conflict with read-write transactions. As a consequence of not
|
58
66
|
# taking locks, they also do not abort, so retry loops are not needed.
|
59
67
|
#
|
60
|
-
# Transactions may only read
|
61
|
-
# may, however, read
|
68
|
+
# Transactions may only read-write data in a single database. They
|
69
|
+
# may, however, read-write data in different tables within that
|
62
70
|
# database.
|
63
71
|
#
|
64
|
-
# Locking
|
72
|
+
# Locking read-write transactions:
|
73
|
+
#
|
65
74
|
# Locking transactions may be used to atomically read-modify-write
|
66
75
|
# data anywhere in a database. This type of transaction is externally
|
67
76
|
# consistent.
|
@@ -72,7 +81,7 @@ module Google
|
|
72
81
|
# active as long as the transaction continues to do reads, and the
|
73
82
|
# transaction has not been terminated by
|
74
83
|
# {::Google::Cloud::Spanner::V1::Spanner::Client#commit Commit} or
|
75
|
-
# {::Google::Cloud::Spanner::V1::Spanner::Client#rollback Rollback}.
|
84
|
+
# {::Google::Cloud::Spanner::V1::Spanner::Client#rollback Rollback}. Long periods of
|
76
85
|
# inactivity at the client may cause Cloud Spanner to release a
|
77
86
|
# transaction's locks and abort it.
|
78
87
|
#
|
@@ -84,6 +93,7 @@ module Google
|
|
84
93
|
# transaction.
|
85
94
|
#
|
86
95
|
# Semantics:
|
96
|
+
#
|
87
97
|
# Cloud Spanner can commit the transaction if all read locks it acquired
|
88
98
|
# are still valid at commit time, and it is able to acquire write
|
89
99
|
# locks for all writes. Cloud Spanner can abort the transaction for any
|
@@ -95,7 +105,8 @@ module Google
|
|
95
105
|
# use Cloud Spanner locks for any sort of mutual exclusion other than
|
96
106
|
# between Cloud Spanner transactions themselves.
|
97
107
|
#
|
98
|
-
# Retrying
|
108
|
+
# Retrying aborted transactions:
|
109
|
+
#
|
99
110
|
# When a transaction aborts, the application can choose to retry the
|
100
111
|
# whole transaction again. To maximize the chances of successfully
|
101
112
|
# committing the retry, the client should execute the retry in the
|
@@ -110,7 +121,8 @@ module Google
|
|
110
121
|
# instead, it is better to limit the total amount of time spent
|
111
122
|
# retrying.
|
112
123
|
#
|
113
|
-
# Idle
|
124
|
+
# Idle transactions:
|
125
|
+
#
|
114
126
|
# A transaction is considered idle if it has no outstanding reads or
|
115
127
|
# SQL queries and has not started a read or SQL query within the last 10
|
116
128
|
# seconds. Idle transactions can be aborted by Cloud Spanner so that they
|
@@ -121,7 +133,8 @@ module Google
|
|
121
133
|
# SQL query in the transaction (for example, `SELECT 1`) prevents the
|
122
134
|
# transaction from becoming idle.
|
123
135
|
#
|
124
|
-
# Snapshot
|
136
|
+
# Snapshot read-only transactions:
|
137
|
+
#
|
125
138
|
# Snapshot read-only transactions provides a simpler method than
|
126
139
|
# locking read-write transactions for doing several consistent
|
127
140
|
# reads. However, this type of transaction does not support writes.
|
@@ -153,13 +166,12 @@ module Google
|
|
153
166
|
#
|
154
167
|
# If the Cloud Spanner database to be read is geographically distributed,
|
155
168
|
# stale read-only transactions can execute more quickly than strong
|
156
|
-
# or read-write
|
169
|
+
# or read-write transactions, because they are able to execute far
|
157
170
|
# from the leader replica.
|
158
171
|
#
|
159
172
|
# Each type of timestamp bound is discussed in detail below.
|
160
173
|
#
|
161
|
-
# Strong:
|
162
|
-
# Strong reads are guaranteed to see the effects of all transactions
|
174
|
+
# Strong: Strong reads are guaranteed to see the effects of all transactions
|
163
175
|
# that have committed before the start of the read. Furthermore, all
|
164
176
|
# rows yielded by a single read are consistent with each other -- if
|
165
177
|
# any part of the read observes a transaction, all parts of the read
|
@@ -171,9 +183,13 @@ module Google
|
|
171
183
|
# reads should be executed within a transaction or at an exact read
|
172
184
|
# timestamp.
|
173
185
|
#
|
186
|
+
# Queries on change streams (see below for more details) must also specify
|
187
|
+
# the strong read timestamp bound.
|
188
|
+
#
|
174
189
|
# See {::Google::Cloud::Spanner::V1::TransactionOptions::ReadOnly#strong TransactionOptions.ReadOnly.strong}.
|
175
190
|
#
|
176
|
-
# Exact
|
191
|
+
# Exact staleness:
|
192
|
+
#
|
177
193
|
# These timestamp bounds execute reads at a user-specified
|
178
194
|
# timestamp. Reads at a timestamp are guaranteed to see a consistent
|
179
195
|
# prefix of the global transaction history: they observe
|
@@ -194,7 +210,8 @@ module Google
|
|
194
210
|
# See {::Google::Cloud::Spanner::V1::TransactionOptions::ReadOnly#read_timestamp TransactionOptions.ReadOnly.read_timestamp} and
|
195
211
|
# {::Google::Cloud::Spanner::V1::TransactionOptions::ReadOnly#exact_staleness TransactionOptions.ReadOnly.exact_staleness}.
|
196
212
|
#
|
197
|
-
# Bounded
|
213
|
+
# Bounded staleness:
|
214
|
+
#
|
198
215
|
# Bounded staleness modes allow Cloud Spanner to pick the read timestamp,
|
199
216
|
# subject to a user-provided staleness bound. Cloud Spanner chooses the
|
200
217
|
# newest timestamp within the staleness bound that allows execution
|
@@ -223,7 +240,8 @@ module Google
|
|
223
240
|
# See {::Google::Cloud::Spanner::V1::TransactionOptions::ReadOnly#max_staleness TransactionOptions.ReadOnly.max_staleness} and
|
224
241
|
# {::Google::Cloud::Spanner::V1::TransactionOptions::ReadOnly#min_read_timestamp TransactionOptions.ReadOnly.min_read_timestamp}.
|
225
242
|
#
|
226
|
-
# Old
|
243
|
+
# Old read timestamps and garbage collection:
|
244
|
+
#
|
227
245
|
# Cloud Spanner continuously garbage collects deleted and overwritten data
|
228
246
|
# in the background to reclaim storage space. This process is known
|
229
247
|
# as "version GC". By default, version GC reclaims versions after they
|
@@ -233,7 +251,41 @@ module Google
|
|
233
251
|
# timestamp become too old while executing. Reads and SQL queries with
|
234
252
|
# too-old read timestamps fail with the error `FAILED_PRECONDITION`.
|
235
253
|
#
|
236
|
-
#
|
254
|
+
# You can configure and extend the `VERSION_RETENTION_PERIOD` of a
|
255
|
+
# database up to a period as long as one week, which allows Cloud Spanner
|
256
|
+
# to perform reads up to one week in the past.
|
257
|
+
#
|
258
|
+
# Querying change Streams:
|
259
|
+
#
|
260
|
+
# A Change Stream is a schema object that can be configured to watch data
|
261
|
+
# changes on the entire database, a set of tables, or a set of columns
|
262
|
+
# in a database.
|
263
|
+
#
|
264
|
+
# When a change stream is created, Spanner automatically defines a
|
265
|
+
# corresponding SQL Table-Valued Function (TVF) that can be used to query
|
266
|
+
# the change records in the associated change stream using the
|
267
|
+
# ExecuteStreamingSql API. The name of the TVF for a change stream is
|
268
|
+
# generated from the name of the change stream: READ_<change_stream_name>.
|
269
|
+
#
|
270
|
+
# All queries on change stream TVFs must be executed using the
|
271
|
+
# ExecuteStreamingSql API with a single-use read-only transaction with a
|
272
|
+
# strong read-only timestamp_bound. The change stream TVF allows users to
|
273
|
+
# specify the start_timestamp and end_timestamp for the time range of
|
274
|
+
# interest. All change records within the retention period is accessible
|
275
|
+
# using the strong read-only timestamp_bound. All other TransactionOptions
|
276
|
+
# are invalid for change stream queries.
|
277
|
+
#
|
278
|
+
# In addition, if TransactionOptions.read_only.return_read_timestamp is set
|
279
|
+
# to true, a special value of 2^63 - 2 will be returned in the
|
280
|
+
# {::Google::Cloud::Spanner::V1::Transaction Transaction} message that describes the
|
281
|
+
# transaction, instead of a valid read timestamp. This special value should be
|
282
|
+
# discarded and not used for any subsequent queries.
|
283
|
+
#
|
284
|
+
# Please see https://cloud.google.com/spanner/docs/change-streams
|
285
|
+
# for more details on how to query the change stream TVFs.
|
286
|
+
#
|
287
|
+
# Partitioned DML transactions:
|
288
|
+
#
|
237
289
|
# Partitioned DML transactions are used to execute DML statements with a
|
238
290
|
# different execution strategy that provides different, and often better,
|
239
291
|
# scalability properties for large, table-wide operations than DML in a
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: google-cloud-spanner-v1
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.
|
4
|
+
version: 0.10.0
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Google LLC
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2022-
|
11
|
+
date: 2022-07-08 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: gapic-common
|
@@ -16,7 +16,7 @@ dependencies:
|
|
16
16
|
requirements:
|
17
17
|
- - ">="
|
18
18
|
- !ruby/object:Gem::Version
|
19
|
-
version: '0.
|
19
|
+
version: '0.10'
|
20
20
|
- - "<"
|
21
21
|
- !ruby/object:Gem::Version
|
22
22
|
version: 2.a
|
@@ -26,7 +26,7 @@ dependencies:
|
|
26
26
|
requirements:
|
27
27
|
- - ">="
|
28
28
|
- !ruby/object:Gem::Version
|
29
|
-
version: '0.
|
29
|
+
version: '0.10'
|
30
30
|
- - "<"
|
31
31
|
- !ruby/object:Gem::Version
|
32
32
|
version: 2.a
|
@@ -50,28 +50,28 @@ dependencies:
|
|
50
50
|
requirements:
|
51
51
|
- - "~>"
|
52
52
|
- !ruby/object:Gem::Version
|
53
|
-
version: 1.
|
53
|
+
version: 1.26.1
|
54
54
|
type: :development
|
55
55
|
prerelease: false
|
56
56
|
version_requirements: !ruby/object:Gem::Requirement
|
57
57
|
requirements:
|
58
58
|
- - "~>"
|
59
59
|
- !ruby/object:Gem::Version
|
60
|
-
version: 1.
|
60
|
+
version: 1.26.1
|
61
61
|
- !ruby/object:Gem::Dependency
|
62
62
|
name: minitest
|
63
63
|
requirement: !ruby/object:Gem::Requirement
|
64
64
|
requirements:
|
65
65
|
- - "~>"
|
66
66
|
- !ruby/object:Gem::Version
|
67
|
-
version: '5.
|
67
|
+
version: '5.16'
|
68
68
|
type: :development
|
69
69
|
prerelease: false
|
70
70
|
version_requirements: !ruby/object:Gem::Requirement
|
71
71
|
requirements:
|
72
72
|
- - "~>"
|
73
73
|
- !ruby/object:Gem::Version
|
74
|
-
version: '5.
|
74
|
+
version: '5.16'
|
75
75
|
- !ruby/object:Gem::Dependency
|
76
76
|
name: minitest-focus
|
77
77
|
requirement: !ruby/object:Gem::Requirement
|
@@ -106,14 +106,14 @@ dependencies:
|
|
106
106
|
requirements:
|
107
107
|
- - ">="
|
108
108
|
- !ruby/object:Gem::Version
|
109
|
-
version: '
|
109
|
+
version: '13.0'
|
110
110
|
type: :development
|
111
111
|
prerelease: false
|
112
112
|
version_requirements: !ruby/object:Gem::Requirement
|
113
113
|
requirements:
|
114
114
|
- - ">="
|
115
115
|
- !ruby/object:Gem::Version
|
116
|
-
version: '
|
116
|
+
version: '13.0'
|
117
117
|
- !ruby/object:Gem::Dependency
|
118
118
|
name: redcarpet
|
119
119
|
requirement: !ruby/object:Gem::Requirement
|
@@ -214,14 +214,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
|
|
214
214
|
requirements:
|
215
215
|
- - ">="
|
216
216
|
- !ruby/object:Gem::Version
|
217
|
-
version: '2.
|
217
|
+
version: '2.6'
|
218
218
|
required_rubygems_version: !ruby/object:Gem::Requirement
|
219
219
|
requirements:
|
220
220
|
- - ">="
|
221
221
|
- !ruby/object:Gem::Version
|
222
222
|
version: '0'
|
223
223
|
requirements: []
|
224
|
-
rubygems_version: 3.3.
|
224
|
+
rubygems_version: 3.3.14
|
225
225
|
signing_key:
|
226
226
|
specification_version: 4
|
227
227
|
summary: API Client library for the Cloud Spanner V1 API
|