Skip to main content
Several authentication schemes across multiple providers are supported. For a detailed overview of all of the provider-specific options, see the SQL documentation.
Creating an authenticated data source may require creating a corresponding credential object to store the authentication information and then referencing that object when creating the data source. See Creating Credentials for examples.

​
Azure BLOB

CREATE DATA SOURCE azure_ds
LOCATION = 'AZURE'
WITH OPTIONS
(
    CREDENTIAL = 'azure_cred',
    CONTAINER NAME = 'samplecontainer'
)

​
Google Cloud Storage

CREATE DATA SOURCE gcs_ds
LOCATION = 'GCS'
WITH OPTIONS
(
	CREDENTIAL = 'gcs_cred',
	GCS_BUCKET_NAME = 'gcs-public'
)

​
HDFS

CREATE DATA SOURCE hdfs_ds
LOCATION = 'HDFS://example.com:8020'
WITH OPTIONS
(
    CREDENTIAL = 'hdfs_cred'
)

​
JDBC

CREATE DATA SOURCE jdbc_ds
LOCATION = 'jdbc:postgresql://localhost:5432/ki_home'
WITH OPTIONS
(
	CREDENTIAL = 'jdbc_cred',
	JDBC_DRIVER_CLASS_NAME = 'org.postgresql.Driver',
	JDBC_DRIVER_JAR_PATH = 'kifs://drivers/postgresql.jar'
)

​
Kafka (Apache)

CREATE DATA SOURCE kafka_ds
LOCATION = 'KAFKA://example.com:9092'
WITH OPTIONS
(
    KAFKA_TOPIC_NAME = 'sample',
    CREDENTIAL = 'kafka_cred'
)
Creating an authenticated Kafka data source requires creating a corresponding credential object to store the Kafka credentials and then referencing that object when creating the data source. See Kafka (Apache) for examples.

​
Kafka (Confluent)

CREATE DATA SOURCE confluent_ds
LOCATION = 'CONFLUENT://example.com:9092'
WITH OPTIONS
(
    KAFKA_TOPIC_NAME = 'sample',
    CREDENTIAL = 'confluent_cred'
)
Creating an authenticated Confluent data source requires creating a corresponding credential object to store the Confluent credentials and then referencing that object when creating the data source. See Kafka (Confluent) for examples.

​
S3

CREATE DATA SOURCE s3_ds
LOCATION = 'S3'
WITH OPTIONS
(
    CREDENTIAL = 's3_cred',
    BUCKET NAME = 'samplebucket',
    REGION = 'us-east-2'
)