Class: Google::Apis::BigtableadminV2::GoogleBigtableAdminV2TypeArray
- Inherits:
-
Object
- Object
- Google::Apis::BigtableadminV2::GoogleBigtableAdminV2TypeArray
- Includes:
- Core::Hashable, Core::JsonObjectSupport
- Defined in:
- lib/google/apis/bigtableadmin_v2/classes.rb,
lib/google/apis/bigtableadmin_v2/representations.rb,
lib/google/apis/bigtableadmin_v2/representations.rb
Overview
An ordered list of elements of a given type. Values of type Array
are stored
in Value.array_value
.
Instance Attribute Summary collapse
-
#element_type ⇒ Google::Apis::BigtableadminV2::Type
Type
represents the type of data that is written to, read from, or stored in Bigtable.
Instance Method Summary collapse
-
#initialize(**args) ⇒ GoogleBigtableAdminV2TypeArray
constructor
A new instance of GoogleBigtableAdminV2TypeArray.
-
#update!(**args) ⇒ Object
Update properties of this object.
Constructor Details
#initialize(**args) ⇒ GoogleBigtableAdminV2TypeArray
Returns a new instance of GoogleBigtableAdminV2TypeArray.
1769 1770 1771 |
# File 'lib/google/apis/bigtableadmin_v2/classes.rb', line 1769 def initialize(**args) update!(**args) end |
Instance Attribute Details
#element_type ⇒ Google::Apis::BigtableadminV2::Type
Type
represents the type of data that is written to, read from, or stored in
Bigtable. It is heavily based on the GoogleSQL standard to help maintain
familiarity and consistency across products and features. For compatibility
with Bigtable's existing untyped APIs, each Type
includes an Encoding
which describes how to convert to/from the underlying data. Each encoding also
defines the following properties: * Order-preserving: Does the encoded value
sort consistently with the original typed value? Note that Bigtable will
always sort data based on the raw encoded value, not the decoded type. -
Example: BYTES values sort in the same order as their raw encodings. -
Counterexample: Encoding INT64 as a fixed-width decimal string does not
preserve sort order when dealing with negative numbers. INT64(1) > INT64(-1)
,
but STRING("-00001") > STRING("00001)
. * Self-delimiting: If we concatenate
two encoded values, can we always tell where the first one ends and the second
one begins? - Example: If we encode INT64s to fixed-width STRINGs, the first
value will always contain exactly N digits, possibly preceded by a sign. -
Counterexample: If we concatenate two UTF-8 encoded STRINGs, we have no way to
tell where the first one ends. * Compatibility: Which other systems have
matching encoding schemes? For example, does this encoding have a GoogleSQL
equivalent? HBase? Java?
Corresponds to the JSON property elementType
1767 1768 1769 |
# File 'lib/google/apis/bigtableadmin_v2/classes.rb', line 1767 def element_type @element_type end |
Instance Method Details
#update!(**args) ⇒ Object
Update properties of this object
1774 1775 1776 |
# File 'lib/google/apis/bigtableadmin_v2/classes.rb', line 1774 def update!(**args) @element_type = args[:element_type] if args.key?(:element_type) end |