Airbyte Snowflake loads need a JDBC version check

A connector can be the latest published image while its bundled dependency is older than the warehouse's policy. An Airbyte issue reports that destination-snowflake:5.2.0 contains a Snowflake JDBC 3.26.1 jar and that one organization's Snowflake account requires a newer driver. The reporter sees JDBC 3.26.1 in Snowflake query history. This is an open, untriaged report, so treat the exact image and version as a test target rather than a universal statement about every Airbyte deployment.

Identify the client actually connecting

Record the destination connector image tag and digest, Airbyte platform version, and Snowflake connection settings. In a controlled environment, inspect the deployed image for its JDBC jar and compare that with the client version Snowflake records for a test load. Do not infer the JDBC version from the Airbyte platform version or from the source Snowflake connector; source and destination images ship independently.

Compare against the account's rule

Ask the Snowflake administrator for the account's minimum driver requirement and the exact enforcement date or warning. Separate a warning in query history from a rejected connection or a failed sync. The Airbyte Snowflake destination guide identifies connector version 5.2.0 and describes its setup and authentication requirements, but a connector version is not itself proof of a compliant embedded driver.

Plan a supported path

If the deployed image is below policy, raise a vendor ticket with the image digest, observed driver version, Snowflake warning or error, and a reproducible test. Evaluate a vendor-supported update in staging, including authentication and write-path tests. Avoid quietly replacing jars inside a production image: it can change APIs and create an unrepeatable deployment. Put the dependency check in upgrade acceptance so the next connector release is assessed before cutover.

Adovo’s view

The version that matters is the one making the connection. A green sync is temporary evidence; a supported, policy-compliant dependency chain is an operating condition. Test the artifact you deploy, not the release label you intended.