Thanks for your help with the above issue! I just ...
# airbyte-api
r
Thanks for your help with the above issue! I just reached a similar issue with creating a destination, which does not seem to be a connector-specific issue this time: I can successfully add a snowflake destination through the SDK, but when trying to test the destination on the Airbyte UI, I get the following exception:
Copy code
Could not connect with provided configuration. net.snowflake.client.jdbc.SnowflakeSQLException: Cannot perform CREATE SCHEMA. This session does not have a current database. Call 'USE DATABASE', or use a qualified name.

Logs:
2023-07-14 20:16:32 [32mINFO[m i.a.w.t.TemporalAttemptExecution(get):138 - Cloud storage job log path: /workspace/4ef3ddd3-29d9-4094-b9b6-d1703ebe4089/0/logs.log
I did try to run the suggested Snowflake script for setting up the Airbyte entities (wired to the same user/warehouse/database/schema etc.) with no luck. Any advice on how to solve it?
j
Hey @Ron Braha! Not sure exactly what’s going on here, let us take a look and see if we can figure out what’s going on with this job/connection.
Hey @Ron Braha I reached out to our support team who has much more experience troubleshooting connector issues and they recommended that you submit a support request which I believe you can create from here: https://support.airbyte.com/hc/en-us/requests/new. Do you mind doing so to get this issue into their queue?
r
Sure, I just submitted this ticket, I'll let you know about any updates
The support team helped me identify the issue: it was related to the naming convention of the snowflake entities - should not include dashes ('-') in names
j
Ah that makes sense, thanks for letting me know and hope that unblocks you going forward! Feel free to reach out if you have any other questions!