This node uses the selected driver's JDBC URL template to create the concrete database URL. Field validation in the dialog depends on whether the (included) tokens referencing them are mandatory or optional in the template.
This tab contains the main setting to connect to a Snowflake database. For more details about the different connection parameters see the Snowflake documentation.
Choose the JDBC driver to connect to the database here. If you select "Use latest driver version available" upon execution the node will automatically use the driver with the latest (highest) driver version that is available for the current database type. This has the advantage that you do not need to touch the workflow after a driver update. However, the workflow might break in the rare case that the behavior of the driver e.g. type mapping changes with the newer version.
If this option is not enabled, you can select a specific version of the registered drivers via the drop-down list. Additional drivers can be registered via KNIME's preference page "KNIME -> Databases". For more details on how to register a new driver see the database documentation.
This tab allows you to define JDBC driver connection parameter. The value of a parameter can be a
constant, variable, credential user, credential password or KNIME URL.
The TIMEZONE parameter is added with the default time zone of the KNIME runtime environment to
prevent mapping problems when working with
date and time data types.
For more details about the parameter see the
Snowlfake documentation or
ask your Snowflake administrator.
The application parameter is added as default to all Snowflake connections to track the usage
of KNIME Analytics Platform as Snowflake client (for details go
here).
If you are not comfortable sharing this information with Snowflake you can remove the parameter.
However, if you want to promote KNIME as a client with Snowflake leave the parameter as is.
This tab allows you to define KNIME framework properties such as connection handling, advanced SQL dialect settings or logging options.
This tab allows you to define rules to map from database types to KNIME types.
This tab allows you to define rules to map from KNIME types to database types.
To use this input port, you must attach the Microsoft Authenticator. Choose one of the OAuth2 authentication types and enter the custom scope you want to use. The scope is specific to the setup of your Azure Entra ID (formerly Azure Active Directory). For further details on how to create a scope or where to find it see the Snowflake documentation.
When available the node will set the authenticator as well as token JDBC parameter automatically based on the information from the connected Microsoft Authenticator node. Depending on your database setup you might need to specify additional JDBC parameters which are described in the Snowflake documentation.
You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.
To use this node in KNIME, install the extension KNIME Snowflake Integration from the below update site following our NodePit Product and Node Installation Guide:
A zipped version of the software site can be downloaded here.
Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.
Try NodePit Runner!Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to mail@nodepit.com.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.