Skip to main content

​
◆ appendRecords() [1/4]

AppendRecordsResponse gpudb::GPUdb::appendRecords (const AppendRecordsRequest &request_) const

Append (or insert) all records from a source table (specified by sourceTableName) to a particular target table (specified by tableName).

The field map (specified by fieldMap) holds the user specified map of target table column names with their mapped source column names.

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

​
◆ appendRecords() [2/4]

AppendRecordsResponse & gpudb::GPUdb::appendRecords (const AppendRecordsRequest &request_,
AppendRecordsResponse &response_ ) const

Append (or insert) all records from a source table (specified by sourceTableName) to a particular target table (specified by tableName).

The field map (specified by fieldMap) holds the user specified map of target table column names with their mapped source column names.

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).

​
◆ appendRecords() [3/4]

AppendRecordsResponse gpudb::GPUdb::appendRecords (const std::string &tableName,
const std::string &sourceTableName,
const std::map< std::string, std::string > &fieldMap,
const std::map< std::string, std::string > &options ) const

Append (or insert) all records from a source table (specified by sourceTableName) to a particular target table (specified by tableName).

The field map (specified by fieldMap) holds the user specified map of target table column names with their mapped source column names.

Parameters
[in]tableNameThe table name for the records to be appended, in [schema_name.]table_name format, using standard name resolution rules. Must be an existing table.
[in]sourceTableNameThe source table name to get records from, in [schema_name.]table_name format, using standard name resolution rules. Must be an existing table name.
[in]fieldMapContains the mapping of column names from the target table (specified by tableName) as the keys, and corresponding column names or expressions (e.g., ‘col_name+1’) from the source table (specified by sourceTableName). Must be existing column names in source table and target table, and their types must be matched. For details on using expressions, see Expressions.
[in]optionsOptional parameters.
  • append_records_offset: A positive integer indicating the number of initial results to skip from sourceTableName. Default is 0. The minimum allowed value is 0. The maximum allowed value is MAX_INT. The default value is ‘0’.
  • append_records_limit: A positive integer indicating the maximum number of results to be returned from sourceTableName. Or END_OF_SET (-9999) to indicate that the max number of results should be returned. The default value is ‘-9999’.
  • append_records_expression: Filter expression to apply to the sourceTableName. The default value is ”.
  • append_records_order_by: Comma-separated list of the columns to be sorted by from source table (specified by sourceTableName), e.g., ‘timestamp asc, x desc’. The order_by columns do not have to be present in fieldMap. The default value is ”.
  • append_records_error_handling: Specifies how record errors are handled while appending source table records into the target table. Currently this governs primary-key collision behavior: skip and permissive drop the colliding source records and continue, while abort rejects the batch. Explicit update_on_existing_pk or ignore_existing_pk take precedence over this option. Supported values:
    • append_records_permissive: Source records that cannot be appended (e.g. a primary-key collision) are skipped and reported; the rest of the batch is appended.
    • append_records_skip: Source records that cannot be appended are skipped and reported; the rest of the batch is appended.
    • append_records_abort: A source record that cannot be appended (e.g. a primary-key collision) raises an error. This is the default.
    The default value is append_records_abort.
  • append_records_update_on_existing_pk: Specifies the record collision policy for inserting source table records (specified by sourceTableName) into a target table (specified by tableName) with a primary key. If set to true, any existing table record with primary key values that match those of a source table record being inserted will be replaced by that new record (the new data will be “upserted”). If set to false, any existing table record with primary key values that match those of a source table record being inserted will remain unchanged, while the source record will be rejected and an error handled as determined by ignore_existing_pk. If the specified table does not have a primary key, then this option has no effect. Supported values:The default value is append_records_false.
  • append_records_enable_inplace_updates: Applies only when upserting (when update_on_existing_pk is true). If set to true, an existing record matched by primary key is modified in place. If set to false, it is updated by deleting the existing record and inserting a replacement (delete and insert), which prevents the change from being reflected in dependent materialized views until they are refreshed. Supported values:The default value is append_records_true.
  • append_records_ignore_existing_pk: Specifies the record collision error-suppression policy for inserting source table records (specified by sourceTableName) into a target table (specified by tableName) with a primary key, only used when not in upsert mode (upsert mode is disabled when update_on_existing_pk is false). If set to true, any source table record being inserted that is rejected for having primary key values that match those of an existing target table record will be ignored with no error generated. If false, the rejection of any source table record for having primary key values matching an existing target table record will result in an error being raised. If the specified table does not have a primary key or if upsert mode is in effect (update_on_existing_pk is true), then this option has no effect. Supported values:
    • append_records_true: Ignore source table records whose primary key values collide with those of target table records.
    • append_records_false: Raise an error for any source table record whose primary key values collide with those of a target table record.
    The default value is append_records_false.
  • append_records_pk_conflict_predicate_higher: The record with higher value for the column resolves the primary-key insert conflict. The default value is ”.
  • append_records_pk_conflict_predicate_lower: The record with lower value for the column resolves the primary-key insert conflict. The default value is ”.
  • append_records_truncate_strings: If set to true, it allows inserting longer strings into smaller charN string columns by truncating the longer strings to fit. Supported values:The default value is append_records_false.
The default value is an empty map.
Returns
Response object containing the result of the operation.

​
◆ appendRecords() [4/4]

AppendRecordsResponse & gpudb::GPUdb::appendRecords (const std::string &tableName,
const std::string &sourceTableName,
const std::map< std::string, std::string > &fieldMap,
const std::map< std::string, std::string > &options,
AppendRecordsResponse &response_ ) const

Append (or insert) all records from a source table (specified by sourceTableName) to a particular target table (specified by tableName).

The field map (specified by fieldMap) holds the user specified map of target table column names with their mapped source column names.

Parameters
[in]tableNameThe table name for the records to be appended, in [schema_name.]table_name format, using standard name resolution rules. Must be an existing table.
[in]sourceTableNameThe source table name to get records from, in [schema_name.]table_name format, using standard name resolution rules. Must be an existing table name.
[in]fieldMapContains the mapping of column names from the target table (specified by tableName) as the keys, and corresponding column names or expressions (e.g., ‘col_name+1’) from the source table (specified by sourceTableName). Must be existing column names in source table and target table, and their types must be matched. For details on using expressions, see Expressions.
[in]optionsOptional parameters.
  • append_records_offset: A positive integer indicating the number of initial results to skip from sourceTableName. Default is 0. The minimum allowed value is 0. The maximum allowed value is MAX_INT. The default value is ‘0’.
  • append_records_limit: A positive integer indicating the maximum number of results to be returned from sourceTableName. Or END_OF_SET (-9999) to indicate that the max number of results should be returned. The default value is ‘-9999’.
  • append_records_expression: Filter expression to apply to the sourceTableName. The default value is ”.
  • append_records_order_by: Comma-separated list of the columns to be sorted by from source table (specified by sourceTableName), e.g., ‘timestamp asc, x desc’. The order_by columns do not have to be present in fieldMap. The default value is ”.
  • append_records_error_handling: Specifies how record errors are handled while appending source table records into the target table. Currently this governs primary-key collision behavior: skip and permissive drop the colliding source records and continue, while abort rejects the batch. Explicit update_on_existing_pk or ignore_existing_pk take precedence over this option. Supported values:
    • append_records_permissive: Source records that cannot be appended (e.g. a primary-key collision) are skipped and reported; the rest of the batch is appended.
    • append_records_skip: Source records that cannot be appended are skipped and reported; the rest of the batch is appended.
    • append_records_abort: A source record that cannot be appended (e.g. a primary-key collision) raises an error. This is the default.
    The default value is append_records_abort.
  • append_records_update_on_existing_pk: Specifies the record collision policy for inserting source table records (specified by sourceTableName) into a target table (specified by tableName) with a primary key. If set to true, any existing table record with primary key values that match those of a source table record being inserted will be replaced by that new record (the new data will be “upserted”). If set to false, any existing table record with primary key values that match those of a source table record being inserted will remain unchanged, while the source record will be rejected and an error handled as determined by ignore_existing_pk. If the specified table does not have a primary key, then this option has no effect. Supported values:The default value is append_records_false.
  • append_records_enable_inplace_updates: Applies only when upserting (when update_on_existing_pk is true). If set to true, an existing record matched by primary key is modified in place. If set to false, it is updated by deleting the existing record and inserting a replacement (delete and insert), which prevents the change from being reflected in dependent materialized views until they are refreshed. Supported values:The default value is append_records_true.
  • append_records_ignore_existing_pk: Specifies the record collision error-suppression policy for inserting source table records (specified by sourceTableName) into a target table (specified by tableName) with a primary key, only used when not in upsert mode (upsert mode is disabled when update_on_existing_pk is false). If set to true, any source table record being inserted that is rejected for having primary key values that match those of an existing target table record will be ignored with no error generated. If false, the rejection of any source table record for having primary key values matching an existing target table record will result in an error being raised. If the specified table does not have a primary key or if upsert mode is in effect (update_on_existing_pk is true), then this option has no effect. Supported values:
    • append_records_true: Ignore source table records whose primary key values collide with those of target table records.
    • append_records_false: Raise an error for any source table record whose primary key values collide with those of a target table record.
    The default value is append_records_false.
  • append_records_pk_conflict_predicate_higher: The record with higher value for the column resolves the primary-key insert conflict. The default value is ”.
  • append_records_pk_conflict_predicate_lower: The record with lower value for the column resolves the primary-key insert conflict. The default value is ”.
  • append_records_truncate_strings: If set to true, it allows inserting longer strings into smaller charN string columns by truncating the longer strings to fit. Supported values:The default value is append_records_false.
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).