I am trying to configure a Snowflake import without writing code to show chemical engineers that Snowflake and Knime can be a good solution to sharing carbon emissions data / calculations.
Unfortunately when I get to the point of reading Snowflake data, and a particular table therein, I am getting this error which is suggesting a snowflake warehouse needs to be selected to extract / read the data (which seems strange). Does anyone know how to overcome this without writing SQL in the DB table selector drive the date extraction?
SOLVED! The text from this error comes straight from Snowflake and has been seen in other platforms connecting to Snowflake. In this case it occurred because the Snowflake āRoleā (termed āDefault access control roleā in the KNIME Snowflake connector) was set to PUBLIC in KNIME, however in Snowflake PUBLIC role had no access to the warehouse. Once changed to ACCOUNTADMIN in KNIME (a role which had warehouse access in Snowflake) the DB Table Selector worked.
Hi @nesmi1, welcome to the KNIME forum, and Iām glad to hear you resolved your problem.
Iād definitely recommend that you create lesser roles with default access to the required warehouse and then use a dedicated āservice userā with that role for basic loading/reporting access from KNIME, as accountadmin role is rather āgod-likeā in snowflake, and best not to use that for general querying .
(You may already know that in which case this is advice for anybody else who reads this in future. )