CREATE DATA CONNECTION
The CREATE DATA CONNECTION
statement creates the metadata required to connect to an external system for later use.
Include data connections in mapping statements to allow the SQL service to connect to, read from, write to, or query data from your external systems. To simplify setup, you can use the same data connection in multiple SQL mappings.
You can also configure data connections programmatically or in the configuration files of Hazelcast members. |
Syntax Summary
This code block is a quick reference with all the parameters that you can use with the CREATE DATA CONNECTION
statement.
See some practical examples.
CREATE [OR REPLACE] DATA CONNECTION [IF NOT EXISTS] data_connection_name
TYPE connection_type
[[NOT] SHARED]
OPTIONS ('option_name' = 'option_value' [, ...] );
Parameters
The CREATE DATA CONNECTION
statement accepts the following parameters.
You must provide the following:
-
data_connection_name
-
connection_type
Parameter | Description |
---|---|
|
Overwrite an existing data connection of the same name, if it exists. If a data connection of the same name has been configured programmatically or in the configuration files of Hazelcast members, then the data connection will not be overwritten. Configured data connections always take precedence. |
|
Create a new data connection only if a connection of the same name does not already exist. |
|
Unique name for the data connection. |
|
The type of data connection required to connect to the external system. The following types of connection are supported: |
|
Every time you issue a query against a SQL mapping, a new physical connection to the external system is created. |
|
A reusable data connection. See the implementation of each data connection type for full details of reusability: |
|
Configuration options for the chosen |
Dependency Management
Replacing a data connection will not affect any queries that are already running. Only the following queries or jobs are affected by the changes:
-
New queries on existing mappings
-
Queries or jobs that are restarted after a data connection is updated
Permissions
Enterprise Edition
If security is enabled, you can grant or deny permission for certain clients to use this statement. See SQL Permissions.
Examples
Create a Kafka Data Connection
CREATE DATA CONNECTION IF NOT EXISTS myKafkaSource
TYPE Kafka
SHARED
OPTIONS (
'bootstrap.servers' = '127.0.0.1:9092');
Create a JDBC Data Connection
CREATE DATA CONNECTION IF NOT EXISTS myDatabase
TYPE JDBC
SHARED
OPTIONS (
'jdbcUrl'='jdbc:mysql://dummy:3306',
'user'='xyz',
'password'='xyz');
For a full list of configuration options, see HikariCP configuration.