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

​
Azure BLOB

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

​
Google Cloud Storage

CREATE DATA SINK gcs_dsink
LOCATION = 'GCS'
WITH OPTIONS
(
	CREDENTIAL = 'gcs_cred',
	GCS_BUCKET_NAME = 'gcs-private'
)

​
HDFS

Credential
CREATE DATA SINK hdfs_dsink
LOCATION = 'HDFS://example.com:8020'
WITH OPTIONS
(
	CREDENTIAL = 'hdfs_cred'
)

​
JDBC

CREATE DATA SINK jdbc_dsink
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

CREATE DATA SINK kafka_dsink
LOCATION = 'kafka://example.com:9092'
WITH OPTIONS
(
    KAFKA_TOPIC_NAME = 'sample',
    CREDENTIAL = 'kafka_cred'
)

​
Local Table

User Auth
CREATE DATA SINK local_table_dsink
LOCATION = 'table://example.local_target_table'

​
S3

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

​
Webhook

CREATE DATA SINK http_dsink
LOCATION = 'http://example.com/webhook'