| [in] | filepaths_ | A list of file paths from which data will be sourced; For paths in KiFS, use the uri prefix of kifs:// followed by the path to a file or directory. File matching by prefix is supported, e.g. kifs://dir/file would match dir/file_1 and dir/file_2. When prefix matching is used, the path must start with a full, valid KiFS directory name. If an external data source is specified in datasource_name, these file paths must resolve to accessible files at that data source location. Prefix matching is supported. If the data source is hdfs, prefixes must be aligned with directories, i.e. partial file names will not match. If no data source is specified, the files are assumed to be local to the database and must all be accessible to the gpudb user, residing on the path (or relative to the path) specified by the external files directory in the Kinetica configuration file. Wildcards (*) can be used to specify a group of files. Prefix matching is supported, the prefixes must be aligned with directories. If the first path ends in .tsv, the text delimiter will be defaulted to a tab character. If the first path ends in .psv, the text delimiter will be defaulted to a pipe character (|). |
| [in] | options_ | Optional parameters.
-
insert_records_from_files_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.
-
insert_records_from_files_bad_record_table_limit: A positive integer indicating the maximum number of records that can be written to the bad-record-table. The default value is '10000'.
-
insert_records_from_files_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_files_batch_size: Number of records to insert per batch when inserting data. The default value is '50000'.
-
insert_records_from_files_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, & 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_files_columns_to_load: Specifies a comma-delimited list of columns from the source data to load. If more than one file is being loaded, this list applies to all files. Column numbers can be specified discretely or as a range. For example, a value of '5,7,1..3' will insert values from the fifth column in the source data into the first column in the target table, from the seventh column in the source data into the second column in the target table, and from the first through third columns in the source data into the third through fifth columns in the target table. If the source data contains a header, column names matching the file header names may be provided instead of column numbers. If the target table doesn't exist, the table will be created with the columns in this order. If the target table does exist with columns in a different order than the source data, this list can be used to match the order of the target table. For example, a value of 'C, B, A' will create a three column table with column C, followed by column B, followed by column A; or will insert those fields in that order into a table created with columns in that order. If the target table exists, the column names must match the source data field names for a name-mapping to be successful. Mutually exclusive with columns_to_skip.
-
insert_records_from_files_columns_to_skip: Specifies a comma-delimited list of columns from the source data to skip. Mutually exclusive with columns_to_load.
-
insert_records_from_files_compression_type: Source data compression type. Supported values:
The default value is insert_records_from_files_auto.
-
insert_records_from_files_datasource_name: Name of an existing external data source from which data file(s) specified in filepaths_ will be loaded
-
insert_records_from_files_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, & datetime. This default column-property-bound format can be overridden by specifying a column property & 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_files_error_handling: Specifies how errors should be handled upon insertion. Supported values:
The default value is insert_records_from_files_abort.
-
insert_records_from_files_file_type: Specifies the type of the file(s) whose records will be inserted. Supported values:
The default value is insert_records_from_files_delimited_text.
-
insert_records_from_files_flatten_columns: Specifies how to handle nested columns. Supported values:
The default value is insert_records_from_files_false.
-
insert_records_from_files_gdal_configuration_options: Comma separated list of gdal conf options, for the specific requets: key=value
-
insert_records_from_files_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_files_false.
-
insert_records_from_files_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_files_full.
-
insert_records_from_files_kafka_consumers_per_rank: Number of Kafka consumer threads per rank (valid range 1-6). The default value is '1'.
-
insert_records_from_files_kafka_group_id: The group id to be used when consuming data from a Kafka topic (valid only for Kafka datasource subscriptions).
-
insert_records_from_files_kafka_offset_reset_policy: Policy to determine whether the Kafka data consumption starts either at earliest offset or latest offset. Supported values:
The default value is insert_records_from_files_earliest.
-
insert_records_from_files_kafka_optimistic_ingest: Enable optimistic ingestion where Kafka topic offsets and table data are committed independently to achieve parallelism. Supported values:
The default value is insert_records_from_files_false.
-
insert_records_from_files_kafka_subscription_cancel_after: Sets the Kafka subscription lifespan (in minutes). Expired subscription will be cancelled automatically.
-
insert_records_from_files_kafka_type_inference_fetch_timeout: Maximum time to collect Kafka messages before type inferencing on the set of them.
-
insert_records_from_files_layer: Geo files layer(s) name(s): comma separated.
-
insert_records_from_files_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_files_head: The head node loads all data. All files must be available to the head node.
-
insert_records_from_files_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_files_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_files_head.
-
insert_records_from_files_local_time_offset: Apply an offset to Avro local timestamp columns.
-
insert_records_from_files_max_records_to_load: Limit the number of records to load in this request: if this number is larger than batch_size, then the number of records loaded will be limited to the next whole number of batch_size (per working thread).
-
insert_records_from_files_num_tasks_per_rank: Number of tasks for reading file per rank. Default will be system configuration parameter, external_file_reader_num_tasks.
-
insert_records_from_files_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. The default value is '0'.
-
insert_records_from_files_primary_keys: Comma separated list of column names to set as primary keys, when not specified in the type.
-
insert_records_from_files_schema_registry_schema_name: Name of the Avro schema in the schema registry to use when reading Avro records.
-
insert_records_from_files_shard_keys: Comma separated list of column names to set as shard keys, when not specified in the type.
-
insert_records_from_files_skip_lines: Skip number of lines from begining of file.
-
insert_records_from_files_start_offsets: Starting offsets by partition to fetch from kafka. A comma separated list of partition:offset pairs.
-
insert_records_from_files_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_files_false.
-
insert_records_from_files_table_insert_mode: Insertion scheme to use when inserting records from multiple shapefiles. Supported values:
The default value is insert_records_from_files_single.
-
insert_records_from_files_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_files_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_files_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, & 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_files_text_has_header: Indicates whether the source data contains a header row. For delimited_text file_type only. Supported values:
The default value is insert_records_from_files_true.
-
insert_records_from_files_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_files_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_files_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_files_text_search_columns: Add 'text_search' property to internally inferenced string columns. Comma seperated list of column names or '*' for all columns. To add 'text_search' property only to string columns greater than or equal to a minimum size, also set the text_search_min_column_length
-
insert_records_from_files_text_search_min_column_length: Set the minimum column size for strings to apply the 'text_search' property to. Used only when text_search_columns has a value.
-
insert_records_from_files_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_files_false.
-
insert_records_from_files_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_files_false.
-
insert_records_from_files_type_inference_mode: Optimize type inferencing for either speed or accuracy. Supported values:
The default value is insert_records_from_files_accuracy.
-
insert_records_from_files_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 & 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_files_false.
The default value is an empty map. |
1.8.15