URL: http://<db.host>:<db.port>/insert/records/fromquery
Input Parameter Description
string
Name of the table into which the data will be inserted, in [schema_name.]table_name format, using standard name resolution rules. If the table does not exist, the table will be created using either an existing type_id or the type inferred from the remote query, and the new table name will have to meet standard table naming criteria.
string
Query for which result data needs to be imported.
map of string to maps of string to strings
Not implemented yet.The default value is an empty map ( {} ).
map of string to strings
Options used when creating the target table.The default value is an empty map ( {} ).
Show create_table_options
Show create_table_options
If true, prevents an error from occurring if the table already exists and is of the given type. If a table with the same ID but a different type exists, it is still an error.The default value is
false.The supported values are:- true
- false
Affects the distribution scheme for the table’s data. If true and the given type has no explicit shard key defined, the table will be replicated. If false, the table will be sharded according to the shard key specified in the given type_id, or randomly sharded, if no shard key is specified. Note that a type containing a shard key cannot be used to create a replicated table.The default value is
false.The supported values are:- true
- false
Semicolon-separated list of foreign keys, of the format ‘(source_column_name [, …]) references target_table_name(primary_key_column_name [, …]) [as foreign_key_name]’.
Foreign shard key of the format ‘source_column references shard_by_column from target_table(primary_key_column)’.
Partitioning scheme to use.
- RANGE: Use range partitioning.
- INTERVAL: Use interval partitioning.
- LIST: Use list partitioning.
- HASH: Use hash partitioning.
- SERIES: Use series partitioning.
Comma-separated list of partition keys, which are the columns or column expressions by which records will be assigned to partitions defined by partition_definitions.
Comma-separated list of partition definitions, whose format depends on the choice of partition_type. See range partitioning, interval partitioning, list partitioning, hash partitioning, or series partitioning for example formats.
If true, a new partition will be created for values which don’t fall into an existing partition. Currently only supported for list partitions.The default value is
false.The supported values are:- true
- false
Indicates the number of records per chunk to be used for this table.
Indicates whether the table is a memory-only table. A result table cannot contain columns with text_search data-handling, and it will not be retained if the server is restarted.The default value is
false.The supported values are:- true
- false
The tier strategy for the table and its columns.
The default compression codec for this table’s columns.
map of string to strings
Optional parameters.The default value is an empty map ( {} ).
Show options
Show options
Name of a table to which records that were rejected are written. The bad-record-table has the following columns: line_number (long), line_rejected (string), error_message (string). When error handling is Abort, bad records table is not populated.
A positive integer indicating the maximum number of records that can be written to the bad-record-table. Default value is 10000.
Number of records per batch when inserting data.
Name of an existing external data source from which table will be loaded.
Specifies how errors should be handled upon insertion.The default value is
abort.- permissive: Records with missing columns are populated with nulls if possible; otherwise, the malformed records are skipped.
- skip: Malformed records are skipped.
- ignore_bad_records: Deprecated. Alias for skip.
- abort: Stops current insertion and aborts entire operation when an error is encountered. Primary key collisions are considered abortable errors in this mode.
The record with higher value for the column resolves the primary-key insert conflict.The default value is ”.
The record with lower value for the column resolves the primary-key insert conflict.The default value is ”.
Specifies the record collision error-suppression policy for inserting into a table 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 record being inserted that is rejected for having primary key values that match those of an existing table record will be ignored with no error generated. If false, the rejection of any record for having primary key values matching an existing record will result in an error being reported, as determined by error_handling. 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.The default value is
false.- true: Ignore new records whose primary key values collide with those of existing records.
- false: Treat as errors any new records whose primary key values collide with those of existing records.
Whether to do a full load, dry run, or perform a type inference on the source data.The default value is
full.- full: Run a type inference on the source data (if needed) and ingest.
- dry_run: Does not load data, but walks through the source data and determines the number of valid records, taking into account the current mode of error_handling.
- type_inference_only: Infer the type of the source data and return, without ingesting any data. The inferred type is returned in the response.
The JDBC fetch size, which determines how many rows to fetch per round trip.
Executes the statement per each JDBC session before doing actual load.The default value is ”.
Number of splits for reading data per rank. Default will be external_file_reader_num_tasks.The default value is ”.
Number of tasks for reading data per rank. Default will be external_file_reader_num_tasks.
Comma separated list of column names, to set as primary keys, when not specified in the type.The default value is ”.
Comma separated list of column names, to set as shard keys, when not specified in the type.The default value is ”.
Continuously poll the data source to check for new data and load it into the table.The default value is
false.The supported values are:- true
- false
If set to true, truncates the table specified by input parameter table_name prior to loading the data.The default value is
false.The supported values are:- true
- false
Remote SQL query from which data will be sourced.
Name of column to be used for splitting the query into multiple sub-queries using ordering of given column.The default value is ”.
Name of column to be used for splitting the query into multiple sub-queries using the data distribution of given column.The default value is ”.
Column on subscribed remote query result that will increase for new records (e.g., TIMESTAMP).The default value is ”.
Alias name for remote_query_filter_column.The default value is ”.
If set to true, truncate string values that are longer than the column’s type size.The default value is
false.The supported values are:- true
- false
Applies only when upserting (when update_on_existing_pk is true). If set to true (the default), an existing record matched by primary key is modified in place. If set to false, the matched record is updated by deleting it and inserting a replacement (delete and insert), which prevents the change from being reflected in dependent materialized views until they are refreshed.The default value is
true.The supported values are:- true
- false
Specifies the record collision policy for inserting into a table with a primary key. If set to true, any existing table record with primary key values that match those of a 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 record being inserted will remain unchanged, while the new record will be rejected and the error handled as determined by ignore_existing_pk and error_handling. If the specified table does not have a primary key, then this option has no effect.The default value is
false.- true: Upsert new records when primary keys match existing records.
- false: Reject new records when primary keys match existing records.
Output Parameter Description
The Kinetica server embeds the endpoint response inside a standard response structure which contains status information and the actual response to the query. Here is a description of the various fields of the wrapper:String
‘OK’ or ‘ERROR’
String
Empty if success or an error message
String
‘insert_records_from_query_response’ or ‘none’ in case of an error
String
Empty string
JSON or String
This embedded JSON represents the result of the /insert/records/fromquery endpoint:
Empty string in case of an error.
Show data_str
Show data_str
string
Value of input parameter table_name.
string
A JSON string describing the columns of the target table.
string
The user-defined description associated with the target table’s structure.
map of string to arrays of strings
A mapping of each target table column name to an array of column properties associated with that column.
long
Number of records inserted into the target table.
long
Number of records skipped, when not running in abort error handling mode.
long
[Not yet implemented] Number of records updated within the target table.
map of string to strings
Additional information.