google-apis-bigtableadmin_v2 0.55.0 → 0.57.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +8 -0
- data/lib/google/apis/bigtableadmin_v2/classes.rb +56 -56
- data/lib/google/apis/bigtableadmin_v2/gem_version.rb +2 -2
- metadata +3 -3
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 9f2067c541f73d2053b94481e1aad921f404762d24c8ab1fb097f21af2341187
|
4
|
+
data.tar.gz: b14e6d46811af6aa61b4f1c4b077bf61cd7609ec7efc220724c357399e684603
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 91eedb26003cf9c756fcf00293847c69fd8ecaf9eb5d70c0b6c712e33f9e1b54e7a448b9a46b3fab4c92846190cfdc25419082816d122132b844423972ffc295
|
7
|
+
data.tar.gz: 7863be2ef388ec7ab108df123bb04556672258aabdb0c1d06183f3cfdd7a40e7d73b945e8bb602409e8e44cc423ce58e4e1d5c4e7f066b278560e69de44f6130
|
data/CHANGELOG.md
CHANGED
@@ -1,5 +1,13 @@
|
|
1
1
|
# Release history for google-apis-bigtableadmin_v2
|
2
2
|
|
3
|
+
### v0.57.0 (2024-06-16)
|
4
|
+
|
5
|
+
* Regenerated from discovery document revision 20240604
|
6
|
+
|
7
|
+
### v0.56.0 (2024-06-09)
|
8
|
+
|
9
|
+
* Regenerated from discovery document revision 20240522
|
10
|
+
|
3
11
|
### v0.55.0 (2024-05-19)
|
4
12
|
|
5
13
|
* Regenerated using generator version 0.15.0
|
@@ -314,10 +314,10 @@ module Google
|
|
314
314
|
# @return [String]
|
315
315
|
attr_accessor :end_time
|
316
316
|
|
317
|
-
# Required. The expiration time of the backup
|
318
|
-
#
|
319
|
-
#
|
320
|
-
#
|
317
|
+
# Required. The expiration time of the backup. When creating a backup or
|
318
|
+
# updating its `expire_time`, the new value must: - Be at most 90 days in the
|
319
|
+
# future - Be at least 6 hours in the future Once the `expire_time` has passed,
|
320
|
+
# Cloud Bigtable will delete the backup.
|
321
321
|
# Corresponds to the JSON property `expireTime`
|
322
322
|
# @return [String]
|
323
323
|
attr_accessor :expire_time
|
@@ -771,19 +771,19 @@ module Google
|
|
771
771
|
# Each link in the encoding chain also defines the following properties: *
|
772
772
|
# Natural sort: Does the encoded value sort consistently with the original typed
|
773
773
|
# value? Note that Bigtable will always sort data based on the raw encoded value,
|
774
|
-
# *not* the decoded type. - Example:
|
775
|
-
# their
|
776
|
-
#
|
777
|
-
# INT64(
|
778
|
-
#
|
779
|
-
#
|
780
|
-
#
|
781
|
-
#
|
782
|
-
#
|
783
|
-
#
|
784
|
-
#
|
785
|
-
#
|
786
|
-
#
|
774
|
+
# *not* the decoded type. - Example: BYTES values sort in the same order as
|
775
|
+
# their raw encodings. - Counterexample: Encoding INT64 to a fixed-width STRING
|
776
|
+
# does *not* preserve sort order when dealing with negative numbers. INT64(1) >
|
777
|
+
# INT64(-1), but STRING("-00001") > STRING("00001). - The overall encoding chain
|
778
|
+
# has this property if *every* link does. * Self-delimiting: If we concatenate
|
779
|
+
# two encoded values, can we always tell where the first one ends and the second
|
780
|
+
# one begins? - Example: If we encode INT64s to fixed-width STRINGs, the first
|
781
|
+
# value will always contain exactly N digits, possibly preceded by a sign. -
|
782
|
+
# Counterexample: If we concatenate two UTF-8 encoded STRINGs, we have no way to
|
783
|
+
# tell where the first one ends. - The overall encoding chain has this property
|
784
|
+
# if *any* link does. * Compatibility: Which other systems have matching
|
785
|
+
# encoding schemes? For example, does this encoding have a GoogleSQL equivalent?
|
786
|
+
# HBase? Java?
|
787
787
|
# Corresponds to the JSON property `valueType`
|
788
788
|
# @return [Google::Apis::BigtableadminV2::Type]
|
789
789
|
attr_accessor :value_type
|
@@ -1607,19 +1607,19 @@ module Google
|
|
1607
1607
|
# Each link in the encoding chain also defines the following properties: *
|
1608
1608
|
# Natural sort: Does the encoded value sort consistently with the original typed
|
1609
1609
|
# value? Note that Bigtable will always sort data based on the raw encoded value,
|
1610
|
-
# *not* the decoded type. - Example:
|
1611
|
-
# their
|
1612
|
-
#
|
1613
|
-
# INT64(
|
1614
|
-
#
|
1615
|
-
#
|
1616
|
-
#
|
1617
|
-
#
|
1618
|
-
#
|
1619
|
-
#
|
1620
|
-
#
|
1621
|
-
#
|
1622
|
-
#
|
1610
|
+
# *not* the decoded type. - Example: BYTES values sort in the same order as
|
1611
|
+
# their raw encodings. - Counterexample: Encoding INT64 to a fixed-width STRING
|
1612
|
+
# does *not* preserve sort order when dealing with negative numbers. INT64(1) >
|
1613
|
+
# INT64(-1), but STRING("-00001") > STRING("00001). - The overall encoding chain
|
1614
|
+
# has this property if *every* link does. * Self-delimiting: If we concatenate
|
1615
|
+
# two encoded values, can we always tell where the first one ends and the second
|
1616
|
+
# one begins? - Example: If we encode INT64s to fixed-width STRINGs, the first
|
1617
|
+
# value will always contain exactly N digits, possibly preceded by a sign. -
|
1618
|
+
# Counterexample: If we concatenate two UTF-8 encoded STRINGs, we have no way to
|
1619
|
+
# tell where the first one ends. - The overall encoding chain has this property
|
1620
|
+
# if *any* link does. * Compatibility: Which other systems have matching
|
1621
|
+
# encoding schemes? For example, does this encoding have a GoogleSQL equivalent?
|
1622
|
+
# HBase? Java?
|
1623
1623
|
# Corresponds to the JSON property `inputType`
|
1624
1624
|
# @return [Google::Apis::BigtableadminV2::Type]
|
1625
1625
|
attr_accessor :input_type
|
@@ -1635,19 +1635,19 @@ module Google
|
|
1635
1635
|
# Each link in the encoding chain also defines the following properties: *
|
1636
1636
|
# Natural sort: Does the encoded value sort consistently with the original typed
|
1637
1637
|
# value? Note that Bigtable will always sort data based on the raw encoded value,
|
1638
|
-
# *not* the decoded type. - Example:
|
1639
|
-
# their
|
1640
|
-
#
|
1641
|
-
# INT64(
|
1642
|
-
#
|
1643
|
-
#
|
1644
|
-
#
|
1645
|
-
#
|
1646
|
-
#
|
1647
|
-
#
|
1648
|
-
#
|
1649
|
-
#
|
1650
|
-
#
|
1638
|
+
# *not* the decoded type. - Example: BYTES values sort in the same order as
|
1639
|
+
# their raw encodings. - Counterexample: Encoding INT64 to a fixed-width STRING
|
1640
|
+
# does *not* preserve sort order when dealing with negative numbers. INT64(1) >
|
1641
|
+
# INT64(-1), but STRING("-00001") > STRING("00001). - The overall encoding chain
|
1642
|
+
# has this property if *every* link does. * Self-delimiting: If we concatenate
|
1643
|
+
# two encoded values, can we always tell where the first one ends and the second
|
1644
|
+
# one begins? - Example: If we encode INT64s to fixed-width STRINGs, the first
|
1645
|
+
# value will always contain exactly N digits, possibly preceded by a sign. -
|
1646
|
+
# Counterexample: If we concatenate two UTF-8 encoded STRINGs, we have no way to
|
1647
|
+
# tell where the first one ends. - The overall encoding chain has this property
|
1648
|
+
# if *any* link does. * Compatibility: Which other systems have matching
|
1649
|
+
# encoding schemes? For example, does this encoding have a GoogleSQL equivalent?
|
1650
|
+
# HBase? Java?
|
1651
1651
|
# Corresponds to the JSON property `stateType`
|
1652
1652
|
# @return [Google::Apis::BigtableadminV2::Type]
|
1653
1653
|
attr_accessor :state_type
|
@@ -3170,19 +3170,19 @@ module Google
|
|
3170
3170
|
# Each link in the encoding chain also defines the following properties: *
|
3171
3171
|
# Natural sort: Does the encoded value sort consistently with the original typed
|
3172
3172
|
# value? Note that Bigtable will always sort data based on the raw encoded value,
|
3173
|
-
# *not* the decoded type. - Example:
|
3174
|
-
# their
|
3175
|
-
#
|
3176
|
-
# INT64(
|
3177
|
-
#
|
3178
|
-
#
|
3179
|
-
#
|
3180
|
-
#
|
3181
|
-
#
|
3182
|
-
#
|
3183
|
-
#
|
3184
|
-
#
|
3185
|
-
#
|
3173
|
+
# *not* the decoded type. - Example: BYTES values sort in the same order as
|
3174
|
+
# their raw encodings. - Counterexample: Encoding INT64 to a fixed-width STRING
|
3175
|
+
# does *not* preserve sort order when dealing with negative numbers. INT64(1) >
|
3176
|
+
# INT64(-1), but STRING("-00001") > STRING("00001). - The overall encoding chain
|
3177
|
+
# has this property if *every* link does. * Self-delimiting: If we concatenate
|
3178
|
+
# two encoded values, can we always tell where the first one ends and the second
|
3179
|
+
# one begins? - Example: If we encode INT64s to fixed-width STRINGs, the first
|
3180
|
+
# value will always contain exactly N digits, possibly preceded by a sign. -
|
3181
|
+
# Counterexample: If we concatenate two UTF-8 encoded STRINGs, we have no way to
|
3182
|
+
# tell where the first one ends. - The overall encoding chain has this property
|
3183
|
+
# if *any* link does. * Compatibility: Which other systems have matching
|
3184
|
+
# encoding schemes? For example, does this encoding have a GoogleSQL equivalent?
|
3185
|
+
# HBase? Java?
|
3186
3186
|
class Type
|
3187
3187
|
include Google::Apis::Core::Hashable
|
3188
3188
|
|
@@ -16,13 +16,13 @@ module Google
|
|
16
16
|
module Apis
|
17
17
|
module BigtableadminV2
|
18
18
|
# Version of the google-apis-bigtableadmin_v2 gem
|
19
|
-
GEM_VERSION = "0.
|
19
|
+
GEM_VERSION = "0.57.0"
|
20
20
|
|
21
21
|
# Version of the code generator used to generate this client
|
22
22
|
GENERATOR_VERSION = "0.15.0"
|
23
23
|
|
24
24
|
# Revision of the discovery document this client was generated from
|
25
|
-
REVISION = "
|
25
|
+
REVISION = "20240604"
|
26
26
|
end
|
27
27
|
end
|
28
28
|
end
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: google-apis-bigtableadmin_v2
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.
|
4
|
+
version: 0.57.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: 2024-
|
11
|
+
date: 2024-06-16 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: google-apis-core
|
@@ -58,7 +58,7 @@ licenses:
|
|
58
58
|
metadata:
|
59
59
|
bug_tracker_uri: https://github.com/googleapis/google-api-ruby-client/issues
|
60
60
|
changelog_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-bigtableadmin_v2/CHANGELOG.md
|
61
|
-
documentation_uri: https://googleapis.dev/ruby/google-apis-bigtableadmin_v2/v0.
|
61
|
+
documentation_uri: https://googleapis.dev/ruby/google-apis-bigtableadmin_v2/v0.57.0
|
62
62
|
source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-bigtableadmin_v2
|
63
63
|
post_install_message:
|
64
64
|
rdoc_options: []
|