Snowflake

Connect & Ingest data from / to a Snowflake database

Sling CLI Setup

The following credentials keys are accepted:

• host (required) -> The hostname or account the instance (eg. pua90768.us-east-11)

• user (required) -> The username to access the instance

• database (required) -> The database name of the instance

• password (optional) -> The password to access the instance

• schema (optional) -> The default schema to use

• role (optional) -> The role to access the instance

• warehouse (optional) -> The warehouse to use

• passcode (optional) -> Specifies the passcode provided by Duo when using multi-factor authentication (MFA) for login.

• authenticator (optional) -> Specifies the authenticator to use to login (e.g. snowflake_jwt, externalbrowser).

• private_key_path (optional) -> Specifies the private key file path to use.

• private_key_passphrase (optional) -> Specifies the private key file passphrase.

• max_chunk_download_workers (optional) -> Specifies the Maximum Number of Result Set Chunk Downloader (integer).

• custom_json_decoder_enabled (optional) -> Specifies to use the Custom JSON Decoder for Parsing Result Set (true or false).

Here are examples of setting a connection named SNOWFLAKE. We must provide the type=snowflake property:

$ sling conns set SNOWFLAKE type=snowflake host=<host> user=<user> database=<database> password=<password> role=<role>

# Or use url
$ sling conns set SNOWFLAKE url="snowflake://myuser:[e-mail]/mydatabase?schema=<schema>&role=<role>"

Environment Variable

export SNOWFLAKE='snowflake://myuser:[e-mail]/mydatabase?schema=<schema>&role=<role>'

Sling Env File YAML

See here to learn more about the sling env.yaml file.

connections:
  SNOWFLAKE:
    type: snowflake
    host: <host>
    user: <user>
    password: <password>
    port: <port>
    database: <database>
    schema: <schema>
    role: <role>
    warehouse: <warehouse>

  SNOWFLAKE_URL:
    url: "snowflake://myuser:[e-mail]/mydatabase?schema=<schema>&role=<role>"

If you are facing issues connecting, please reach out to us at [e-mail], on discord or open a Github Issue here.