Starburst Snowflake connector#

The Snowflake connector allows querying and creating tables in an external Snowflake database. This can be used to join data between different systems like Snowflake and Hive, or between different Snowflake instances.


To connect to Snowflake, you need:


To configure the Snowflake connector, create a catalog properties file in etc/catalog named, for example,, to mount the Snowflake connector as the snowflake catalog.

There are two flavors of the Snowflake connector:

  • snowflake-jdbc

  • snowflake-distributed

snowflake-jdbc uses JDBC for all reads and writes and is more efficient when the result set returned from Snowflake is small.

When larger result sets are extracted from Snowflake, the snowflake-distributed connector may be a better choice. Instead of requesting query results over a JDBC connection, the connector asks Snowflake to export them to object storage and SEP reads them from there. Since write and read operations are parallelized, this approach scales better for large data sets, but has a higher latency.

A requirement of using the distributed connector is that your Snowflake deployment runs on AWS or Azure. The connector automatically creates temporary stages in temporary storage buckets using Snowflake.

Create the catalog properties file with the following contents, replacing the connection properties as appropriate for your setup (for example, replace <account_name> with the full name of your account, as provided by Snowflake).

For AWS:<snowflake-jdbc or snowflake-distributed>

For Azure:<snowflake-jdbc or snowflake-distributed>

The role used by Snowflake to execute operations can be specified as snowflake.role=<role_name>. This configuration is optional, and can not be used together with User impersonation.

Additionally, there are a number of configuration properties that apply only to the distributed connector.

Distributed connector configuration properties#

Property name




Name of the schema in which stages are created for exporting data


Number of export retries



Maximum block size when reading from the export file



Maximum split size for processing the export file



Maximum initial split size

Half of snowflake.max-split-size


Maximum size of files to create when exporting data


Type mapping#

General configuration properties#

The following properties can be used to configure how data types from the connected data source are mapped to Trino data types and how the metadata is cached in Trino.

Property name


Default value


Configure how unsupported column data types are handled:

  • IGNORE, column is not accessible.

  • CONVERT_TO_VARCHAR, column is converted to unbounded VARCHAR.

The respective catalog session property is unsupported_type_handling.



Allow forced mapping of comma separated lists of data types to convert to unbounded VARCHAR


Support case insensitive database and collection names



1 minute


Duration for which metadata, including table and column statistics, is cached

0 (disabled caching)


Cache the fact that metadata, including table and column statistics, is not available


SQL support#

The connector provides read and write access to data and metadata in the Snowflake database. In addition to the globally available and read operation statements, the connector supports the following features:


If a WHERE clause is specified, the DELETE operation only works if the predicate in the clause can be fully pushed down to the data source.


The connector includes a number of performance improvements, detailed in the following sections.

Table statistics#

The Snowflake connector supports only table statistics to improve query processing performance based on the actual data in the data source.

The statistics are collected by Snowflake and retrieved by the connector.

They are based on Snowflake’s INFORMATION_SCHEMA.TABLES table. Table statistics are automatically updated by Snowflake.


The connector supports pushdown for a number of operations:

Aggregate pushdown for the following functions:

Dynamic filtering#

Dynamic filtering is enabled by default. It causes the connector to wait for dynamic filtering to complete before starting a JDBC query.

You can disable dynamic filtering by setting the property dynamic-filtering.enabled in your catalog properties file to false.

JDBC connection pooling#

You can improve performance by enabling JDBC connection pooling, which is disabled by default.

Starburst Cached Views#

The connectors supports table scan redirection to improve performance and reduce load on the data source.


The connector includes a number of security-related features, detailed in the following sections.

User impersonation#

The Snowflake connector supports User impersonation. It can be configured to use a number of different impersonation mechanisms, specified by the values configured for the property snowflake.impersonation-type:


Connect as the service user with the credentials from the catalog properties file and assume the role defined by the snowflake.role property, or the service user’s default role, if the property is missing.


Connect as the service user and use auth-to-local mapping to map the user to a role.


Assume the identity of the SEP user, authenticated with Okta using LDAP credentials, and use the default Snowflake user role.


As above, but additionally use auth-to-local mapping to map the user to a role.


Impersonation using Okta is not supported for Azure.

Authentication with Okta#

The Snowflake connector supports the usage of the Okta Single Sign-On system to authenticate users via SEP to Snowflake.


Okta authentication is not supported for Azure.

The setup allows users to authenticate to SEP using their LDAP credentials and use the same credentials to authenticate to Snowflake through Okta. The same credentials are used by SEP when accessing data in Snowflake.

Behind the scenes SEP and the Snowflake connector authenticate to Okta with the LDAP credentials of the user. After the user authenticates with Okta, including MFA potentially, a SAML assertion allows Snowflake to issue an an OAuth 2.0 token pair. The tokens are cached in SEP and used for further authentications until they expire, and another authentication is requested.

If Okta multi-factor authentication (MFA) is configured, users have to confirm authentication with it. One time codes are not supported.

To enable the Okta integration, SEP and Snowflake need to be configured correctly.

Okta and SEP are configured to use LDAP authentication using the same user identifiers and LDAP directory. In addition to the usual LDAP configuration, LDAP authentication, for SEP, you need to enable password forwarding in etc/


Snowflake is configured in Okta as a SAML application as detailed in the Snowflake documentation. Note that the Snowflake login_name must match the corresponding SAML Subject NameID attribute value.

SEP is configured as an OAuth client in Snowflake, again detailed in the Snowflake OAuth documentation.

A number of properties are required to configure the Okta integration in the Snowflake catalog properties file:


Name of Snowflake account.


URL of the Snowflake account. The URL usually has the form, but might include additional segments.


Snowflake OAuth client id. This can be retrieved with the secret name and a query like select system$show_oauth_client_secrets('OAUTH_TEST_INT');.


Snowflake OAuth client secret.


Duration the OAuth refresh token is cached. This value cannot exceed the oauth_refresh_token_validity value used when the OAuth integration was created. E.g. 24h.


The Okta URL, typically

Optional properties allow you to override the default values:


The size of the OAuth credentials cache. Use a value that accommodates the expected number of users that might connect to Snowflake through SEP during the period defined by the TTL of the token. Defaults to 10000.


Connection timeout. Defaults to 30s.


Connection read timeout. Defaults to 30s.


Connection write timeout. Defaults to 30s.


The redirect URI for OAUTH. Value must match the redirect URI specified when creating the security integration (oauth_redirect_uri). Defaults to https://localhost.


Connection timeout. Defaults to 30s.


Connection read timeout. Defaults to 30s.


Connection write timeout. Defaults to 30s.

OAuth 2.0 token pass-through#

The Snowflake connector supports OAuth 2.0 token pass-through.

Configure this option the same as Authentication with Okta, except for the settings described in this section.

Set the authentication type and OAuth 2.0 scope in the coordinator’s config properties file:


The session:role prefix determines the role assigned to the user after successful authentication.

Additionally enable OAUTH2_PASSTHROUGH in the catalog properties file using the Snowflake connector: