Skip to main content
Creates a new data source, which contains the location and connection information for a data store that is external to Kinetica. A data source serves as an authentication & access mechanism to a remote resource and can optionally be used as a streaming source as well.
CREATE DATA SOURCE Syntax
A data source does not reference specific data files within the source; file references (if applicable) can be made by using the data source in a CREATE EXTERNAL TABLE call (for creating a persistent view of the file data) or a LOAD INTO call (for either a one-time load or a subscribed loading of data from the external source to a locally persisted table).
The data source will be validated upon creation, by default, and will fail to be created if an authorized connection cannot be established.
The following data source providers are supported:
  • Azure (Microsoft blob storage)
  • GCS (Google Cloud Storage)
  • HDFS (Apache Hadoop Distributed File System)
  • JDBC (Java Database Connectivity, using a user-supplied driver or one of the drivers on the supported list)
  • Kafka (streaming feed)
    • Apache
    • Confluent
  • S3 (Amazon S3 Bucket)
  • Azure anonymous data sources are only supported when both the container and the contained objects allow anonymous access.
  • HDFS systems with wire encryption are not supported.
  • Confluent & Kafka data sources require an associated credential for authentication.
For provider-specific syntax, see Provider-Specific Syntax. For provider-specific examples, see Creating Data Sources.

Parameters

OR REPLACE

Any existing data source with the same name will be dropped before creating this one

EXTERNAL

Optional keyword for clarity

<schema name>

Name of the schema that will contain the created data source; if no schema is specified, the data source will be created in the user’s default schema

<data source name>

Name of the data source to create; must adhere to the supported naming criteria

<provider>

Provider of the data sourceSupported providers include:
ProviderDescription
AZUREMicrosoft Azure blob storage
CONFLUENTConfluent Kafka streaming feed
The LOCATION can be a comma-delimited list of Kafka URLs, to be used for high-availability; only one of which will be streamed from at any given time.
GCSGoogle Cloud Storage
HDFSApache Hadoop Distributed File System
JDBCJDBC connection, where LOCATION is the JDBC URL.
LOCATION = ‘jdbc:postgresql://example.com:5432/mydb’
See the supported list for the full list of supported drivers, or specify one with JDBC_DRIVER_JAR_PATH and JDBC_DRIVER_CLASS_NAME.
KAFKAApache Kafka streaming feed
The LOCATION can be a comma-delimited list of Kafka URLs, to be used for high-availability; only one of which will be streamed from at any given time.
S3Amazon S3 bucket

<host>

Host to use to connect to the data source; the following providers have a default host, if host is left blank:
ProviderDefault Host
Azure<storage_account_name>.blob.core.windows.net
GCSstorage.googleapis.com
S3<region>.amazonaws.com

<port>

Port, for HDFS or Kafka, to use to connect to the data source

USER

Optional user name, given in <username>, to use for authenticating to the data source

PASSWORD

Optional password, given in <password>, to use for authenticating to the data source

WITH OPTIONS

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

Examples

To create a data source, kin_ds, that connects to an Amazon S3 bucket, kinetica_ds, in the US East (N. Virginia) region:
CREATE DATA SOURCE Example

Options

Provider-Specific Syntax

Several authentication schemes across multiple providers are supported.

Azure

Syntax below, examples here.

GCS

Syntax below, examples here.

HDFS

Syntax below, examples here.

JDBC

Syntax below, examples here.

Kafka (Apache)

Syntax below, examples here.

Kafka (Confluent)

Syntax below, examples here.

S3

Syntax below, examples here.