DuckDB
Connect & Ingest data from / to a DuckDB database
Setup
The following credentials keys are accepted:
instance
(required) -> The local file path of the database fileschema
(optional) -> The default schema to use.duckdb_version
(optional) -> The CLI version of DuckDB to use. You can also specify the env. variableDUCKDB_VERSION
.read_only
(optional) -> Whether to open the connection inreadonly
mode. Acceptstrue
orfalse
. Default isfalse
.interactive
(optional) -> Whether to communicate to the DuckDB CLI via interactive mode instead of reopening the connection each time. Acceptstrue
orfalse
. Default isfalse
.
Using sling conns
sling conns
Here are examples of setting a connection named DUCKDB
. We must provide the type=duckdb
property:
Environment Variable
Sling Env File YAML
See here to learn more about the sling env.yaml
file.
Specifying a DuckDB version
By default, Sling will download the DuckDB binary automatically. If you would like to use a specific DuckDB version, you can specify this way, and sling will download that version:
Specifying a DuckDB Binary Path
If you already have DuckDB on your machine and would like to use it (instead of having Sling download it), you can specify the binary path this way:
If you are facing issues connecting, please reach out to us at support@slingdata.io, on discord or open a Github Issue here.
Potential Issue
If you have a .duckdbrc
file, which runs commands whenever the DuckDB CLI is invoked, this may interfere with normal Sling operation. If you are facing weird issues and have this file, try again after deleting it.
Last updated