Skip to main content

  • ​
    insertRecordsFromFiles

    public InsertRecordsFromFilesResponse insertRecordsFromFiles(InsertRecordsFromFilesRequest request) throws GPUdbException
    Reads from one or more files and inserts the data into a new or existing table. The source data can be located either in KiFS; on the cluster, accessible to the database; or remotely, accessible via a pre-defined external data source.

    For delimited text files, there are two loading schemes: positional and name-based. The name-based loading scheme is enabled when the file has a header present and TEXT_HAS_HEADER is set to TRUE. In this scheme, the source file(s) field names must match the target table’s column names exactly; however, the source file can have more fields than the target table has columns. If ERROR_HANDLING is set to PERMISSIVE, the source file can have fewer fields than the target table has columns. If the name-based loading scheme is being used, names matching the file header’s names may be provided to COLUMNS_TO_LOAD instead of numbers, but ranges are not supported.

    Note: Due to data being loaded in parallel, there is no insertion order guaranteed. For tables with primary keys, in the case of a primary key collision, this means it is indeterminate which record will be inserted first and remain, while the rest of the colliding key records are discarded.

    Returns once all files are processed.

    Parameters:
    request - Request object containing the parameters for the operation.
    Returns:
    Response object containing the results of the operation.
    Throws:
    GPUdbException - if an error occurs during the operation.

  • ​
    insertRecordsFromFiles

    public InsertRecordsFromFilesResponse insertRecordsFromFiles(String tableName, List<String> filepaths, Map<String,Map<String,String>> modifyColumns, Map<String,String> createTableOptions, Map<String,String> options) throws GPUdbException
    Reads from one or more files and inserts the data into a new or existing table. The source data can be located either in KiFS; on the cluster, accessible to the database; or remotely, accessible via a pre-defined external data source.

    For delimited text files, there are two loading schemes: positional and name-based. The name-based loading scheme is enabled when the file has a header present and TEXT_HAS_HEADER is set to TRUE. In this scheme, the source file(s) field names must match the target table’s column names exactly; however, the source file can have more fields than the target table has columns. If ERROR_HANDLING is set to PERMISSIVE, the source file can have fewer fields than the target table has columns. If the name-based loading scheme is being used, names matching the file header’s names may be provided to COLUMNS_TO_LOAD instead of numbers, but ranges are not supported.

    Note: Due to data being loaded in parallel, there is no insertion order guaranteed. For tables with primary keys, in the case of a primary key collision, this means it is indeterminate which record will be inserted first and remain, while the rest of the colliding key records are discarded.

    Returns once all files are processed.

    Parameters:
    tableName - 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 file, and the new table name will have to meet standard table naming criteria.
    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 (|).
    modifyColumns - Not implemented yet. The default value is an empty Map.
    createTableOptions - Options from createTable, allowing the structure of the table to be defined independently of the data source, when creating the target table.The default value is an empty Map.
    options - Optional parameters.
    • 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.
    • 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’.
    • 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.
    • BATCH_SIZE: Number of records to insert per batch when inserting data. The default value is ‘50000’.
    • 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.
    • 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.
    • 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.
    • COMPRESSION_TYPE: Source data compression type. Supported values:
      • NONE: No compression.
      • AUTO: Auto detect compression type.
      • GZIP: gzip file compression.
      • BZIP2: bzip2 file compression.
      The default value is AUTO.
    • DATASOURCE_NAME: Name of an existing external data source from which data file(s) specified in filepaths will be loaded.
    • 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”
    • 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.
      • 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 default value is ABORT.
    • FILE_TYPE: Specifies the type of the file(s) whose records will be inserted. Supported values:
      • AVRO: Avro file format.
      • DELIMITED_TEXT: Delimited text file format; e.g., CSV, TSV, PSV, etc.
      • GDB: Esri/GDB file format.
      • JSON: JSON file format.
      • PARQUET: Apache Parquet file format.
      • SHAPEFILE: ShapeFile file format.
      The default value is DELIMITED_TEXT.
    • FLATTEN_COLUMNS: Specifies how to handle nested columns. Supported values:
      • TRUE: Break up nested columns to multiple columns.
      • FALSE: Treat nested columns as JSON columns instead of flattening.
      The default value is FALSE.
    • GDAL_CONFIGURATION_OPTIONS: Comma separated list of gdal conf options, for the specific requests: key=value.
    • PK_CONFLICT_PREDICATE_HIGHER: The record with higher value for the column resolves the primary-key insert conflict. The default value is ”.
    • PK_CONFLICT_PREDICATE_LOWER: The record with lower value for the column resolves the primary-key insert conflict. The default value is ”.
    • 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:
      • 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.
      The default value is FALSE.
    • 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 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 default value is FULL.
    • KAFKA_CONSUMERS_PER_RANK: Number of Kafka consumer threads per rank (valid range 1-6). The default value is ‘1’.
    • KAFKA_GROUP_ID: The group id to be used when consuming data from a Kafka topic (valid only for Kafka datasource subscriptions).
    • 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 EARLIEST.
    • 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 FALSE.
    • KAFKA_SUBSCRIPTION_CANCEL_AFTER: Sets the Kafka subscription lifespan (in minutes). Expired subscription will be cancelled automatically.
    • KAFKA_TYPE_INFERENCE_FETCH_TIMEOUT: Maximum time to collect Kafka messages before type inferencing on the set of them.
    • LAYER: Geo files layer(s) name(s): comma separated.
    • 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:
      • HEAD: The head node loads all data. All files must be available to the head node.
      • 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.
      • 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 HEAD.
    • LOCAL_TIME_OFFSET: Apply an offset to Avro local timestamp columns.
    • 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).
    • 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.
    • NUM_TASKS_PER_RANK: Number of tasks for reading file per rank. Default will be system configuration parameter, external_file_reader_num_tasks.
    • 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’.
    • PRIMARY_KEYS: Comma separated list of column names to set as primary keys, when not specified in the type.
    • SCHEMA_REGISTRY_CONNECTION_RETRIES: Confluent Schema registry connection timeout (in secs).
    • SCHEMA_REGISTRY_CONNECTION_TIMEOUT: Confluent Schema registry connection timeout (in secs).
    • SCHEMA_REGISTRY_MAX_CONSECUTIVE_CONNECTION_FAILURES: Max records to skip due to SR connection failures, before failing.
    • MAX_CONSECUTIVE_INVALID_SCHEMA_FAILURE: Max records to skip due to schema related errors, before failing.
    • SCHEMA_REGISTRY_SCHEMA_NAME: Name of the Avro schema in the schema registry to use when reading Avro records.
    • SHARD_KEYS: Comma separated list of column names to set as shard keys, when not specified in the type.
    • SKIP_LINES: Skip a number of lines from the beginning of the file.
    • START_OFFSETS: Starting offsets by partition to fetch from kafka. A comma separated list of partition:offset pairs.
    • SUBSCRIBE: Continuously poll the data source to check for new data and load it into the table. Supported values:The default value is FALSE.
    • TABLE_INSERT_MODE: Insertion scheme to use when inserting records from multiple shapefiles. Supported values:
      • SINGLE: Insert all records into a single table.
      • TABLE_PER_FILE: Insert records from each file into a new table corresponding to that file.
      The default value is SINGLE.
    • 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 ’#’.
    • 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 ’,’.
    • 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.
    • TEXT_HAS_HEADER: Indicates whether the source data contains a header row. For DELIMITED_TEXTFILE_TYPE only. Supported values:The default value is TRUE.
    • 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 ’|’.
    • 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’.
    • 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 ’”’.
    • 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 greater than or equal to a minimum size, also set the TEXT_SEARCH_MIN_COLUMN_LENGTH
    • 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.
    • TRIM_SPACE: If set to TRUE, remove leading or trailing space from fields. Supported values:The default value is FALSE.
    • TRUNCATE_STRINGS: If set to TRUE, truncate string values that are longer than the column’s type size. Supported values:The default value is FALSE.
    • TRUNCATE_TABLE: If set to TRUE, truncates the table specified by tableName prior to loading the file(s). Supported values:The default value is FALSE.
    • TYPE_INFERENCE_MAX_RECORDS_READ
    • TYPE_INFERENCE_MODE: Optimize type inferencing for either speed or accuracy. Supported values:
      • ACCURACY: Scans data to get exactly-typed and sized columns for all data scanned.
      • SPEED: Scans data and picks the widest possible column types so that ‘all’ values will fit with minimum data scanned.
      The default value is ACCURACY.
    • 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 TRUE.
    • 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:
      • TRUE: Upsert new records when primary keys match existing records.
      • FALSE: Reject new records when primary keys match existing records.
      The default value is FALSE.
    • 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,1 for the first input column, 2 for the second, etc.). The default value is ”.
    The default value is an empty Map.
    Returns:
    Response object containing the results of the operation.
    Throws:
    GPUdbException - if an error occurs during the operation.