Class: Google::Apis::BigtableadminV2::GoogleBigtableAdminV2TypeAggregate

Inherits:
Object
  • Object
show all
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

A value that combines incremental updates into a summarized value. Data is never directly written or read using type Aggregate. Writes provide either the input_type or state_type, and reads always return the state_type .

Instance Attribute Summary collapse

Instance Method Summary collapse

Constructor Details

#initialize(**args) ⇒ GoogleBigtableAdminV2TypeAggregate

Returns a new instance of GoogleBigtableAdminV2TypeAggregate.



1946
1947
1948
 
# File 'lib/google/apis/bigtableadmin_v2/classes.rb', line 1946

def initialize(**args)
   update!(**args)
end

Instance Attribute Details

#hllpp_unique_count ⇒ Google::Apis::BigtableadminV2::GoogleBigtableAdminV2TypeAggregateHyperLogLogPlusPlusUniqueCount

Computes an approximate unique count over the input values. When using raw data as input, be careful to use a consistent encoding. Otherwise the same value encoded differently could count more than once, or two distinct values could count as identical. Input: Any, or omit for Raw State: TBD Special state conversions: Int64 (the unique count estimate) Corresponds to the JSON property hllppUniqueCount

Returns:



1886
1887
1888
 
# File 'lib/google/apis/bigtableadmin_v2/classes.rb', line 1886

def hllpp_unique_count
  @hllpp_unique_count
end

#input_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 or from the underlying data. Each encoding can operate in one of two modes: - Sorted: In this mode, Bigtable guarantees that Encode(X) <= Encode(Y) if and only if X <= Y. This is useful anywhere sort order is important, for example when encoding keys. - Distinct: In this mode, Bigtable guarantees that if X != Y then Encode(X) != Encode(Y). However, the converse is not guaranteed. For example, both 'foo': '1', 'bar': '2' and 'bar': '2', 'foo': '1' are valid encodings of the same JSON value. The API clearly documents which mode is used wherever an encoding can be configured. Each encoding also documents which values are supported in which modes. For example, when encoding INT64 as a numeric STRING, negative numbers cannot be encoded in sorted mode. This is because INT64(1) > INT64(-1) , but STRING("-00001") > STRING("00001"). Corresponds to the JSON property inputType

Returns:



1906
1907
1908
 
# File 'lib/google/apis/bigtableadmin_v2/classes.rb', line 1906

def input_type
  @input_type
end

#max ⇒ Google::Apis::BigtableadminV2::GoogleBigtableAdminV2TypeAggregateMax

Computes the max of the input values. Allowed input: Int64 State: same as input Corresponds to the JSON property max

Returns:



1912
1913
1914
 
# File 'lib/google/apis/bigtableadmin_v2/classes.rb', line 1912

def max
  @max
end

#min ⇒ Google::Apis::BigtableadminV2::GoogleBigtableAdminV2TypeAggregateMin

Computes the min of the input values. Allowed input: Int64 State: same as input Corresponds to the JSON property min

Returns:



1918
1919
1920
 
# File 'lib/google/apis/bigtableadmin_v2/classes.rb', line 1918

def min
  @min
end

#state_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 or from the underlying data. Each encoding can operate in one of two modes: - Sorted: In this mode, Bigtable guarantees that Encode(X) <= Encode(Y) if and only if X <= Y. This is useful anywhere sort order is important, for example when encoding keys. - Distinct: In this mode, Bigtable guarantees that if X != Y then Encode(X) != Encode(Y). However, the converse is not guaranteed. For example, both 'foo': '1', 'bar': '2' and 'bar': '2', 'foo': '1' are valid encodings of the same JSON value. The API clearly documents which mode is used wherever an encoding can be configured. Each encoding also documents which values are supported in which modes. For example, when encoding INT64 as a numeric STRING, negative numbers cannot be encoded in sorted mode. This is because INT64(1) > INT64(-1) , but STRING("-00001") > STRING("00001"). Corresponds to the JSON property stateType

Returns:



1938
1939
1940
 
# File 'lib/google/apis/bigtableadmin_v2/classes.rb', line 1938

def state_type
  @state_type
end

#sum ⇒ Google::Apis::BigtableadminV2::GoogleBigtableAdminV2TypeAggregateSum

Computes the sum of the input values. Allowed input: Int64 State: same as input Corresponds to the JSON property sum

Returns:



1944
1945
1946
 
# File 'lib/google/apis/bigtableadmin_v2/classes.rb', line 1944

def sum
  @sum
end

Instance Method Details

#update!(**args) ⇒ Object

Update properties of this object



1951
1952
1953
1954
1955
1956
1957
1958
 
# File 'lib/google/apis/bigtableadmin_v2/classes.rb', line 1951

def update!(**args)
  @hllpp_unique_count = args[:hllpp_unique_count] if args.key?(:hllpp_unique_count)
  @input_type = args[:input_type] if args.key?(:input_type)
  @max = args[:max] if args.key?(:max)
  @min = args[:min] if args.key?(:min)
  @state_type = args[:state_type] if args.key?(:state_type)
  @sum = args[:sum] if args.key?(:sum)
end