Skip to main content

​
◆ createType() [1/4]

CreateTypeResponse gpudb::GPUdb::createType (const CreateTypeRequest &request_) const

Creates a new type describing the columns of a table.

The type definition is specified as a list of columns, each specified as a list of the column name, data type, and any column attributes.

Example of a type definition with some parameters:

[
[“id”, “int8”, “primary_key”],
[“dept_id”, “int8”, “primary_key”, “shard_key”],
[“manager_id”, “int8”, “nullable”],
[“first_name”, “char32”],
[“last_name”, “char64”],
[“salary”, “decimal”],
[“hire_date”, “date”]
]

Each column definition consists of the column name (which should meet the standard column naming criteria), the column’s specific type (int, long, float, double, string, bytes, or any of the possible values for properties), and any data handling, data key, or data replacement properties.

Note that some properties are mutually exclusive–i.e. they cannot be specified for any given column simultaneously. One example of mutually exclusive properties are primary_key and nullable.

A single primary key and/or single shard key can be set across one or more columns. If a primary key is specified, then a uniqueness constraint is enforced, in that only a single object can exist with a given primary key column value (or set of values for the key columns, if using a composite primary key). When inserting data into a table with a primary key, depending on the parameters in the request, incoming objects with primary key values that match existing objects will either overwrite (i.e. update) the existing object or will be skipped and not added into the set.

Parameters
[in]request_Request object containing the parameters for the operation.
Returns
Response object containing the result of the operation.

​
◆ createType() [2/4]

CreateTypeResponse & gpudb::GPUdb::createType (const CreateTypeRequest &request_,
CreateTypeResponse &response_ ) const

Creates a new type describing the columns of a table.

The type definition is specified as a list of columns, each specified as a list of the column name, data type, and any column attributes.

Example of a type definition with some parameters:

[
[“id”, “int8”, “primary_key”],
[“dept_id”, “int8”, “primary_key”, “shard_key”],
[“manager_id”, “int8”, “nullable”],
[“first_name”, “char32”],
[“last_name”, “char64”],
[“salary”, “decimal”],
[“hire_date”, “date”]
]

Each column definition consists of the column name (which should meet the standard column naming criteria), the column’s specific type (int, long, float, double, string, bytes, or any of the possible values for properties), and any data handling, data key, or data replacement properties.

Note that some properties are mutually exclusive–i.e. they cannot be specified for any given column simultaneously. One example of mutually exclusive properties are primary_key and nullable.

A single primary key and/or single shard key can be set across one or more columns. If a primary key is specified, then a uniqueness constraint is enforced, in that only a single object can exist with a given primary key column value (or set of values for the key columns, if using a composite primary key). When inserting data into a table with a primary key, depending on the parameters in the request, incoming objects with primary key values that match existing objects will either overwrite (i.e. update) the existing object or will be skipped and not added into the set.

Parameters
[in]request_Request object containing the parameters for the operation.
[out]response_Response object containing the results of the operation.
Returns
Response object containing the result of the operation (initially passed in by reference).

​
◆ createType() [3/4]

CreateTypeResponse gpudb::GPUdb::createType (const std::string &typeDefinition,
const std::string &label,
const std::map< std::string, std::vector< std::string > > &properties,
const std::map< std::string, std::string > &options ) const

Creates a new type describing the columns of a table.

The type definition is specified as a list of columns, each specified as a list of the column name, data type, and any column attributes.

Example of a type definition with some parameters:

[
[“id”, “int8”, “primary_key”],
[“dept_id”, “int8”, “primary_key”, “shard_key”],
[“manager_id”, “int8”, “nullable”],
[“first_name”, “char32”],
[“last_name”, “char64”],
[“salary”, “decimal”],
[“hire_date”, “date”]
]

Each column definition consists of the column name (which should meet the standard column naming criteria), the column’s specific type (int, long, float, double, string, bytes, or any of the possible values for properties), and any data handling, data key, or data replacement properties.

Note that some properties are mutually exclusive–i.e. they cannot be specified for any given column simultaneously. One example of mutually exclusive properties are primary_key and nullable.

A single primary key and/or single shard key can be set across one or more columns. If a primary key is specified, then a uniqueness constraint is enforced, in that only a single object can exist with a given primary key column value (or set of values for the key columns, if using a composite primary key). When inserting data into a table with a primary key, depending on the parameters in the request, incoming objects with primary key values that match existing objects will either overwrite (i.e. update) the existing object or will be skipped and not added into the set.

Parameters
[in]typeDefinitionJSON string defining the columns of the type to be registered, as described above.
[in]labelA user-defined description string which can be used to differentiate between tables and types with otherwise identical schemas.
[in]properties[DEPRECATED–please use these property values in the typeDefinition directly, as described at the top, instead] Each key-value pair specifies the properties to use for a given column where the key is the column name. All keys used must be relevant column names for the given table. Specifying any property overrides the default properties for that column (which is based on the column’s data type). Valid values are:
  • create_type_data: Default property for all numeric and string type columns; makes the column available for GPU queries.
  • create_type_text_search: Valid only for select ‘string’ columns. Enables full text search–see Full Text Search for details and applicable string column types.
  • create_type_timestamp: Valid only for ‘long’ columns. Indicates that this field represents a timestamp and will be provided in milliseconds since the Unix epoch: 00:00:00 Jan 1 1970. Dates represented by a timestamp must fall between the year 1000 and the year 2900.
  • create_type_ulong: Valid only for ‘string’ columns. It represents an unsigned long integer data type. The string can only be interpreted as an unsigned long data type with minimum value of zero, and maximum value of 18446744073709551615.
  • create_type_uuid: Valid only for ‘string’ columns. It represents an uuid data type. Internally, it is stored as a 128-bit integer.
  • create_type_decimal: Valid only for ‘string’ columns. It represents a SQL type NUMERIC(19, 4) data type. There can be up to 15 digits before the decimal point and up to four digits in the fractional part. The value can be positive or negative (indicated by a minus sign at the beginning). This property is mutually exclusive with the text_search property.
  • create_type_date: Valid only for ‘string’ columns. Indicates that this field represents a date and will be provided in the format ‘YYYY-MM-DD’. The allowable range is 1000-01-01 through 2900-01-01. This property is mutually exclusive with the text_search property.
  • create_type_time: Valid only for ‘string’ columns. Indicates that this field represents a time-of-day and will be provided in the format ‘HH:MM:SS.mmm’. The allowable range is 00:00:00.000 through 23:59:59.999. This property is mutually exclusive with the text_search property.
  • create_type_datetime: Valid only for ‘string’ columns. Indicates that this field represents a datetime and will be provided in the format ‘YYYY-MM-DD HH:MM:SS.mmm’. The allowable range is 1000-01-01 00:00:00.000 through 2900-01-01 23:59:59.999. This property is mutually exclusive with the text_search property.
  • create_type_char1: This property provides optimized memory, disk and query performance for string columns. Strings with this property must be no longer than 1 character.
  • create_type_char2: This property provides optimized memory, disk and query performance for string columns. Strings with this property must be no longer than 2 characters.
  • create_type_char4: This property provides optimized memory, disk and query performance for string columns. Strings with this property must be no longer than 4 characters.
  • create_type_char8: This property provides optimized memory, disk and query performance for string columns. Strings with this property must be no longer than 8 characters.
  • create_type_char16: This property provides optimized memory, disk and query performance for string columns. Strings with this property must be no longer than 16 characters.
  • create_type_char32: This property provides optimized memory, disk and query performance for string columns. Strings with this property must be no longer than 32 characters.
  • create_type_char64: This property provides optimized memory, disk and query performance for string columns. Strings with this property must be no longer than 64 characters.
  • create_type_char128: This property provides optimized memory, disk and query performance for string columns. Strings with this property must be no longer than 128 characters.
  • create_type_char256: This property provides optimized memory, disk and query performance for string columns. Strings with this property must be no longer than 256 characters.
  • create_type_boolean: This property provides optimized memory and query performance for int columns. Ints with this property must be between 0 and 1(inclusive)
  • create_type_int8: This property provides optimized memory and query performance for int columns. Ints with this property must be between -128 and +127 (inclusive)
  • create_type_int16: This property provides optimized memory and query performance for int columns. Ints with this property must be between -32768 and +32767 (inclusive)
  • create_type_ipv4: This property provides optimized memory, disk and query performance for string columns representing IPv4 addresses (i.e. 192.168.1.1). Strings with this property must be of the form: A.B.C.D where A, B, C and D are in the range of 0-255.
  • create_type_array: Valid only for ‘string’ columns. Indicates that this field contains an array. The value type and (optionally) the item count should be specified in parenthesis; e.g., ‘array(int, 10)’ for a 10-integer array. Both ‘array(int)’ and ‘array(int, -1)’ will designate an unlimited-length integer array, though no bounds checking is performed on arrays of any length.
  • create_type_json: Valid only for ‘string’ columns. Indicates that this field contains values in JSON format.
  • create_type_vector: Valid only for ‘bytes’ columns. Indicates that this field contains a vector of floats. The length should be specified in parenthesis, e.g., ‘vector(1000)’.
  • create_type_wkt: Valid only for ‘string’ and ‘bytes’ columns. Indicates that this field contains geospatial geometry objects in Well-Known Text (WKT) or Well-Known Binary (WKB) format.
  • create_type_primary_key: This property indicates that this column will be part of (or the entire) primary key.
  • create_type_soft_primary_key: This property indicates that this column will be part of (or the entire) soft primary key.
  • create_type_shard_key: This property indicates that this column will be part of (or the entire) shard key.
  • create_type_nullable: This property indicates that this column is nullable. However, setting this property is insufficient for making the column nullable. The user must declare the type of the column as a union between its regular type and ‘null’ in the Avro schema for the record type in typeDefinition. For example, if a column is of type integer and is nullable, then the entry for the column in the Avro schema must be: [‘int’, ‘null’]. The C++, C#, Java, and Python APIs have built-in convenience for bypassing setting the Avro schema by hand. For those languages, one can use this property as usual and not have to worry about the Avro schema for the record.
  • create_type_compress: This property indicates that this column should be compressed with the given codec and optional level; e.g., ‘compress(snappy)’ for Snappy compression and ‘compress(zstd(7))’ for zstd level 7 compression. This property is primarily used in order to save disk space.
  • create_type_dict: This property indicates that this column should be dictionary encoded. It can only be used in conjunction with restricted string (charN), int, long or date columns. Dictionary encoding is best for columns where the cardinality (the number of unique values) is expected to be low. This property can save a large amount of memory.
  • create_type_init_with_now: For ‘date’, ‘time’, ‘datetime’, or ‘timestamp’ column types, replace empty strings and invalid timestamps with ‘NOW()’ upon insert.
  • create_type_init_with_uuid: For ‘uuid’ type, replace empty strings and invalid UUID values with randomly-generated UUIDs upon insert.
  • create_type_update_with_now: For ‘date’, ‘time’, ‘datetime’, or ‘timestamp’ column types, update the field with ‘NOW()’ upon any update.
  • create_type_update_with_user: For ‘charN’ or ‘string’ column types, update the field with the current user’s name upon any update.
  • create_type_default: Sets a default value expression for this column, e.g. ‘default(0)’, ‘default(”pending”)’, or ‘default(NOW())’. When the column is omitted from an insert via request_schema_str, the expression is evaluated and the result is used as the column value.
  • create_type_default_sql: Sets a default value expression for this column with SQL syntax, e.g. ‘default(0)’, ‘default(”pending”)’, or ‘default(NOW())’. Only used for showing the expression when generating SQL DDL.
The default value is an empty map.
[in]optionsOptional parameters.The default value is an empty map.
Returns
Response object containing the result of the operation.

​
◆ createType() [4/4]

CreateTypeResponse & gpudb::GPUdb::createType (const std::string &typeDefinition,
const std::string &label,
const std::map< std::string, std::vector< std::string > > &properties,
const std::map< std::string, std::string > &options,
CreateTypeResponse &response_ ) const

Creates a new type describing the columns of a table.

The type definition is specified as a list of columns, each specified as a list of the column name, data type, and any column attributes.

Example of a type definition with some parameters:

[
[“id”, “int8”, “primary_key”],
[“dept_id”, “int8”, “primary_key”, “shard_key”],
[“manager_id”, “int8”, “nullable”],
[“first_name”, “char32”],
[“last_name”, “char64”],
[“salary”, “decimal”],
[“hire_date”, “date”]
]

Each column definition consists of the column name (which should meet the standard column naming criteria), the column’s specific type (int, long, float, double, string, bytes, or any of the possible values for properties), and any data handling, data key, or data replacement properties.

Note that some properties are mutually exclusive–i.e. they cannot be specified for any given column simultaneously. One example of mutually exclusive properties are primary_key and nullable.

A single primary key and/or single shard key can be set across one or more columns. If a primary key is specified, then a uniqueness constraint is enforced, in that only a single object can exist with a given primary key column value (or set of values for the key columns, if using a composite primary key). When inserting data into a table with a primary key, depending on the parameters in the request, incoming objects with primary key values that match existing objects will either overwrite (i.e. update) the existing object or will be skipped and not added into the set.

Parameters
[in]typeDefinitionJSON string defining the columns of the type to be registered, as described above.
[in]labelA user-defined description string which can be used to differentiate between tables and types with otherwise identical schemas.
[in]properties[DEPRECATED–please use these property values in the typeDefinition directly, as described at the top, instead] Each key-value pair specifies the properties to use for a given column where the key is the column name. All keys used must be relevant column names for the given table. Specifying any property overrides the default properties for that column (which is based on the column’s data type). Valid values are:
  • create_type_data: Default property for all numeric and string type columns; makes the column available for GPU queries.
  • create_type_text_search: Valid only for select ‘string’ columns. Enables full text search–see Full Text Search for details and applicable string column types.
  • create_type_timestamp: Valid only for ‘long’ columns. Indicates that this field represents a timestamp and will be provided in milliseconds since the Unix epoch: 00:00:00 Jan 1 1970. Dates represented by a timestamp must fall between the year 1000 and the year 2900.
  • create_type_ulong: Valid only for ‘string’ columns. It represents an unsigned long integer data type. The string can only be interpreted as an unsigned long data type with minimum value of zero, and maximum value of 18446744073709551615.
  • create_type_uuid: Valid only for ‘string’ columns. It represents an uuid data type. Internally, it is stored as a 128-bit integer.
  • create_type_decimal: Valid only for ‘string’ columns. It represents a SQL type NUMERIC(19, 4) data type. There can be up to 15 digits before the decimal point and up to four digits in the fractional part. The value can be positive or negative (indicated by a minus sign at the beginning). This property is mutually exclusive with the text_search property.
  • create_type_date: Valid only for ‘string’ columns. Indicates that this field represents a date and will be provided in the format ‘YYYY-MM-DD’. The allowable range is 1000-01-01 through 2900-01-01. This property is mutually exclusive with the text_search property.
  • create_type_time: Valid only for ‘string’ columns. Indicates that this field represents a time-of-day and will be provided in the format ‘HH:MM:SS.mmm’. The allowable range is 00:00:00.000 through 23:59:59.999. This property is mutually exclusive with the text_search property.
  • create_type_datetime: Valid only for ‘string’ columns. Indicates that this field represents a datetime and will be provided in the format ‘YYYY-MM-DD HH:MM:SS.mmm’. The allowable range is 1000-01-01 00:00:00.000 through 2900-01-01 23:59:59.999. This property is mutually exclusive with the text_search property.
  • create_type_char1: This property provides optimized memory, disk and query performance for string columns. Strings with this property must be no longer than 1 character.
  • create_type_char2: This property provides optimized memory, disk and query performance for string columns. Strings with this property must be no longer than 2 characters.
  • create_type_char4: This property provides optimized memory, disk and query performance for string columns. Strings with this property must be no longer than 4 characters.
  • create_type_char8: This property provides optimized memory, disk and query performance for string columns. Strings with this property must be no longer than 8 characters.
  • create_type_char16: This property provides optimized memory, disk and query performance for string columns. Strings with this property must be no longer than 16 characters.
  • create_type_char32: This property provides optimized memory, disk and query performance for string columns. Strings with this property must be no longer than 32 characters.
  • create_type_char64: This property provides optimized memory, disk and query performance for string columns. Strings with this property must be no longer than 64 characters.
  • create_type_char128: This property provides optimized memory, disk and query performance for string columns. Strings with this property must be no longer than 128 characters.
  • create_type_char256: This property provides optimized memory, disk and query performance for string columns. Strings with this property must be no longer than 256 characters.
  • create_type_boolean: This property provides optimized memory and query performance for int columns. Ints with this property must be between 0 and 1(inclusive)
  • create_type_int8: This property provides optimized memory and query performance for int columns. Ints with this property must be between -128 and +127 (inclusive)
  • create_type_int16: This property provides optimized memory and query performance for int columns. Ints with this property must be between -32768 and +32767 (inclusive)
  • create_type_ipv4: This property provides optimized memory, disk and query performance for string columns representing IPv4 addresses (i.e. 192.168.1.1). Strings with this property must be of the form: A.B.C.D where A, B, C and D are in the range of 0-255.
  • create_type_array: Valid only for ‘string’ columns. Indicates that this field contains an array. The value type and (optionally) the item count should be specified in parenthesis; e.g., ‘array(int, 10)’ for a 10-integer array. Both ‘array(int)’ and ‘array(int, -1)’ will designate an unlimited-length integer array, though no bounds checking is performed on arrays of any length.
  • create_type_json: Valid only for ‘string’ columns. Indicates that this field contains values in JSON format.
  • create_type_vector: Valid only for ‘bytes’ columns. Indicates that this field contains a vector of floats. The length should be specified in parenthesis, e.g., ‘vector(1000)’.
  • create_type_wkt: Valid only for ‘string’ and ‘bytes’ columns. Indicates that this field contains geospatial geometry objects in Well-Known Text (WKT) or Well-Known Binary (WKB) format.
  • create_type_primary_key: This property indicates that this column will be part of (or the entire) primary key.
  • create_type_soft_primary_key: This property indicates that this column will be part of (or the entire) soft primary key.
  • create_type_shard_key: This property indicates that this column will be part of (or the entire) shard key.
  • create_type_nullable: This property indicates that this column is nullable. However, setting this property is insufficient for making the column nullable. The user must declare the type of the column as a union between its regular type and ‘null’ in the Avro schema for the record type in typeDefinition. For example, if a column is of type integer and is nullable, then the entry for the column in the Avro schema must be: [‘int’, ‘null’]. The C++, C#, Java, and Python APIs have built-in convenience for bypassing setting the Avro schema by hand. For those languages, one can use this property as usual and not have to worry about the Avro schema for the record.
  • create_type_compress: This property indicates that this column should be compressed with the given codec and optional level; e.g., ‘compress(snappy)’ for Snappy compression and ‘compress(zstd(7))’ for zstd level 7 compression. This property is primarily used in order to save disk space.
  • create_type_dict: This property indicates that this column should be dictionary encoded. It can only be used in conjunction with restricted string (charN), int, long or date columns. Dictionary encoding is best for columns where the cardinality (the number of unique values) is expected to be low. This property can save a large amount of memory.
  • create_type_init_with_now: For ‘date’, ‘time’, ‘datetime’, or ‘timestamp’ column types, replace empty strings and invalid timestamps with ‘NOW()’ upon insert.
  • create_type_init_with_uuid: For ‘uuid’ type, replace empty strings and invalid UUID values with randomly-generated UUIDs upon insert.
  • create_type_update_with_now: For ‘date’, ‘time’, ‘datetime’, or ‘timestamp’ column types, update the field with ‘NOW()’ upon any update.
  • create_type_update_with_user: For ‘charN’ or ‘string’ column types, update the field with the current user’s name upon any update.
  • create_type_default: Sets a default value expression for this column, e.g. ‘default(0)’, ‘default(”pending”)’, or ‘default(NOW())’. When the column is omitted from an insert via request_schema_str, the expression is evaluated and the result is used as the column value.
  • create_type_default_sql: Sets a default value expression for this column with SQL syntax, e.g. ‘default(0)’, ‘default(”pending”)’, or ‘default(NOW())’. Only used for showing the expression when generating SQL DDL.
The default value is an empty map.
[in]optionsOptional parameters.The default value is an empty map.
[out]response_Response object containing the results of the operation.
Returns
Response object containing the result of the operation (initially passed in by reference).