Snowflake Destination User Failure

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Linux
  • Memory / Disk: 64Gb
  • Deployment: Docker
  • Airbyte Version: v0.36.4-alpha
  • Source name/version: N/A
  • Destination name/version: 0.4.24
  • Step: Sync & Connection
  • Description: At random intervals, the snowflake destination starts failing for all our different connectors. The error message is Could not connect with provided configuration. Incorrect username or password was specified.

To be clear:

  • The existing destination configuration is failing (username and password)
  • I create a new snowflake destination with the same credentials and the configuration succeeds.
  • I log into snowflake UI separately with the same username and password successfully.

So there is obviously an issue with existing destination configuration schema.

This is breaking all of our production syncs so its absolutely critical.

hey @danieldiamond can you share the sync logs for those syncs which failed

failed_logs.txt (19.4 KB)
successful_logs.txt (8.4 KB)

I’m providing the response from https://airbyte-public-api-docs.s3.us-east-2.amazonaws.com/rapidoc-api-docs.html#post-/v1/destinations/check_connection
the successful one is with a test snowflake destination and the failed one is with the existing destination. they both have the same credentials and configuration

I wonder if the source of the issue is at Exception during pool initialization

successful connection

        "2022-05-04 09:47:06 \u001b[32mINFO\u001b[m i.a.w.p.a.DefaultAirbyteStreamFactory(lambda$create$0):61 - 2022-05-04 09:47:06 \u001b[32mINFO\u001b[m c.z.h.HikariDataSource(getConnection):110 - HikariPool-1 - Starting...",
        "2022-05-04 09:47:07 \u001b[32mINFO\u001b[m i.a.w.p.a.DefaultAirbyteStreamFactory(lambda$create$0):61 - 2022-05-04 09:47:07 \u001b[32mINFO\u001b[m c.z.h.p.HikariPool(checkFailFast):565 - HikariPool-1 - Added connection net.snowflake.client.jdbc.SnowflakeConnectionV1@32091c14",
        "2022-05-04 09:47:07 \u001b[32mINFO\u001b[m i.a.w.p.a.DefaultAirbyteStreamFactory(lambda$create$0):61 - 2022-05-04 09:47:07 \u001b[32mINFO\u001b[m c.z.h.HikariDataSource(getConnection):123 - HikariPool-1 - Start completed.",
        "2022-05-04 09:47:08 \u001b[32mINFO\u001b[m i.a.w.p.a.DefaultAirbyteStreamFactory(lambda$create$0):61 - 2022-05-04 09:47:08 \u001b[32mINFO\u001b[m i.a.d.j.DefaultJdbcDatabase(lambda$unsafeQuery$1):106 - closing connection",

failed connection

        "2022-05-04 09:45:02 \u001b[32mINFO\u001b[m i.a.w.p.a.DefaultAirbyteStreamFactory(lambda$create$0):61 - 2022-05-04 09:45:02 \u001b[32mINFO\u001b[m c.z.h.HikariDataSource(getConnection):110 - HikariPool-1 - Starting...",
        "2022-05-04 09:45:04 \u001b[32mINFO\u001b[m i.a.w.p.a.DefaultAirbyteStreamFactory(lambda$create$0):61 - 2022-05-04 09:45:04 \u001b[1;31mERROR\u001b[m c.z.h.p.HikariPool(throwPoolInitializationException):594 - HikariPool-1 - Exception during pool initialization.",
        "2022-05-04 09:45:04 \u001b[32mINFO\u001b[m i.a.w.p.a.DefaultAirbyteStreamFactory(lambda$create$0):61 - net.snowflake.client.jdbc.SnowflakeSQLException: Incorrect username or password was specified.",

After further investigation, I have a theory it could be because we have been updating the credentials using the API and so password was configured at the same level as username i.e. password field was in connectionConfiguration and not nested within credentials.

However, password was set at both levels. So should the connection really fail if there’s password set at both levels, or if the schema sees additional fields within the schema?

At the very least the error message should be changed because that is completely misleading. Spent a bunch of time with snowflake support :-1:

Hey can you confirm after updating the password inside the credentials this problem is solved? And yeah if this is the case I agree that the error message is misleading

I have confirmed this for now.