google-apis-bigtableadmin_v2 0.58.0 → 0.59.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 9be357010d76ff45a0e26d20cb9791ef387d2e629cfded0ef129116bec48f773
4
- data.tar.gz: fa6111b2fc3fedbe0dddfbce94029e6fc455b9116999c91ab6c6a1b9f63c5e65
3
+ metadata.gz: 9dae557d01a00c4b6572f9dc26dc879506eb29081f2063d8611c08680b3d8f82
4
+ data.tar.gz: fb0feaf650a94b0cc695302276d67c915e277be32b8cf224c1ba6314dbac2960
5
5
  SHA512:
6
- metadata.gz: 97b22b1bf94543f2100add67066e09d845b72c9b15e53353652c88dd2da6f7c26e6796cb088400b0e95fdb6ce11aab35eb8c93791a3f926469f540ec1a9331b2
7
- data.tar.gz: 4e35a2a4424bdc0e5fb5995212c93f2e032c85311f45cb26822d4d02686db2165d6df2c8df466baaa46850099581ad4683a1883325ccc2f8cf8905bbb8a5f4d2
6
+ metadata.gz: 810a6d2860281ddb54096dfa4c91d3d8ec4509c05634688fc200df130912f26e928cc849ad8226a77f62d22a444c65f78e68f544d6b5f1456bcf35cc327e9be3
7
+ data.tar.gz: d5fc805e5b288866899d7890ca9f0f8506c7151d96c84f2b4869a815d7b08b33c1016ecef50d40143d7231012390639c198ae668a29dd785f3f78ff9263edc7d
data/CHANGELOG.md CHANGED
@@ -1,5 +1,10 @@
1
1
  # Release history for google-apis-bigtableadmin_v2
2
2
 
3
+ ### v0.59.0 (2024-08-04)
4
+
5
+ * Regenerated from discovery document revision 20240720
6
+ * Regenerated using generator version 0.15.1
7
+
3
8
  ### v0.58.0 (2024-07-25)
4
9
 
5
10
  * Regenerated from discovery document revision 20240703
@@ -770,8 +770,8 @@ module Google
770
770
  # always sort data based on the raw encoded value, *not* the decoded type. -
771
771
  # Example: BYTES values sort in the same order as their raw encodings. -
772
772
  # Counterexample: Encoding INT64 as a fixed-width decimal string does *not*
773
- # preserve sort order when dealing with negative numbers. INT64(1) > INT64(-1),
774
- # but STRING("-00001") > STRING("00001). * Self-delimiting: If we concatenate
773
+ # preserve sort order when dealing with negative numbers. `INT64(1) > INT64(-1)`,
774
+ # but `STRING("-00001") > STRING("00001)`. * Self-delimiting: If we concatenate
775
775
  # two encoded values, can we always tell where the first one ends and the second
776
776
  # one begins? - Example: If we encode INT64s to fixed-width STRINGs, the first
777
777
  # value will always contain exactly N digits, possibly preceded by a sign. -
@@ -1610,8 +1610,8 @@ module Google
1610
1610
  # always sort data based on the raw encoded value, *not* the decoded type. -
1611
1611
  # Example: BYTES values sort in the same order as their raw encodings. -
1612
1612
  # Counterexample: Encoding INT64 as a fixed-width decimal string does *not*
1613
- # preserve sort order when dealing with negative numbers. INT64(1) > INT64(-1),
1614
- # but STRING("-00001") > STRING("00001). * Self-delimiting: If we concatenate
1613
+ # preserve sort order when dealing with negative numbers. `INT64(1) > INT64(-1)`,
1614
+ # but `STRING("-00001") > STRING("00001)`. * Self-delimiting: If we concatenate
1615
1615
  # two encoded values, can we always tell where the first one ends and the second
1616
1616
  # one begins? - Example: If we encode INT64s to fixed-width STRINGs, the first
1617
1617
  # value will always contain exactly N digits, possibly preceded by a sign. -
@@ -1645,8 +1645,8 @@ module Google
1645
1645
  # always sort data based on the raw encoded value, *not* the decoded type. -
1646
1646
  # Example: BYTES values sort in the same order as their raw encodings. -
1647
1647
  # Counterexample: Encoding INT64 as a fixed-width decimal string does *not*
1648
- # preserve sort order when dealing with negative numbers. INT64(1) > INT64(-1),
1649
- # but STRING("-00001") > STRING("00001). * Self-delimiting: If we concatenate
1648
+ # preserve sort order when dealing with negative numbers. `INT64(1) > INT64(-1)`,
1649
+ # but `STRING("-00001") > STRING("00001)`. * Self-delimiting: If we concatenate
1650
1650
  # two encoded values, can we always tell where the first one ends and the second
1651
1651
  # one begins? - Example: If we encode INT64s to fixed-width STRINGs, the first
1652
1652
  # value will always contain exactly N digits, possibly preceded by a sign. -
@@ -1753,8 +1753,8 @@ module Google
1753
1753
  # always sort data based on the raw encoded value, *not* the decoded type. -
1754
1754
  # Example: BYTES values sort in the same order as their raw encodings. -
1755
1755
  # Counterexample: Encoding INT64 as a fixed-width decimal string does *not*
1756
- # preserve sort order when dealing with negative numbers. INT64(1) > INT64(-1),
1757
- # but STRING("-00001") > STRING("00001). * Self-delimiting: If we concatenate
1756
+ # preserve sort order when dealing with negative numbers. `INT64(1) > INT64(-1)`,
1757
+ # but `STRING("-00001") > STRING("00001)`. * Self-delimiting: If we concatenate
1758
1758
  # two encoded values, can we always tell where the first one ends and the second
1759
1759
  # one begins? - Example: If we encode INT64s to fixed-width STRINGs, the first
1760
1760
  # value will always contain exactly N digits, possibly preceded by a sign. -
@@ -1963,8 +1963,8 @@ module Google
1963
1963
  # always sort data based on the raw encoded value, *not* the decoded type. -
1964
1964
  # Example: BYTES values sort in the same order as their raw encodings. -
1965
1965
  # Counterexample: Encoding INT64 as a fixed-width decimal string does *not*
1966
- # preserve sort order when dealing with negative numbers. INT64(1) > INT64(-1),
1967
- # but STRING("-00001") > STRING("00001). * Self-delimiting: If we concatenate
1966
+ # preserve sort order when dealing with negative numbers. `INT64(1) > INT64(-1)`,
1967
+ # but `STRING("-00001") > STRING("00001)`. * Self-delimiting: If we concatenate
1968
1968
  # two encoded values, can we always tell where the first one ends and the second
1969
1969
  # one begins? - Example: If we encode INT64s to fixed-width STRINGs, the first
1970
1970
  # value will always contain exactly N digits, possibly preceded by a sign. -
@@ -1986,8 +1986,8 @@ module Google
1986
1986
  # always sort data based on the raw encoded value, *not* the decoded type. -
1987
1987
  # Example: BYTES values sort in the same order as their raw encodings. -
1988
1988
  # Counterexample: Encoding INT64 as a fixed-width decimal string does *not*
1989
- # preserve sort order when dealing with negative numbers. INT64(1) > INT64(-1),
1990
- # but STRING("-00001") > STRING("00001). * Self-delimiting: If we concatenate
1989
+ # preserve sort order when dealing with negative numbers. `INT64(1) > INT64(-1)`,
1990
+ # but `STRING("-00001") > STRING("00001)`. * Self-delimiting: If we concatenate
1991
1991
  # two encoded values, can we always tell where the first one ends and the second
1992
1992
  # one begins? - Example: If we encode INT64s to fixed-width STRINGs, the first
1993
1993
  # value will always contain exactly N digits, possibly preceded by a sign. -
@@ -2040,6 +2040,11 @@ module Google
2040
2040
  # @return [Google::Apis::BigtableadminV2::GoogleBigtableAdminV2TypeStringEncodingUtf8Bytes]
2041
2041
  attr_accessor :utf8_bytes
2042
2042
 
2043
+ # Deprecated: prefer the equivalent `Utf8Bytes`.
2044
+ # Corresponds to the JSON property `utf8Raw`
2045
+ # @return [Google::Apis::BigtableadminV2::GoogleBigtableAdminV2TypeStringEncodingUtf8Raw]
2046
+ attr_accessor :utf8_raw
2047
+
2043
2048
  def initialize(**args)
2044
2049
  update!(**args)
2045
2050
  end
@@ -2047,6 +2052,7 @@ module Google
2047
2052
  # Update properties of this object
2048
2053
  def update!(**args)
2049
2054
  @utf8_bytes = args[:utf8_bytes] if args.key?(:utf8_bytes)
2055
+ @utf8_raw = args[:utf8_raw] if args.key?(:utf8_raw)
2050
2056
  end
2051
2057
  end
2052
2058
 
@@ -2065,6 +2071,19 @@ module Google
2065
2071
  end
2066
2072
  end
2067
2073
 
2074
+ # Deprecated: prefer the equivalent `Utf8Bytes`.
2075
+ class GoogleBigtableAdminV2TypeStringEncodingUtf8Raw
2076
+ include Google::Apis::Core::Hashable
2077
+
2078
+ def initialize(**args)
2079
+ update!(**args)
2080
+ end
2081
+
2082
+ # Update properties of this object
2083
+ def update!(**args)
2084
+ end
2085
+ end
2086
+
2068
2087
  # A structured data value, consisting of fields which map to dynamically typed
2069
2088
  # values. Values of type `Struct` are stored in `Value.array_value` where
2070
2089
  # entries are in the same order and number as `field_types`.
@@ -2106,8 +2125,8 @@ module Google
2106
2125
  # always sort data based on the raw encoded value, *not* the decoded type. -
2107
2126
  # Example: BYTES values sort in the same order as their raw encodings. -
2108
2127
  # Counterexample: Encoding INT64 as a fixed-width decimal string does *not*
2109
- # preserve sort order when dealing with negative numbers. INT64(1) > INT64(-1),
2110
- # but STRING("-00001") > STRING("00001). * Self-delimiting: If we concatenate
2128
+ # preserve sort order when dealing with negative numbers. `INT64(1) > INT64(-1)`,
2129
+ # but `STRING("-00001") > STRING("00001)`. * Self-delimiting: If we concatenate
2111
2130
  # two encoded values, can we always tell where the first one ends and the second
2112
2131
  # one begins? - Example: If we encode INT64s to fixed-width STRINGs, the first
2113
2132
  # value will always contain exactly N digits, possibly preceded by a sign. -
@@ -3512,8 +3531,8 @@ module Google
3512
3531
  # always sort data based on the raw encoded value, *not* the decoded type. -
3513
3532
  # Example: BYTES values sort in the same order as their raw encodings. -
3514
3533
  # Counterexample: Encoding INT64 as a fixed-width decimal string does *not*
3515
- # preserve sort order when dealing with negative numbers. INT64(1) > INT64(-1),
3516
- # but STRING("-00001") > STRING("00001). * Self-delimiting: If we concatenate
3534
+ # preserve sort order when dealing with negative numbers. `INT64(1) > INT64(-1)`,
3535
+ # but `STRING("-00001") > STRING("00001)`. * Self-delimiting: If we concatenate
3517
3536
  # two encoded values, can we always tell where the first one ends and the second
3518
3537
  # one begins? - Example: If we encode INT64s to fixed-width STRINGs, the first
3519
3538
  # value will always contain exactly N digits, possibly preceded by a sign. -
@@ -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.58.0"
19
+ GEM_VERSION = "0.59.0"
20
20
 
21
21
  # Version of the code generator used to generate this client
22
- GENERATOR_VERSION = "0.15.0"
22
+ GENERATOR_VERSION = "0.15.1"
23
23
 
24
24
  # Revision of the discovery document this client was generated from
25
- REVISION = "20240703"
25
+ REVISION = "20240720"
26
26
  end
27
27
  end
28
28
  end
@@ -400,6 +400,12 @@ module Google
400
400
  include Google::Apis::Core::JsonObjectSupport
401
401
  end
402
402
 
403
+ class GoogleBigtableAdminV2TypeStringEncodingUtf8Raw
404
+ class Representation < Google::Apis::Core::JsonRepresentation; end
405
+
406
+ include Google::Apis::Core::JsonObjectSupport
407
+ end
408
+
403
409
  class GoogleBigtableAdminV2TypeStruct
404
410
  class Representation < Google::Apis::Core::JsonRepresentation; end
405
411
 
@@ -1254,6 +1260,8 @@ module Google
1254
1260
  class Representation < Google::Apis::Core::JsonRepresentation
1255
1261
  property :utf8_bytes, as: 'utf8Bytes', class: Google::Apis::BigtableadminV2::GoogleBigtableAdminV2TypeStringEncodingUtf8Bytes, decorator: Google::Apis::BigtableadminV2::GoogleBigtableAdminV2TypeStringEncodingUtf8Bytes::Representation
1256
1262
 
1263
+ property :utf8_raw, as: 'utf8Raw', class: Google::Apis::BigtableadminV2::GoogleBigtableAdminV2TypeStringEncodingUtf8Raw, decorator: Google::Apis::BigtableadminV2::GoogleBigtableAdminV2TypeStringEncodingUtf8Raw::Representation
1264
+
1257
1265
  end
1258
1266
  end
1259
1267
 
@@ -1263,6 +1271,12 @@ module Google
1263
1271
  end
1264
1272
  end
1265
1273
 
1274
+ class GoogleBigtableAdminV2TypeStringEncodingUtf8Raw
1275
+ # @private
1276
+ class Representation < Google::Apis::Core::JsonRepresentation
1277
+ end
1278
+ end
1279
+
1266
1280
  class GoogleBigtableAdminV2TypeStruct
1267
1281
  # @private
1268
1282
  class Representation < Google::Apis::Core::JsonRepresentation
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.58.0
4
+ version: 0.59.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-07-25 00:00:00.000000000 Z
11
+ date: 2024-08-04 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.58.0
61
+ documentation_uri: https://googleapis.dev/ruby/google-apis-bigtableadmin_v2/v0.59.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: []