Skip to main content
Kinetica can load either internal or external data into a table, using a LOAD INTO statement.
LOAD INTO Syntax
For contextualized examples, see Examples. For copy/paste examples, see Loading Data. For an overview of loading data into Kinetica, see Data Loading Concepts.
The data can be sourced through either of the following:
  • local files uploaded into KiFS
  • a data source configured to allow access to:
    • remote files on Azure, GCS, HDFS, or S3
    • remote messages on a Kafka topic
    • a remote database queryable via JDBC
A LOAD INTO that uses a data source can perform a one-time load upon creation and optionally subscribe for updates on an interval, depending on the data source provider: See Manage Subscription for pausing, resuming, & canceling subscriptions on the target table. The use of LOAD INTO with ring resiliency has additional considerations.

Parameters

DATA

Optional keyword for compatibility

<schema name>

Name of the schema containing the table into which data will be loaded

<table name>

Name of the table into which data will be loaded

FROM REMOTE QUERY

Source data specification clause, where <source data query> is a SQL query selecting the data which will be loaded.
This clause is mutually exclusive with the FROM FILE PATHS clause, and is only applicable to JDBC data sources.
The query should meet the following criteria:
  • Any column expression used is given a column alias.
  • The first column is not a WKT or unlimited length VARCHAR type.
  • The columns and expressions queried should match the order, number, & type of the columns in the target table. If the target table doesn’t exist, it will be created using the names and data types of the queried columns in the order in which they appear in the query.
Any query resulting in more than 10,000 records will be distributed and loaded in parallel (unless directed otherwise) using the following rule sequence:
  1. If REMOTE_QUERY_NO_SPLIT is TRUE, the query will not be distributed.
  2. If a valid REMOTE_QUERY_PARTITION_COLUMN is specified, the query will be distributed by partitioning on the given column’s values
  3. If a valid REMOTE_QUERY_ORDER_BY is specified, the query will be distributed by ordering the data accordingly and then partitioning into sequential blocks from the first record
  4. If a non-null numeric/date/time column exists, the query will be distributed by partitioning on the first such column’s values
  5. The query will be distributed by sorting the data on the first column and then partitioning into sequential blocks from the first record
Type inferencing is limited by the available JDBC types. To take advantage of Kinetica-specific types and properties, create the target table manually before loading data.

FROM FILE PATHS

Source file specification clause, where <file paths> is a comma-separated list of single-quoted file paths from which data will be loaded; all files specified are presumed to have the same format and data types.
This clause is mutually exclusive with the FROM REMOTE QUERY clause, and is not applicable to JDBC data sources.
The form of a file path is dependent on the source referenced:
  • Data Source: If a data source is specified in the load options, these file paths must resolve to accessible files at that data source location. A “path prefix” can be specified instead, which will cause all files whose path begins with the given prefix to be included. For example, a “path prefix” of /data/ge for <file paths> would match all of the following:
    • /data/geo.csv
    • /data/geo/flights.csv
    • /data/geo/2021/airline.csv
    If using an HDFS data source, the “path prefix” must be the name of an HDFS directory.
  • KiFS: The path must resolve to an accessible file path within KiFS. A “path prefix” can be specified instead, which will cause all files whose path begins with the given prefix to be included. For example, a “path prefix” of kifs://data/ge would match all of the following files under the KiFS data directory:
    • kifs://data/geo.csv
    • kifs://data/geo/flights.csv
    • kifs://data/geo/2021/airline.csv
  • Kinetica Cluster: The paths are OS-level paths under the Kinetica configuration file’s external files directory that are accessible to the gpudb user and either:
    • accessible to all nodes in the Kinetica cluster
    • mirrored across each node in the Kinetica cluster
    A “path prefix” that references a directory on the cluster file system can be specified, which will cause all files contained within that directory and its subdirectories to be included. Wildcards can also be used to specify a group of files. Directories of shapefiles are loaded as a single data set, rather than being traversed recursively. For example, if external_files_directory is set to /opt/gpudb/data, the following <file paths> specifications will refer to these corresponding files:
File PathReference
/opt/gpudb/data/products.csvFile /opt/gpudb/data/products.csv
archive/products.csvFile /opt/gpudb/data/archive/products.csv
archive/*.csvAll files under /opt/gpudb/data/archive with a csv extension
archiveAll files under /opt/gpudb/data/archive and its subdirectories
/opt/gpudb/products.csvError, as absolute path /opt/gpudb does not contain external files directory /opt/gpudb/data as part of the path

FORMAT

Optional indicator of source file type, for file-based data sources; will be inferred from the file extension if not given.Supported formats include:
KeywordDescription
[DELIMITED] TEXTAny text-based, delimited field data file (CSV, PSV, TSV, etc.); a comma-delimited list of options can be given to specify the way in which the data file(s) should be parsed, including the delimiter used, whether headers are present, etc. Records spanning multiple lines are not supported. See Delimited Text Options for the complete list of <delimited text options>.
AVROApache Avro data file
JSONEither a JSON or GeoJSON data file See JSON/GeoJSON Limitations for the supported data types.
PARQUETApache Parquet data file See Parquet Limitations for the supported data types.
SHAPEFILEArcGIS shapefile

WITH OPTIONS

Optional indicator that a comma-delimited list of connection & global option/value assignments will follow.See Load Options for the complete list of options.

<table property clause>

Optional comma-separated list of table properties, from a subset of those available, to the table to load into, if it is created by this call.

Delimited Text Options

The following options can be specified when loading data from delimited text files. When reading from multiple files, options specific to the source file will be applied to each file being read.

COMMENT = '<string>'

Treat lines in the source file(s) that begin with string as comments and skip.The default comment marker is #.

DELIMITER = '<char>'

Use char as the source file field delimiter.The default delimiter is a comma, unless a source file has one of these extensions:
  • .psv - will cause | to be the delimiter
  • .tsv - will cause the tab character to be the delimiter
See Delimited Text Option Characters for allowed characters.

ESCAPE = '<char>'

Use char as the source file data escape character. The escape character preceding any other character, in the source data, will be converted into that other character, except in the following special cases:
Source Data StringRepresentation when Loaded into the Database
<char>aASCII bell
<char>bASCII backspace
<char>fASCII form feed
<char>nASCII line feed
<char>rASCII carriage return
<char>tASCII horizontal tab
<char>vASCII vertical tab
For instance, if the escape character is \, a \t encountered in the data will be converted to a tab character when stored in the database.The escape character can 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.There is no default escape character.

HEADER DELIMITER = '<char>'

Use char as the source file header field name/property delimiter, when the source file header contains both names and properties. This is largely specific to the Kinetica export to delimited text feature, which will, within each field’s header, contain the field name and any associated properties, delimited by the pipe | character.An example Kinetica header in a CSV file:
The default is the | (pipe) character. See Delimited Text Option Characters for allowed characters.
The DELIMITER character will still be used to separate field name/property sets from each other in the header row

INCLUDES HEADER = <TRUE|FALSE>

Declare that the source file(s) will or will not have a header.The default is TRUE.

NULL = '<string>'

Treat string as the indicator of a null source field value.The default is \N.

QUOTE = '<char>'

Use char as the source file data quoting character, for enclosing field values. Usually used to wrap field values that contain embedded delimiter characters, though any field may be enclosed in quote characters (for clarity, for instance). The quote character must appear as the first and last character of a field value in order to be interpreted as quoting the value. Within a quoted value, embedded quote characters may be escaped by preceding them with another quote character or the escape character specified by ESCAPE, if given.The default is the " (double-quote) character. See Delimited Text Option Characters for allowed characters.

Delimited Text Option Characters

For DELIMITER, HEADER DELIMITER, ESCAPE, & QUOTE, any single character can be used, or any one of the following escaped characters: For instance, if two single quotes ('') are specified for a QUOTE character, the parser will interpret single quotes in the source file as quoting characters; specifying \t for DELIMITER will cause the parser to interpret ASCII horizontal tab characters in the source file as delimiter characters.

Load Options

The following options can be specified to modify the way data is loaded (or not loaded) into the target table.

AVRO_SCHEMA

String containing the Avro schema to use when reading Avro data that includes only records—i.e. data that does not embed its own schema.
Supplying this option implies the source data is schemaless.

AVRO_SCHEMA_NO_INFERENCE

Whether to derive the target table’s column types solely from the Avro schema, when one is available, instead of inferring them from the data.

BAD RECORD TABLE

Name of the table containing records that failed to be loaded into the target table. This bad record table will include the following columns:
Column NameSource Data Format Codes
line_numberNumber of the line in the input file containing the failed record
char_numberPosition of character within a failed record that is assessed as the beginning of the portion of the record that failed to process
filenameName of file that contained the failed record
line_rejectedText of the record that failed to process
error_msgError message associated with the record processing failure
This option is not applicable for an ON ERROR mode of ABORT. In that mode, processing stops at the first error and that error is returned to the user.

BATCH SIZE

Use an ingest batch size of the given number of records.The default batch size is 50,000.

COLUMN FORMATS

Use the given type-specific formatting for the given column when parsing source data being loaded into that column. This should be a map of column names to format specifications, where each format specification is map of column type to data format, all formatted as a JSON string.Supported column types include:
Apply the given date format to the given column.Common date format codes follow. For the complete list, see Date/Time Conversion Codes.
CodeDescription
YYYY4-digit year
MM2-digit month, where January is 01
DD2-digit day of the month, where the 1st of each month is 01
For example, to load dates of the format 2010.10.30 into date column d and times of the 24-hour format 18:36:54.789 into time column t:
This option is not available for data sources configured for JDBC.

DATA SOURCE

Load data from the given data source. Data source connect privilege is required when loading from a data source.

DEFAULT COLUMN FORMATS

Use the given formats for source data being loaded into target table columns with the corresponding column types. This should be a map of target column type to source format for data being loaded into columns of that type, formatted as a JSON string.Supported column properties and source data formats are the same as those listed in the description of the COLUMN FORMATS option.For example, to make the default format for loading source data dates like 2010.10.30 and 24-hour times like 18:36:54.789:
This option is not available for data sources configured for JDBC.

FIELDS IGNORED BY

Choose a comma-separated list of fields from the source file(s) to exclude from the load. Fields can be identified by either NAME or POSITION. If ignoring by NAME, the specified names must match the source file field names exactly; source fields can be named with FIELDS MAPPED AS COLUMN.
  • Identifying by Name:
  • Identifying by Position:
  • If the target table has no column definition, the non-ignored source fields define its columns, in source file order.
  • If the target table has a column definition, the non-ignored source fields are matched to its columns by name, case-insensitively; their order & number need not correspond to those columns, and any source field matching none of them is ignored as well.
  • If the target table has a column definition and the source data has no field names (no header row and no FIELDS MAPPED AS COLUMN), the non-ignored source fields are matched to its columns by position instead, and the source field count must equal the column count plus the number of fields ignored.
  • Ignoring a source field that corresponds to a target table column causes that column to be populated with its default value, init_with_* value, or null. This makes FIELDS IGNORED BY the means of preferring a column default over a value present in the source data.
  • Ignoring fields by POSITION is only supported for delimited text files.

FIELDS MAPPED AS COLUMN

Choose a comma-separated list of names to assign to the source file fields, in order; the i-th name is assigned to the i-th field of the file. Only supported for delimited text files.
Naming the source fields allows them to be matched to the target table columns by name, and allows FIELDS MAPPED BY NAME & FIELDS IGNORED BY NAME, which otherwise require the source file to have a header row.
  • If the source file has a header row, these names override the header names; if it has no header row, these names become the source field names.
  • For a source file with no header row, applying this option switches the matching of source fields to target table columns from positional to by-name. Any column with no matching source field is then populated with its default value or null, rather than being filled positionally.
  • The list is not validated against the number of fields in the file; if it is shorter, the trailing source fields are left unnamed.

FIELDS MAPPED BY

Choose a comma-separated list of source file fields to load, in the order of the target table columns into which they will be loaded; the i-th entry identifies the source field that feeds the i-th column. This is a positional mapping onto the target table rather than a filter, so it can also be used to reorder source fields. Fields can be identified by either NAME or POSITION, but the two cannot be mixed—a single non-numeric entry causes the entire list to be read as names.
  • Identifying by Name - the source file fields ID, Name, & Stock are loaded into the first three columns, respectively:
  • Identifying by Position - the 1st, 2nd, & 5th source file fields are loaded into the first three columns, respectively:
  • Positions are 1-based & may be given as ranges, which may descend to reverse the order of that group, while an empty entry is a placeholder that feeds no source field to the corresponding column. Here, the 5th source field is loaded into the first column, the 7th into the second, nothing into the third, and the 1st through 3rd into the fourth through sixth:
  • If the target table has no column definition, it is created with the identified fields as its columns, in the order given; the list may identify any subset of the source fields.
  • If the target table has a column definition, the number of entries must equal its column count; empty entries can be used to pad the list to that width.
  • Applying this option disables the population of target table columns that no source field feeds; such columns are assigned null instead of their default value, init_with_now, or init_with_uuid value, and the record is rejected if the column is not nullable. To have unfed columns take their defaults, use FIELDS IGNORED BY instead.
  • If mapping by NAME, the specified names must match the source file field names exactly; source fields can be named with FIELDS MAPPED AS COLUMN.
  • Mapping fields by POSITION is only supported for delimited text & Avro files.

FLATTEN_COLUMNS

Specify the policy for handling nested columns within JSON data.The default is FALSE.
ValueDescription
TRUEBreak up nested columns into multiple columns.
FALSETreat nested columns as JSON columns instead of flattening.

IGNORE_EXISTING_PK

Specify the error suppression policy for inserting duplicate primary key values into a table with a primary key. If the specified table does not have a primary key or the UPDATE_ON_EXISTING_PK option is used, then this options has no effect.The default is FALSE.
ValueDescription
TRUESuppress errors when inserted records and existing records’ PKs match.
FALSEReturn errors when inserted records and existing records’ PKs match.

INGESTION MODE

Whether to do a full ingest of the data or perform a dry run or type inference instead.The default mode is FULL.
ValueDescription
DRY RUNNo data will be inserted, but the file will be read with the applied ON ERROR mode and the number of valid records that would normally be inserted is returned.
FULLData is fully ingested according to the active ON ERROR mode.
TYPE INFERENCEInfer the type of the source data and return, without ingesting any data. The inferred type is returned in the response, as the output of a SHOW TABLE command.

JDBC_FETCH_SIZE

Retrieve this many records at a time from the remote database. Lowering this number will help tables with large record sizes fit into available memory during ingest.The default is 50,000.
This option is only available for data sources configured for JDBC.

JDBC_SESSION_INIT_STATEMENT

Run the single given statement before the initial load is performed. Also run it before each subsequent reload, if SUBSCRIBE is TRUE.For example, to set the time zone to UTC before running each load, use:
This option is only available for data sources configured for JDBC.

KAFKA_CONSUMERS_PER_RANK

Number of Kafka consumer threads per rank; valid range is 1 through 6.The default is 1.

KAFKA_GROUP_ID

Consumer group ID to use for data sources configured for Kafka. If not specified, one will be randomly generated.

KAFKA_OPTIMISTIC_INGEST

Enable optimistic ingestion where Kafka topic offsets and table data are committed independently to achieve parallelism.The default is FALSE.

KAFKA_OFFSET_RESET_POLICY

Whether to start a Kafka subscription at the earliest or latest offset, for data sources configured for Kafka. The default is earliest.
ValueDescription
earliestStart streaming from the oldest message in the queue.
latestStart streaming from the newest message in the queue.

KAFKA_SUBSCRIPTION_CANCEL_AFTER

Optional number of minutes after which a Kafka subscription will be cancelled, for data sources configured for Kafka.

KAFKA_TYPE_INFERENCE_FETCH_TIMEOUT

Maximum time to collect Kafka messages before type inferencing on the set of them.The default is generally 30 seconds.

LOADING MODE

Use one of the following distribution schemes to load data files. The default mode is HEAD.
ModeDescription
HEADThe head node loads all data. All files must be available to the head node.
DISTRIBUTED LOCALA 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).
* The head node must be able to access at least one source file in order to determine the structure of a table that does not already exist. * Specifying a data source overrides this mode; such data is always loaded as though DISTRIBUTED SHARED were given. * Only hosts with at least one active worker rank participate in the load; rank 0 never loads data in this mode.
DISTRIBUTED SHAREDThe head node coordinates loading data by worker processes across all nodes from shared files available to all workers.
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.

MAX_RECORDS_TO_LOAD

Limit the number of records to load in this request. If the number is larger than BATCH SIZE, the number of records loaded will be limited to the next whole number of BATCH SIZE (per working thread).
This option is only available for file-based data sources.

NUM_SPLITS_PER_RANK

The number of remote query partitions to assign each Kinetica worker process. The queries assigned to a worker process will be executed by the tasks allotted to the process.To decrease memory pressure, increase the number of splits per rank.The default is 8 splits per rank.
This option is only available for data sources configured for JDBC.

NUM_TASKS_PER_RANK

The number of tasks to use on each Kinetica worker process to process remote data.To decrease memory pressure, decrease the number of tasks per rank.The default is 8 tasks per rank. This is configurable in external_file_reader_num_tasks.
This option is not available for data sources configured for Kafka.

ON ERROR

When an error is encountered loading a record, handle it using one of the following modes. The default mode is ABORT.
ValueDescription
PERMISSIVEIf an error is encountered parsing a source record, attempt to insert as many of the valid fields from the record as possible; insert a null for each errant value found.
SKIPIf an error is encountered parsing a source record, skip the record.
ABORTIf an error is encountered parsing a source record, stop the data load process. Primary key collisions are considered abortable errors in this mode.

POLL_INTERVAL

Interval, in seconds, at which a data source is polled for updates. The number of seconds must be passed as a single-quoted string.The default interval is 60 seconds. This option is only applicable when SUBSCRIBE is TRUE.
This option is not available for data sources configured for Kafka.

PRIMARY KEY

Optional primary key specification clause, where the value is a parenthesized comma-separated list of columns to use as the primary key for the table:

REMOTE_QUERY_INCREASING_COLUMN

For a JDBC query change data capture loading scheme, the remote query column that will be used to determine whether a record is new and should be loaded or not. This column should have an ever-increasing value and be of an integral or date/timestamp type. Often, this column will be a sequence-based ID or create/modify timestamp.This option is only applicable when SUBSCRIBE is TRUE.
This option is only available for data sources configured for JDBC.

REMOTE_QUERY_NO_SPLIT

Whether to not distribute the retrieval of remote data and issue queries for blocks of data at time in parallel.The default is FALSE.
This option is only available for data sources configured for JDBC
ValueDescription
TRUEIssue the remote data retrieval as a single query.
FALSEDistribute and parallelize the remote data retrieval in queries for blocks of data at a time.

REMOTE_QUERY_ORDER_BY

Ordering expression to use in partitioning remote data for retrieval. The remote data will be ordered according to this expression and then retrieved in sequential blocks from the first record. This is potentially less performant than using REMOTE_QUERY_PARTITION_COLUMN.If REMOTE_QUERY_NO_SPLIT is TRUE, a valid REMOTE_QUERY_PARTITION_COLUMN is specified, or the column given is invalid, this option is ignored.
This option is only available for data sources configured for JDBC

REMOTE_QUERY_PARTITION_COLUMN

Column to use to partition remote data for retrieval. The column must be numeric and should be relatively evenly distributed so that queries using values of this column to partition data will retrieve relatively consistently-sized result sets.If REMOTE_QUERY_NO_SPLIT is TRUE or the column given is invalid, this option is ignored.
This option is only available for data sources configured for JDBC

SCHEMA_REGISTRY_SCHEMA_NAME

Name of the Avro schema in the schema registry to use when reading Avro records.
This option is not available for data sources configured for Kafka.

SHARD KEY

Optional shard key specification clause, where the value is a parenthesized comma-separated list of columns to use as the shard key for the table:

SKIP_LINES

Skip this number of lines when loading from a source file.

SUBSCRIBE

Whether to subscribe to the data source specified in the DATA SOURCE option.The default is FALSE.
This option is not available for data sources configured for HDFS.
ValueDescription
TRUEStream data from the specified data source.
FALSELoad all data once from the specified data source.

TRUNCATE_STRINGS

Specify the string truncation policy for inserting text into VARCHAR columns that are not large enough to hold the entire text value.The default is FALSE.
ValueDescription
TRUETruncate any inserted string value at the maximum size for its column.
FALSEReject any record with a string value that is too long for its column.

TRUNCATE_TABLE

Specify whether to truncate the target table before beginning the load or subscription.The default is FALSE (don’t truncate the target table).

TYPE_INFERENCE_MODE

When making a type inference of the data values in order to define column types for the target table, use one of the following modes.The default mode is SPEED.
ValueDescription
ACCURACYScan all available data to arrive at column types that are the narrowest possible that can still hold all the data.
SPEEDPick the widest possible column types from the minimum data scanned in order to quickly arrive at column types that should fit all data values.

UPDATE_ON_EXISTING_PK

Specify the record collision policy for inserting into a table with a primary key. If the specified table does not have a primary key, then this options has no effect.The default is FALSE.
ValueDescription
TRUEUpdate existing records with records being inserted, when PKs match.
FALSEDiscard records being inserted when existing records’ PKs match.

Table Property Clause

A comma-separated list of options for creating the target table, if it doesn’t exist and if the source data file has Kinetica headers, can be specified. Kinetica headers contain column type information, which are used in creating the target table if it doesn’t exist. An example Kinetica header:
LOAD INTO Table Property Clause

CHUNK COLUMN MEMORY

Size of the blocks of memory holding the data, when loaded; specified as the maximum number of bytes any one column should hold.
The size of dictionary-encoded columns is estimated.

CHUNK MEMORY

Size of the blocks of memory holding the data, when loaded; specified as the maximum total number of bytes all columns should hold.
The size of dictionary-encoded columns is estimated.

CHUNK SIZE

Size of the blocks of memory holding the data, when loaded; specified as the maximum number of records each block of memory should hold

COMPRESSION_CODEC

The default compression type to apply to columns of this table not explicitly given one.

TTL

The time-to-live (TTL) for the table; if not set, the table will not expire

Examples

File Paths

Single File

To load a CSV file of product data named products.csv in the KiFS directory data, into a table named product:
LOAD INTO (Single File) Example

Multiple Files

When loading files from multiple paths, specify a comma-delimited list of those file paths. To load one file named products.csv and one file named products.kh.csv, both under the KiFS directory data, into a table named product:
LOAD INTO (Multiple Files) Example

File Formats

Single File - No Header

To load a headerless CSV file of product data named products.nh.csv in the KiFS directory data, into a table named product:
LOAD INTO (No Header) Example

Delimited Text Options

To load data from a product data file with the following options:
  • data file named products.ssv located in the KiFS directory data
  • the file has a header
  • the field delimiter is a semicolon
  • data requiring quotes will have single quotes as the quoting character
  • the escape character is the backtick
  • the data file represents null values as <null>
  • data file comments are on lines starting with --
  • when parse errors are encountered, the record will be skipped
LOAD INTO with Delimited Text Options Example

Kinetica Headers

A CSV file with Kinetica headers can be used to specify the column types of the target table when creating it if it doesn’t exist. To load such a file of product data with the following conditions:
  • data file named products.kh.csv located in the KiFS directory data
  • data file contains a Kinetica header
  • target table named product_create_on_load
  • target table will be created if it doesn’t exist
LOAD INTO (Kinetica Header) Example

Parquet File

To load a Parquet file of employee data, employee.parquet, in the KiFS directory data, into a table named example.employee_2000:
LOAD INTO (Parquet) Example

Kafka

To subscribe to a Kafka data feed with the following conditions:
  • Kafka remote source is represented by the kafka_ds data source
  • data will be continuously streamed from the Kafka source
  • target table named orders
LOAD INTO (Kafka) Example

Table Options

If the target table doesn’t exist, the LOAD INTO command will create it using the given table options and data type inferencing for the column types. See Kinetica Headers for an example of loading a file with Kinetica headers to define the column types of the created table.

Primary/Shard Keys

A CSV file can be used to create a target table with primary & shard keys if it doesn’t exist. To load such a file of employee data with the following conditions:
  • data file named employee.csv located in the KiFS directory data
  • data file does not contain a Kinetica header
  • target table named example.employee
  • target table will be created if it doesn’t exist
  • target table will have a composite primary key on the id & dept_id columns and a shard key on id column, if it is created by this load command
LOAD INTO (Primary/Shard Key) Example
The data must have no nulls in any columns designated as primary key columns.

Creation Options

Table creation options can be used to define characteristics of a table when creating it if it doesn’t exist. To load such a file of product data with the following conditions:
  • data file named products.kh.csv located in the KiFS directory data
  • data file does not contain a Kinetica header
  • target table named product_create_options
  • target table will be created if it doesn’t exist
  • target table will have a chunk size of 1,000,000 records, if it is created by this load command
  • target table will have a TTL of 5 minutes, and will be dropped if unused for any 5-minute span, if it is created by this load command
LOAD INTO (Create Table) Example

Column Options

Column/Field Names

To load specific fields from a product data file, with the following conditions:
  • data file named products.title-case.csv located in the KiFS directory data
  • data file contains a header with fields named ID, Category, Name, Description, & Stock
  • target table named product_name_stock
  • target columns named id, name, & stock
  • only load fields ID, Name, & Stock into columns id, name, & stock
  • skip records that fail to load successfully
LOAD INTO (Column/Field Names) Example
When specifying source data file field names, the set of source data file fields selected must align, in type & number, with the target table columns into which data will be loaded.

Date/Time Column Types

To apply a specific date format to the hire_date field:
LOAD INTO (Date/Time Column Types) Example

Dry Run

To perform a dry run of a load of a CSV file, products.csv, in the KiFS directory data, into a table named example.product:
LOAD INTO (Dry Run) Example
The dry run will return the number of records that would have been loaded, but not actually insert any records into the target table.

Data Sources

File-Based

To load a CSV file, products.csv, from the data source example.product_ds, into a table named example.product:
LOAD INTO (Data Source File) Example

Query-Based

To load the results of a remote query of employees in department 2 from the JDBC data source example.jdbc_ds, into a local table named example.employee_dept2:
LOAD INTO (Data Source Query) Example

Change Data Capture

File-Based

To load a set of order data in a change data capture scheme with the following conditions:
  • data pulled through a data source, example.order_ds
  • data files contained with an orders directory
  • initially, all files in the directory will be loaded; subsequently, only those files that have been updated since the last check will be reloaded
  • files will be polled for updates every 5 minutes
  • target table named example.orders
  • target table will be created if it doesn’t exist
LOAD INTO (File Change Data Capture) Example

Query-Based

To load the data from a remote query of orders in a change data capture scheme with the following conditions:
  • data pulled through a data source, example.jdbc_ds
  • data contained with an example.orders table, where only orders for product with ID 42 will be loaded into the target table
  • initially, all orders will be loaded; subsequently, only those orders with an order_id column value higher than the highest one on the previous poll cycle will be loaded
  • remote table will be polled for updates every 60 seconds
  • target table named example.order_product42
  • target table will be created if it doesn’t exist
LOAD INTO (Query Change Data Capture) Example