You can use a Snowflake catalog to configure access to Snowflake in the following deployments:
Follow these steps to create a catalog for Snowflake:
The following sections provide more detail for creating Snowflake catalog connections.
The Cloud provider configuration is necessary to allow Starburst Galaxy to correctly match catalogs and clusters.
The data source configured in a catalog, and the cluster must operate in the same cloud provider and region for performance and cost reasons.
If you select the Google Cloud icon, a pop-up note reminds you that Snowflake can only be used with Google Cloud as a read only catalog. No write operations can be performed.
The Catalog name is visible in the query editor and other clients. It is used to identify the catalog when writing SQL or showing the catalog and its nested schemas and tables in client applications.
The name is displayed in the query editor, and in the output of a SHOW
CATALOGS command.
It is used to fully qualify the name of any table in SQL queries following the
catalogname.schemaname.tablename
syntax. For example, you can run the
following query in the sample cluster without first setting the catalog or
schema context: SELECT * FROM tpch.sf1.nation;
.
The Description is a short, optional paragraph that provides further details about the catalog. It appears in the Starburst Galaxy user interface and can help other users determine what data can be accessed with the catalog.
Read further to learn about each supported connection method. The following sections detail the setup for the supported cloud providers.
Connect directly
The connection to the database requires a username, password authentication,
and the details necessary to connect to the database server, typically
hostname or IP address and port.
PrivateLink Starburst Galaxy supports AWS PrivateLink for Snowflake catalogs.
The user credentials must belong to a user that has been granted permissions to use the Snowflake role with the required access rights.
To configure the connection to your Snowflake cluster, you must provide the following details:
Snowflake account identifier: which specifies your Snowflake account ID in
a URL-friendly lowercase form, where <account_name>
can include additional
<account_locator>
and <cloud_region_id>
or
<cloud_region_id>.<cloud>
segments that identify the cloud platform and
region where your account is hosted. The identifier can take different forms,
depending on the specifics of your Snowflake account. The most common forms
are:
<orgname>-<account_name>
For example, starburstdata-gh41406
.<account_locator>
For example, gh41406
.<account_locator>.<cloud_region_id>
For example,
gh41406.east-us-2
.<account_locator>.<cloud_region_id>.<cloud>
For example,
gh41406.east-us-2.aws
.See account identifiers to learn more about Snowflake identifier formats.
Username: enter a Snowflake username.
Password: specify the password for this username.
Database name: specify the database you want to connect to.
Warehouse name: specify the warehouse you want to connect to.
Snowflake role: select a role with the required access rights.
The toggle_on Enable parallel mode toggle is disabled by default. Leave disabled to continue using single-thread query mode, which conserves resources. Otherwise, click to enable parallel mode.
With parallel mode enabled, this catalog takes advantage of a feature of the Snowflake JDBC driver to fetch query results over multiple parallel connections. For most queries, this translates to faster performance.
Snowflake parallel mode is a public preview feature. Contact Starburst support with questions or feedback.
Once you have configured the connection details, click Test connection to confirm data access is working. If the test is successful, you can save the catalog.
If the test fails, look over your entries in the configuration fields, correct any errors, and try again. If the test continues to fail, Galaxy provides diagnostic information that you can use to fix the data source configuration in the cloud provider system.
Click Connect catalog, and proceed to set permissions where you can grant access to certain roles.
This optional step allows you to configure read-only access or full read and write access to the catalog.
Use the following steps to assign read-only access to all roles:
You can specify read-only access and read-write access separately for different sets of roles. That is, one set of roles can get full read and write access to all schemas, tables, and views in the catalog, while another set of roles gets read-only access.
Use the following steps to assign read/write access to some or all roles:
You can add your catalog to a cluster later by editing a cluster. Click Skip to proceed to the catalogs page.
Use the following steps to add your catalog to an existing cluster or create a new cluster in the same cloud region:
Click Add to cluster to view your new catalog’s configuration.
The catalog provides read access and write access to data and metadata in the Snowflake database. It supports the following features:
The following section provides details for the SQL support with Snowflake catalogs.
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.
Is the information on this page helpful?
Yes
No