| [in] | options | Optional parameters.- insert_records_from_payload_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).
- insert_records_from_payload_bad_record_table_limit: A positive integer indicating the maximum number of records that can be written to the bad-record-table. Default value is 10000.
- insert_records_from_payload_bad_record_table_limit_per_input: For subscriptions: A positive integer indicating the maximum number of records that can be written to the bad-record-table per file/payload. Default value will be ‘bad_record_table_limit’ and total size of the table per rank is limited to ‘bad_record_table_limit’.
- insert_records_from_payload_batch_size: Internal tuning parameter–number of records per batch when inserting data.
- insert_records_from_payload_column_formats: For each target column specified, applies the column-property-bound format to the source data loaded into that column. Each column format will contain a mapping of one or more of its column properties to an appropriate format for each property. Currently supported column properties include date, time, and datetime. The parameter value must be formatted as a JSON string of maps of column names to maps of column properties to their corresponding column formats, e.g., ’ “order_date” : “date” : “%Y.%m.%d” , “order_time” : “time” : “%H:%M:%S” ’. See default_column_formats for valid format syntax.
- insert_records_from_payload_columns_to_load: Specifies a comma-delimited list of source-data columns that supply the target table’s columns. If more than one file is being loaded, this list applies to all files. Mutually exclusive with columns_to_skip. This list is a positional mapping onto the target table rather than a filter: the i-th entry identifies the source column that feeds the i-th column of the target table. Entries may be column numbers, column names, or empty. Column numbers are 1-based, specified discretely or as a range. For example, ‘5,7,,1..3’ inserts the fifth source column into the first target column, the seventh into the second, null into the third, and the first through third into the fourth through sixth. A range may descend (‘3..1’) to reverse that group’s order. Zero is not a valid column number. Numbers are supported only for delimited-text and Avro sources. Column names are strings, matching the source-data field names – either the file’s header names or the names supplied by name_columns_from_file. Requires that the source data have column names. Names are matched case-sensitively, and a name not present in the source will fail. An empty entry, acting as a placeholder meaning that no source column feeds the corresponding target column. Numbers and names cannot be mixed: a single non-numeric entry causes the entire list to be interpreted as names. If the target table does not exist, it is created with these columns in this order, and the list may name any subset of the source columns. If the target table already exists, the number of entries must equal the target table’s column count. Use empty entries to pad the list to the target’s width. Because the mapping is positional, this option can also reorder source columns into the target’s column order – for example ‘C, B, A’ for a target table whose columns are C, B, A. Note: specifying columns_to_load disables server-side population of target columns that no source column feeds. Such columns receive NULL instead of their default value, ‘init_with_now’, or ‘init_with_uuid’ value; if the column is non-nullable, the record is rejected. To have unfed target columns take their defaults, omit columns_to_load and rely on name-based matching, optionally with columns_to_skip.
- insert_records_from_payload_columns_to_skip: Specifies a comma-delimited list of source-data columns to exclude from the load. If more than one file is being loaded, this list applies to all files. Mutually exclusive with columns_to_load. Entries may be column names matching the source-data field names (the file’s header names, or the names supplied by name_columns_from_file, matched case-sensitively), or 1-based column numbers. Numbers are supported only for delimited-text sources. Name-based entries require the source data to have column names. Unlike columns_to_load, this option does not change how the remaining source columns are matched to the target table. Matching remains by name and is case-insensitive, so the order and number of source columns need not correspond to the target table’s columns. Excluding a source column that corresponds to a target table column causes that target column to be populated from its default value, ‘init_with_*’ property, or null. This makes columns_to_skip the means of preferring a target column’s default over a value present in the source data. Source columns that don’t correspond to any target table column need not be listed; they are ignored. If the target table does not exist, the non-excluded source columns define the new table’s columns, in source-data order. If the source data has no column names (no header row and no name_columns_from_file) and this option is given as numbers, the remaining source columns are matched to target columns by position; the source column count must then equal the target table’s column count plus the number of columns skipped.
- insert_records_from_payload_compression_type: Payload compression type. Supported values:The default value is insert_records_from_payload_auto.
- insert_records_from_payload_default_column_formats: Specifies the default format to be applied to source data loaded into columns with the corresponding column property. Currently supported column properties include date, time, and datetime. This default column-property-bound format can be overridden by specifying a column property and format for a given target column in column_formats. For each specified annotation, the format will apply to all columns with that annotation unless a custom column_formats for that annotation is specified. The parameter value must be formatted as a JSON string that is a map of column properties to their respective column formats, e.g., ’ “date” : “%Y.%m.%d”, “time” : “%H:%M:%S” ’. Column formats are specified as a string of control characters and plain text. The supported control characters are ‘Y’, ‘m’, ‘d’, ‘H’, ‘M’, ‘S’, and ‘s’, which follow the Linux ‘strptime()’ specification, as well as ‘s’, which specifies seconds and fractional seconds (though the fractional component will be truncated past milliseconds). Formats for the ‘date’ annotation must include the ‘Y’, ‘m’, and ‘d’ control characters. Formats for the ‘time’ annotation must include the ‘H’, ‘M’, and either ‘S’ or ‘s’ (but not both) control characters. Formats for the ‘datetime’ annotation meet both the ‘date’ and ‘time’ control character requirements. For example, ‘“datetime” : “%m/%d/%Y %H:%M:%S” ’ would be used to interpret text as “05/04/2000 12:12:11”
- insert_records_from_payload_error_handling: Specifies how errors should be handled upon insertion. Supported values:The default value is insert_records_from_payload_abort.
- insert_records_from_payload_file_type: Specifies the type of the file(s) whose records will be inserted. Supported values:The default value is insert_records_from_payload_delimited_text.
- insert_records_from_payload_flatten_columns: Specifies how to handle nested columns. Supported values:The default value is insert_records_from_payload_false.
- insert_records_from_payload_gdal_configuration_options: Comma separated list of gdal conf options, for the specific requests: key=value. The default value is ”.
- insert_records_from_payload_pk_conflict_predicate_higher: The record with higher value for the column resolves the primary-key insert conflict. The default value is ”.
- insert_records_from_payload_pk_conflict_predicate_lower: The record with lower value for the column resolves the primary-key insert conflict. The default value is ”.
- insert_records_from_payload_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 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. Supported values:The default value is insert_records_from_payload_false.
- insert_records_from_payload_ingestion_mode: Whether to do a full load, dry run, or perform a type inference on the source data. Supported values:The default value is insert_records_from_payload_full.
- insert_records_from_payload_layer: Geo files layer(s) name(s): comma separated. The default value is ”.
- insert_records_from_payload_loading_mode: Scheme for distributing the extraction and loading of data from the source data file(s). This option applies only when loading files that are local to the database. Supported values:
- insert_records_from_payload_head: The head node loads all data. All files must be available to the head node.
- insert_records_from_payload_distributed_shared: The head node coordinates loading data by worker processes across all nodes from shared files available to all workers. NOTE: Instead of existing on a shared source, the files can be duplicated on a source local to each host to improve performance, though the files must appear as the same data set from the perspective of all hosts performing the load.
- insert_records_from_payload_distributed_local: A single worker process on each node loads all files that are available to it. This option works best when each worker loads files from its own file system, to maximize performance. In order to avoid data duplication, either each worker performing the load needs to have visibility to a set of files unique to it (no file is visible to more than one node) or the target table needs to have a primary key (which will allow the worker to automatically deduplicate data). NOTE: If the target table doesn’t exist, the table structure will be determined by the head node. If the head node has no files local to it, it will be unable to determine the structure and the request will fail. If the head node is configured to have no worker processes, no data strictly accessible to the head node will be loaded.
The default value is insert_records_from_payload_head. - insert_records_from_payload_local_time_offset: For Avro local timestamp columns.
- insert_records_from_payload_max_records_to_load: Limit the number of records to load in this request: If this number is larger than a batch_size, then the number of records loaded will be limited to the next whole number of batch_size (per working thread). The default value is ”.
- insert_records_from_payload_name_columns_from_file: Specifies a comma-delimited list of column names to be used as the source-data column names. Supported for delimited-text sources only. The i-th name in this list applies to the i-th column in the file. If the file has a header row (i.e., text_has_header is true), these names override the file’s header names. If the file has no header row, these names become the source-data column names. Naming the source columns enables name-based matching against the target table’s columns, and permits name-based columns_to_load / columns_to_skip, which otherwise require a header row. Note: for a source with no header row, supplying this option changes how source columns are matched to target columns – from positional matching to matching by name. Target columns with no matching source column are then populated from their defaults or null rather than being filled positionally. The list is not validated against the file’s actual column count. If it is shorter, the trailing source columns are left unnamed.
- insert_records_from_payload_num_tasks_per_rank: Number of tasks for reading file per rank. Default will be external_file_reader_num_tasks.
- insert_records_from_payload_poll_interval: If true, the number of seconds between attempts to load external files into the table. If zero, polling will be continuous as long as data is found. If no data is found, the interval will steadily increase to a maximum of 60 seconds.
- insert_records_from_payload_primary_keys: Comma separated list of column names, to set as primary keys, when not specified in the type. The default value is ”.
- insert_records_from_payload_schema_registry_connection_retries: Confluent Schema registry connection timeout (in secs).
- insert_records_from_payload_schema_registry_connection_timeout: Confluent Schema registry connection timeout (in secs).
- insert_records_from_payload_schema_registry_max_consecutive_connection_failures: Max records to skip due to SR connection failures, before failing.
- insert_records_from_payload_max_consecutive_invalid_schema_failure: Max records to skip due to schema related errors, before failing.
- insert_records_from_payload_schema_registry_schema_name: Name of the Avro schema in the schema registry to use when reading Avro records.
- insert_records_from_payload_shard_keys: Comma separated list of column names, to set as shard keys, when not specified in the type. The default value is ”.
- insert_records_from_payload_skip_lines: Skip a number of lines from the beginning of the file.
- insert_records_from_payload_subscribe: Continuously poll the data source to check for new data and load it into the table. Supported values:The default value is insert_records_from_payload_false.
- insert_records_from_payload_table_insert_mode: When inserting records from multiple files: if table_per_file, then insert from each file into a new table. Currently supported only for shapefiles. Supported values:The default value is insert_records_from_payload_single.
- insert_records_from_payload_text_comment_string: Specifies the character string that should be interpreted as a comment line prefix in the source data. All lines in the data starting with the provided string are ignored. For delimited_text file_type only. The default value is ’#’.
- insert_records_from_payload_text_delimiter: Specifies the character delimiting field values in the source data and field names in the header (if present). For delimited_text file_type only. The default value is ’,’.
- insert_records_from_payload_text_escape_character: Specifies the character that is used to escape other characters in the source data. An ‘a’, ‘b’, ‘f’, ‘n’, ‘r’, ‘t’, or ‘v’ preceded by an escape character will be interpreted as the ASCII bell, backspace, form feed, line feed, carriage return, horizontal tab, and vertical tab, respectively. For example, the escape character followed by an ‘n’ will be interpreted as a newline within a field value. The escape character can also be used to escape the quoting character, and will be treated as an escape character whether it is within a quoted field value or not. For delimited_text file_type only.
- insert_records_from_payload_text_has_header: Indicates whether the source data contains a header row. For delimited_textfile_type only. Supported values:The default value is insert_records_from_payload_true.
- insert_records_from_payload_text_header_property_delimiter: Specifies the delimiter for column properties in the header row (if present). Cannot be set to same value as text_delimiter. For delimited_text file_type only. The default value is ’|’.
- insert_records_from_payload_text_null_string: Specifies the character string that should be interpreted as a null value in the source data. For delimited_text file_type only. The default value is ‘\N’.
- insert_records_from_payload_text_quote_character: Specifies the character that should be interpreted as a field value quoting character in the source data. The character must appear at beginning and end of field value to take effect. Delimiters within quoted fields are treated as literals and not delimiters. Within a quoted field, two consecutive quote characters will be interpreted as a single literal quote character, effectively escaping it. To not have a quote character, specify an empty string. For delimited_text file_type only. The default value is ’”’.
- insert_records_from_payload_text_search_columns: Add ‘text_search’ property to internally inferenced string columns. Comma separated list of column names or ’*’ for all columns. To add text_search property only to string columns of minimum size, set also the option ‘text_search_min_column_length’.
- insert_records_from_payload_text_search_min_column_length: Set minimum column size. Used only when ‘text_search_columns’ has a value.
- insert_records_from_payload_trim_space: If set to true, remove leading or trailing space from fields. Supported values:The default value is insert_records_from_payload_false.
- insert_records_from_payload_truncate_strings: If set to true, truncate string values that are longer than the column’s type size. Supported values:The default value is insert_records_from_payload_false.
- insert_records_from_payload_truncate_table: If set to true, truncates the table specified by tableName prior to loading the file(s). Supported values:The default value is insert_records_from_payload_false.
- insert_records_from_payload_type_inference_max_records_read: The default value is ”.
- insert_records_from_payload_type_inference_mode: Optimize type inference mode. Supported values:The default value is insert_records_from_payload_accuracy.
- insert_records_from_payload_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 is insert_records_from_payload_true.
- insert_records_from_payload_update_on_existing_pk: 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. Supported values:The default value is insert_records_from_payload_false.
- insert_records_from_payload_transformations: Comma-separated expressions, one per target table column. Each expression is evaluated per record. Empty entries (two consecutive commas) mean no transformation for that column – the value is resolved from the input record, table default, NULL, or an error. Expressions may reference input columns by name or by position (1forthefirstinputcolumn,2 for the second, etc.). The default value is ”.
The default value is an empty map. |
