Skip to main content
interface InsertRecordsFromFilesRequest
create_table_options?: Record<string, string>;
filepaths: string[];
modify_columns?: Record<string, Record<string, string>>;
options?: Record<string, string>;
table_name: string;
create_table_options? filepaths modify_columns? options? table_name
create_table_options?: Record<string, string>

Options from create_table, allowing the structure of the table to be defined independently of the data source, when creating the target table

filepaths: string[]

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 (|).

modify_columns?: Record<string, Record<string, string>>

Not implemented yet.

options?: Record<string, string>

Optional parameters.

table_name: 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 file, and the new table name will have to meet standard table naming criteria.