Package com.gpudb.protocol
Class InsertRecordsFromQueryRequest.Options
java.lang.Object
com.gpudb.protocol.InsertRecordsFromQueryRequest.Options
Enclosing class:
A set of string constants for the
InsertRecordsFromQueryRequest parameter options.
Optional parameters.
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final StringStops current insertion and aborts entire operation when an error is encountered.static final StringA positive integer indicating the maximum number of records that can be written to the bad-record-table.static final StringName of a table to which records that were rejected are written.static final StringNumber of records per batch when inserting data.static final StringName of an existing external data source from which table will be loaded.static final StringDoes not load data, but walks through the source data and determines the number of valid records, taking into account the current mode ofERROR_HANDLING.static final StringApplies only when upserting (when update_on_existing_pk is true).static final StringSpecifies how errors should be handled upon insertion.static final StringReject new records when primary keys match existing records.static final StringRun a type inference on the source data (if needed) and ingest.static final StringMalformed records are skipped.static final StringSpecifies 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 whenUPDATE_ON_EXISTING_PKisFALSE).static final StringWhether to do a full load, dry run, or perform a type inference on the source data.static final StringThe JDBC fetch size, which determines how many rows to fetch per round trip.static final StringExecutes the statement per each JDBC session before doing actual load.static final StringNumber of splits for reading data per rank.static final StringNumber of tasks for reading data per rank.static final StringRecords with missing columns are populated with nulls if possible; otherwise, the malformed records are skipped.static final StringComma separated list of column names, to set as primary keys, when not specified in the type.static final StringRemote SQL query from which data will be sourced.static final StringName of column to be used for splitting the query into multiple sub-queries using the data distribution of given column.static final StringColumn on subscribed remote query result that will increase for new records (e.g., TIMESTAMP).static final StringName of column to be used for splitting the query into multiple sub-queries using ordering of given column.static final StringAlias name forREMOTE_QUERY_FILTER_COLUMN.static final StringComma separated list of column names, to set as shard keys, when not specified in the type.static final StringContinuously poll the data source to check for new data and load it into the table.static final StringUpsert new records when primary keys match existing records.static final StringIf set toTRUE, truncate string values that are longer than the column’s type size.static final Stringstatic final StringInfer the type of the source data and return, without ingesting any data.static final StringSpecifies the record collision policy for inserting into a table with a primary key.
Field Details
BAD_RECORD_TABLE_NAME
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.See Also:ERROR_HANDLING
Specifies how errors should be handled upon insertion. Supported values:PERMISSIVE: Records with missing columns are populated with nulls if possible; otherwise, the malformed records are skipped.IGNORE_BAD_RECORDS: Malformed records are skipped.ABORT: Stops current insertion and aborts entire operation when an error is encountered. Primary key collisions are considered abortable errors in this mode.
ABORT.See Also:IGNORE_EXISTING_PK
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 whenUPDATE_ON_EXISTING_PKisFALSE). If set toTRUE, 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. IfFALSE, the rejection of any record for having primary key values matching an existing record will result in an error being reported, as determined byERROR_HANDLING. If the specified table does not have a primary key or if upsert mode is in effect (UPDATE_ON_EXISTING_PKisTRUE), then this option has no effect. Supported values: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.
FALSE.See Also:INGESTION_MODE
Whether to do a full load, dry run, or perform a type inference on the source data. Supported values: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 ofERROR_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.
FULL.See Also: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 ofERROR_HANDLING.See Also:REMOTE_QUERY_PARTITION_COLUMN
Alias name forREMOTE_QUERY_FILTER_COLUMN. The default value is ”.See Also:ENABLE_INPLACE_UPDATES
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. Supported values:The default value isTRUE.See Also:UPDATE_ON_EXISTING_PK
Specifies the record collision policy for inserting into a table with a primary key. If set toTRUE, 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 toFALSE, 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 byIGNORE_EXISTING_PKandERROR_HANDLING. If the specified table does not have a primary key, then this option has no effect. Supported values:TRUE: Upsert new records when primary keys match existing records.FALSE: Reject new records when primary keys match existing records.
FALSE.See Also: