import KeypairExample from ‘@site/static/_snowflake_keypair_generation.md’;
Snowflake
Set up the Snowflake destination connector by creating the required Snowflake entities and configuring the connector in the Airbyte UI. These entities include a warehouse, database, schema, user, and role.
Follow this guide to set up the Snowflake destination connector.
:::danger Username and password authentication is deprecated From version 5.0.0, username and password authentication is deprecated. It will be removed in a future release. Snowflake now recommends Key pair authentication or a programmatic access token for connections.
This change aligns with Snowflake’s deprecation of single-factor password sign-ins. Snowflake is enforcing strong authentication per account on a rolling basis between August and October 2026. Once enforced, password-only Airbyte logins to your account will fail.
If you currently use username and password authentication, see Snowflake Migration Guide. It explains how to migrate to key pair authentication or a programmatic access token. :::
Prerequisites
- A Snowflake account with the
ACCOUNTADMIN
role. If your account doesn’t have the
ACCOUNTADMINrole, ask your Snowflake administrator to set it up.
Setup
Step 1: Set up key pair authentication
Step 2: Create Airbyte entities in Snowflake
Create Airbyte-specific Snowflake entities to set up the destination connector. You need a warehouse, database, schema, service user, and role with OWNERSHIP permission. These entities let Airbyte write data into Snowflake, track related costs, and control permissions at a granular level.
Run the following script in a new Snowflake worksheet to create the entities:
-
Edit the script below if you want to rename the resources. Replace
<public_key_value>with the RSA public key you generated in Step 1.Note: Follow the Snowflake identifier requirements when renaming resources.
-- set variables (these need to be uppercase)
set airbyte_role = 'AIRBYTE_ROLE';
set airbyte_username = 'AIRBYTE_USER';
set airbyte_warehouse = 'AIRBYTE_WAREHOUSE';
set airbyte_database = 'AIRBYTE_DATABASE';
set airbyte_schema = 'AIRBYTE_SCHEMA';
begin;
-- create Airbyte role
use role securityadmin;
create role if not exists identifier($airbyte_role);
grant role identifier($airbyte_role) to role SYSADMIN;
-- create Airbyte service user with key pair authentication
create user if not exists identifier($airbyte_username)
type = service
default_role = $airbyte_role
default_warehouse = $airbyte_warehouse;
grant role identifier($airbyte_role) to user identifier($airbyte_username);
-- assign the RSA public key to the service user
-- Replace <public_key_value> with the contents of your rsa_key.pub file (excluding the
-- -----BEGIN PUBLIC KEY----- and -----END PUBLIC KEY----- header/footer lines).
alter user identifier($airbyte_username) set rsa_public_key='<public_key_value>';
-- change role to sysadmin for warehouse / database steps
use role sysadmin;
-- create Airbyte warehouse
create warehouse if not exists identifier($airbyte_warehouse)
warehouse_size = xsmall
warehouse_type = standard
auto_suspend = 60
auto_resume = true
initially_suspended = true;
-- create Airbyte database
create database if not exists identifier($airbyte_database);
-- grant Airbyte warehouse access
grant USAGE
on warehouse identifier($airbyte_warehouse)
to role identifier($airbyte_role);
-- grant Airbyte database access
grant OWNERSHIP
on database identifier($airbyte_database)
to role identifier($airbyte_role);
commit;
- Run the script using the Worksheet page or Snowsight. In the Classic Console, select the All Queries checkbox. In Snowsight, select and highlight the entire query.
:::info
Airbyte automatically creates the required schemas in your Snowflake destination database.
To enable this, give the connection user CREATE SCHEMA privileges on the target database.
You can also create schemas manually. The connection user must have OWNERSHIP privileges on those schemas.
This lets the connection manage the tables and other objects required for the integration.
:::
:::info Cost-saving tip
Snowflake bills for compute by the second. The warehouse resumes and incurs charges each time Airbyte loads data. To reduce costs, use a dedicated X-Small warehouse with a one-minute auto-suspend timeout for Airbyte syncs. This is the smallest available compute tier. It shuts the warehouse down quickly after each load, minimising idle compute charges. The script above already configures these settings (warehouse_size = xsmall, auto_suspend = 60).
:::
Step 3: Configure network policies
By default, Snowflake accepts connections from any computer or device IP address. A security administrator with the SECURITYADMIN role, or higher, can create a network policy. This policy can allow or deny one IP address or a list of addresses.
If you use Airbyte Cloud, add Airbyte’s IP addresses to your Snowflake network policy allowlist.
Run the SHOW PARAMETERS command to check for a network policy on your account or a specific user.
Account
SHOW PARAMETERS LIKE 'network_policy' IN ACCOUNT;
User
SHOW PARAMETERS LIKE 'network_policy' IN USER <username>;
For more information, see the official Snowflake documentation
Step 4: Choose a data loading method
Airbyte uses Snowflake’s Internal Stage to load data.
Airbyte creates internal stages in the internal schema (raw_data_schema, default airbyte_internal). The role needs CREATE STAGE only on that schema, not on the output schemas.
Ensure the database and schema have the USAGE privilege.
Step 5: Add Snowflake as an Airbyte destination
Open the Airbyte UI and add Snowflake as a destination. Authenticate with the private key generated in Step 1 or, if you prefer, a programmatic access token.
| Field | Description |
|---|---|
| Host | The host domain of the Snowflake instance, ending with snowflakecomputing.com. Use the format accountname.snowflakecomputing.com or, for accounts that use a region-based locator, accountname.region.cloud.snowflakecomputing.com. Example: accountname.us-east-2.aws.snowflakecomputing.com |
| Role | The role you created in Step 2 for Airbyte to access Snowflake. Example: AIRBYTE_ROLE |
| Warehouse | The warehouse you created in Step 2 for Airbyte to sync data into. Example: AIRBYTE_WAREHOUSE |
| Database | The database you created in Step 2 for Airbyte to sync data into. Example: AIRBYTE_DATABASE |
| Schema | The default schema used as the target schema for all statements issued from the connection that do not explicitly specify a schema name. |
| Username | The service user you created in Step 2 to allow Airbyte to access the database. Example: AIRBYTE_USER |
| Authorization Method | How Airbyte authenticates as the user above. Choose Key Pair Authentication (recommended) or Programmatic Access Token. Username and Password is deprecated; see the migration guide. |
| Private Key | For Key Pair Authentication. The private key from the key pair you generated in Step 1. Paste the full contents of your rsa_key.p8 file, including the -----BEGIN ... PRIVATE KEY----- header and footer. |
| Passphrase (Optional) | For Key Pair Authentication. The passphrase for the private key, if the key was generated with encryption. Leave blank if the key is unencrypted. |
| Programmatic Access Token | For Programmatic Access Token authentication. The token secret generated for the user above. See Programmatic access token authentication. |
| CDC deletion mode | Whether to execute CDC deletions as hard deletes or soft deletes. Hard deletes propagate source deletions to the destination. Soft deletes leave a tombstone record in the destination. Defaults to hard deletes. |
| JDBC URL Params (Optional) | Additional properties to pass to the JDBC URL string when connecting to the database formatted as key=value pairs separated by the symbol &. Example: key1=value1&key2=value2&key3=value3 |
| Legacy raw tables (Optional) | Write the legacy raw tables format for backwards compatibility with older versions of this connector. See Output schema. The data format in _airbyte_data is fairly stable but there are no guarantees that other metadata columns will remain the same in future versions. |
| Airbyte Internal Table Dataset Name (Optional) | The schema used for Airbyte’s internal tables. In legacy raw tables mode, the raw tables are stored in this schema. Defaults to airbyte_internal. |
| Trim Whitespace from String Fields (Optional) | Whether Snowflake should trim leading and trailing whitespace from fields during data loading. Disable this option if leading or trailing whitespace in string fields is meaningful and should be preserved. |
| Data Retention Period (Optional) | The number of days of Snowflake Time Travel to enable on tables. A nonzero value incurs increased storage costs in your Snowflake instance. Defaults to 1. |
| Decimal Data Type (Optional) | Determines which Snowflake data type Airbyte uses for columns with the Airbyte number type: NUMBER(38,9) (recommended) or FLOAT (default). See Data type map for guidance on choosing between them. |
Programmatic access token authentication
You can use a Snowflake programmatic access token (PAT) instead of key pair authentication. Airbyte presents the token to Snowflake in place of a password for the user entered in Username.
-
Create a PAT for the Airbyte user in Snowflake:
ALTER USER <user_name> ADD PROGRAMMATIC ACCESS TOKEN <token_name> ROLE_RESTRICTION = '<airbyte_role>' DAYS_TO_EXPIRY = <days>;Snowflake shows the token secret only when you create the token. Store it securely before closing the result.
-
In Airbyte, select Programmatic Access Token as the authorisation method. Enter the Snowflake username in Username and paste the token secret into Programmatic Access Token.
Keep these points in mind when using a PAT:
- Tokens expire. A PAT expires after the number of days set with
DAYS_TO_EXPIRY. The default is 15 days, with a maximum of 365. When it expires, syncs fail until you create a new token and update the Programmatic Access Token field. Plan to rotate the token before expiry. Key pair authentication doesn’t have this limitation. - Network policy. By default, Snowflake requires a network policy on the user to generate or use a PAT. If you use Airbyte Cloud, ensure that policy allows Airbyte’s IP addresses. See Step 3.
- Service users. For users with
TYPE = SERVICE, Snowflake requiresROLE_RESTRICTIONwhen you create the token. If an authentication policy restricts permitted methods, includePROGRAMMATIC_ACCESS_TOKENinAUTHENTICATION_METHODS.
Output schema
By default, Airbyte outputs each stream to its own raw table in the airbyte_internal schema. You can override this using the Airbyte Internal Table Dataset Name setting. Airbyte also creates a final table with typed columns. Raw table contents aren’t deduplicated.
:::info By default, Airbyte creates permanent tables. To use transient tables, create a dedicated transient database for Airbyte. This makes every Airbyte-created table transient by default. It reduces the extra costs and storage associated with Fail-safe. However, you can’t recover transient tables after operational or system failures.
If you configure a custom Airbyte Internal Table Dataset Name internal schema, keep the default and internal schemas in matching database types. Both databases must be transient or both permanent. This prevents inconsistent data protection behaviour. For more information, see Working with Temporary and Transient Tables. :::
Raw table schema
The raw table contains these fields:
_airbyte_raw_id_airbyte_generation_id_airbyte_extracted_at_airbyte_loaded_at_airbyte_meta_airbyte_data
_airbyte_data is a JSON blob containing the event data. See here for more information about the other fields.
:::info
The contents of _airbyte_data are fairly stable. However, the raw table schema may change in future versions.
:::
Final table schema
The final table includes these fields alongside the columns declared in your stream schema:
_AIRBYTE_RAW_ID_AIRBYTE_GENERATION_ID_AIRBYTE_EXTRACTED_AT_AIRBYTE_LOADED_AT_AIRBYTE_META
See here for more information about these fields.
Data type map
| Airbyte type | Snowflake type |
|---|---|
| STRING | TEXT |
| STRING (BASE64) | TEXT |
| STRING (BIG_NUMBER) | TEXT |
| STRING (BIG_INTEGER) | TEXT |
| NUMBER | FLOAT (default) or NUMBER(38,9) |
| INTEGER | NUMBER |
| BOOLEAN | BOOLEAN |
| STRING (TIMESTAMP_WITH_TIMEZONE) | TIMESTAMP_TZ |
| STRING (TIMESTAMP_WITHOUT_TIMEZONE) | TIMESTAMP_NTZ |
| STRING (TIME_WITH_TIMEZONE) | TEXT |
| STRING (TIME_WITHOUT_TIMEZONE) | TIME |
| DATE | DATE |
| OBJECT | OBJECT |
| ARRAY | ARRAY |
| UNION | VARIANT |
| UNKNOWN | VARIANT |
The Decimal Data Type setting controls the Snowflake data type used for columns with the Airbyte NUMBER decimal type:
- NUMBER(38,9) (recommended): An exact fixed-point decimal type supporting up to 38 total digits. It supports up to 29 digits before the decimal point and 9 after it. Use it for financial data and other values requiring exact decimal representation within this precision and scale.
- FLOAT (default): An approximate binary floating-point type with around 15 digits of precision. It supports magnitudes up to approximately 10^308. It suits scientific calculations, statistical models, probabilities, model scores, and uses requiring a wide numeric range. Small rounding differences must be acceptable.
Unaffected cases:
- Legacy raw tables mode: This setting has no effect because there are no typed columns. All values are stored in the
_airbyte_dataVARIANT column. - Scale-0 database types, such as
NUMERIC(10,0): Source connectors map these to the AirbyteINTEGERtype. Snowflake always stores this type as NUMBER, so this setting doesn’t affect it.
:::warning Run a full refresh after changing this setting on an existing connection. Otherwise, Airbyte converts existing number columns in place during the next sync. FLOAT and NUMBER(38,9) have different range and precision characteristics. Conversion can therefore cause data loss, reduced precision, truncated values, or NULL values:
- Switching to NUMBER(38,9): Stored FLOAT values with more than 29 digits before the decimal point become NULL during conversion. Snowflake converts the column in place, so Airbyte doesn’t process individual rows. Therefore, these changes don’t add a
_airbyte_metaentry. Values originally loaded as FLOAT may already have lost precision. These rows are flaggedTRUNCATEDin_airbyte_metaand remain imprecise because conversion can’t restore unstored digits. Only a full refresh re-syncs the original source values. - Switching to FLOAT: Values silently become approximate again, and query results may differ slightly.
:::
Precision and size limits
Snowflake applies these precision limits to numeric types:
- FLOAT: A standard 64-bit floating-point value.
- NUMBER(38,9), when selected as the number data type: A maximum of 29 digits before the decimal point. Larger values become NULL and are flagged in
_airbyte_meta. If your data contains values this large, use the FLOAT option instead. Values with more than 9 decimal places are truncated and flagged in_airbyte_meta. - NUMBER (INTEGER): A maximum of 38 digits.
Airbyte replaces values outside these type boundaries with NULL. It rounds values within the boundaries when they have excessive precision. In both cases, the _airbyte_meta column includes a changes entry recording the change.
Snowflake also applies size limits to text and semi-structured types:
- VARCHAR: A maximum of 16 MB when UTF-8 encoded.
- VARIANT, used for OBJECT, ARRAY, UNION, and UNKNOWN types: A maximum of 128 MB.
Values exceeding these size limits become NULL, and the _airbyte_meta column records the change.
Schema evolution
This connector supports automatic schema evolution. When the source schema changes, it adds new destination columns and modifies column types as needed. If a source column is removed, the connector retains its destination column and historical data. Subsequent rows use NULL for that column. The connector requires ALTER TABLE privileges on destination tables for this feature.
Supported sync modes
The Snowflake destination supports these sync modes:
| Sync mode | Supported |
|---|---|
| Full Refresh - Overwrite | Yes |
| Full Refresh - Overwrite + Deduped | Yes |
| Full Refresh - Append | Yes |
| Incremental Sync - Append | Yes |
| Incremental Sync - Append + Deduped | Yes |
:::note Deduplication doesn’t run in Legacy raw tables mode. Sync modes that normally deduplicate instead append every record to the raw table without deduplication. :::
Snowflake tutorials
After setting up the Snowflake destination connector, explore these Snowflake tutorials:
- Build a data ingestion pipeline from Mailchimp to Snowflake
- Replicate data from a PostgreSQL database to Snowflake
- Migrate your data from Redshift to Snowflake
- Orchestrate ELT pipelines with Prefect, Airbyte and dbt
Troubleshooting
’Current role does not have permissions on the target schema’
If you receive the Current role does not have permissions on the target schema error, check the Snowflake destination SCHEMA. The role you’ve provided must have permission to access it. When creating a connection, you may be able to select Mirror source structure for the Destination namespace. With some default examples and tutorials, this can make the connection write to a PUBLIC schema.
For a quick fix, change your connection’s ‘Replication’ setting from Mirror source structure to Destination Default. Alternatively, grant the role the required permissions in your chosen namespace.
Namespace support
This destination supports namespaces. The namespace maps to a Snowflake schema.
Changelog
Expand to review
| Version | Date | Pull Request | Subject |
|---|---|---|---|
| 5.2.2 | 2026-10-30 | 90225 | Create internal stages in the internal (raw_data_schema) schema instead of each output schema, so the role only needs CREATE STAGE on the internal schema. |
| 5.2.1 | 2026-10-22 | 89645 | Upgrade to Bulk CDK 1.1.9: fix critical CVEs in Apache MINA (mina-core 2.0.31), MINA SSHD 2.20.0 and BouncyCastle 1.86; netty 4.1.139; pin jsoup 1.23.2. |
| 5.2.0 | 2026-10-09 | 88417 | Add Programmatic Access Token as an authorization method. The token is passed to Snowflake in place of a password. |
| 5.1.2 | 2026-10-05 | 87720 | Allow custom domains in destination connections, consistent with Snowflake sources. |
| 5.1.1 | 2026-10-06 | 88143 | Fix HikariPool “Connection is not available” failures during the final flush by restoring bounded concurrency for Snowflake PUT/COPY operations. |
| 5.1.0 | 2026-10-01 | 87611 | Add optional Fusion S3 sync copies of loaded batches (off by default; enabled through environment configuration). |
| 5.0.1 | 2026-09-09 | 84953 | Add missing Airbyte meta columns (_airbyte_meta, _airbyte_generation_id) to tables created by connector versions prior to 3.10.0 when the AIRBYTE_DESTINATION_SNOWFLAKE_META_COLUMN_REPAIR env var is set to true (off by default), fixing “invalid identifier” sync failures after upgrading to 4.x. |
| 5.0.0 | 2026-09-02 | 85314 | Deprecate username/password authentication; key pair authentication is now the only recommended auth method. Username/password will be removed in a future release. |
| 4.1.2 | 2026-08-24 | 84979 | Upgrade CDK to 1.0.25 (prevents truncate-refresh retries from replacing a populated table with an empty one) |
| 4.1.1 | 2026-08-18 | 76313 | Handle ANSI reserved keywords as column names by prefixing with underscore |
| 4.1.0 | 2026-08-05 | 83713 | Add opt-in NUMBER(38,9) data type for number columns via the new “Decimal Data Type” option. |
| 4.0.49 | 2026-08-05 | 83740 | Upgrade CDK to 1.0.21 |
| 4.0.48 | 2026-07-23 | 82272 | Columns removed from the source schema are now preserved in the destination table instead of being dropped to prevent unintentional data loss due to source schema changes. |
| 4.0.47 | 2026-07-23 | 82294 | Replace ALTER TABLE SWAP WITH with CREATE OR REPLACE TABLE CLONE COPY GRANTS to preserve table grants |
| 4.0.46 | 2026-07-15 | 82104 | Use CREATE TABLE IF NOT EXISTS for non-replace table creation to prevent accidental data loss |
| 4.0.45 | 2026-07-10 | 81530 | Restore NULL-safe primary-key matching in dedup MERGE to fix duplicate rows when composite PKs contain NULLs |
| 4.0.44 | 2026-06-30 | 81346 | Remove unnecessary NULL PK equality checks from merge SQL |
| 4.0.43 | 2026-05-20 | 78231 | Upgrade CDK to 1.0.13 |
| 4.0.42 | 2026-05-14 | 77978 | Improve encrypted key-pair private key handling and error messages |
| 4.0.41 | 2026-05-07 | 77795 | Add option to preserve Snowflake whitespace |
| 4.0.40-rc.1 | 2026-04-27 | 76405 | Upgrade CDK to 1.0.9. Enable fast timestamp coercion. Progressive rollout. |
| 4.0.40 | 2026-05-01 | 77673 | Update the CDK to a version with default timestamp parsing |
| 4.0.39 | 2026-03-13 | 74715 | Drop temp table after successful upsert to prevent duplicate records |
| 4.0.38 | 2026-02-25 | 74041 | Upgrade CDK to 1.0.2 and base image to 2.0.4 for CVE patches |
| 4.0.37 | 2026-02-04 | 72854 | Internal interface changes |
| 4.0.36 | 2026-01-29 | 72417 | Handle exception in countTable correctly |
| 4.0.35 | 2026-01-26 | 72295 | Upgrade CDK to 0.2.0 |
| 4.0.34 | 2026-01-09 | 71273 | Fix check operation in raw tables only mode. |
| 4.0.33 | 2026-01-09 | 71248 | Upgrade to CDK 0.1.99 — limit final aggregate parallelism. |
| 4.0.32 | 2026-01-08 | 71233 | Promoting release candidate 4.0.32-rc.2 to a main version. |
| 4.0.32-rc.2 | 2025-12-19 | 71007 | Fix Raw Mode regression: Change _airbyte_data back to SnowflakeType.VARIANT |
| 4.0.32-rc.1 | 2025-12-18 | 70903 | Upgrade to CDK 0.1.91; internal refactoring |
| 4.0.31 | 2025-12-08 | 70442 | Write VARIANT values correctly when underlying Airbyte type is a union |
| 4.0.30 | 2025-11-24 | 69842 | Update documentation about numeric value handling |
| 4.0.29 | 2025-11-24 | 69342 | Truncate NumberValues and IntegerValues with excessive precision instead of nullifying them |
| 4.0.28 | 2025-11-13 | 69245 | Upgrade to CDK 0.1.78 |
| 4.0.27 | 2025-11-11 | 69285 | Remove spurious log messages |
| 4.0.26 | 2025-11-11 | 69117 | Upgrade to CDK 0.1.74 (internal code changes for schema evolution) |
| 4.0.25 | 2025-11-06 | 69226 | Improved additional statistics handling |
| 4.0.24 | 2025-11-05 | 69200 | Add support for observability metrics |
| 4.0.23 | 2025-11-03 | 69153 | Fix bug in connector spec |
| 4.0.22 | 2025-11-03 | 69147 | Upgrade to CDK 0.1.62 to improve handling of unrecognized JSON schema |
| 4.0.21 | 2025-11-03 | 69100 | Upgrade to CDK 0.1.61 to fix state index bug |
| 4.0.20 | 2025-10-29 | 68186 | Upgrade to CDK 0.1.59 |
| 4.0.19 | 2025-10-28 | 68683 | Upgrade to CDK 0.1.58 (improve logging of unflushed states at end of sync) |
| 4.0.18 | 2025-10-28 | 68125 | Internal refactoring; upgrade to CDK 0.1.56 |
| 4.0.17 | 2025-10-22 | 68585 | Wrap Snowflake permission errors as ConfigErrorException for better error handling |
| 4.0.16 | 2025-10-21 | 68516 | Ensure columns are marked as non-nullable in destination schema. |
| 4.0.15 | 2025-10-21 | 67153 | Implement new proto schema implementation |
| 4.0.14 | 2025-10-16 | 68148 | No user-facing changes. Internal code reorganization. |
| 4.0.13 | 2025-10-15 | 68106 | Revert cache change to fix performance issue. |
| 4.0.12 | 2025-10-15 | 68096 | Cache Airbyte metadata data column checks during formatting to improve performance. |
| 4.0.11 | 2025-10-14 | 67721 | Handle edge case in config migrator; improve test coverage. |
| 4.0.10 | 2025-10-13 | 67714 | Update check to handle QUOTED_IDENTIFIERS_IGNORE_CASE=true correctly. |
| 4.0.9 | 2025-10-10 | 67610 | Fix an issue with varchar size validation |
| 4.0.8 | 2025-10-10 | 67599 | Improve handling of heavily interleaved streams. |
| 4.0.7 | 2025-10-09 | 67590 | Use GZIP compression level 5 to improve performance. No longer explicitly CREATE FILE FORMAT. |
| 4.0.6 | 2025-10-09 | 67582 | Schema evolution supports dropping columns with lowercase characters in their name. |
| 4.0.5 | 2025-10-09 | 67575 | Revert inadvertent type changes. |
| 4.0.4 | 2025-10-08 | 67569 | Prevent crashes when a column value ends with \. |
| 4.0.3 | 2025-10-08 | 67556 | Improve performance and reduce cost by increasing maximum parallel processing. |
| 4.0.2 | 2025-10-07 | 67301 | Improve performance and reduce cost by caching SHOW COLUMNS output. |
| 4.0.1 | 2025-10-06 | 67106 | Removes unnecessary operations and allocations in value validator. |
| 4.0.0 | 2025-10-06 | 66747 | Upgrade to direct-load tables; add option for soft CDC deletes. |
| 3.15.11-rc.2 | 2025-09-29 | 66753 | Pin to CDK artifact |
| 3.15.11-rc.1 | 2025-09-25 | 66307 | Initial Direct Load RC release |
| 3.15.10 | 2025-06-13 | 61588 | Publish version to account for possible duplicate publishing in pipeline. Noop change. |
| 3.15.9 | 2025-05-16 | 60328 | Migrate to base 2.0.2. |
| 3.15.8 | 2025-05-02 | 59222 | Upgrade libraries for security patches. |
| 3.15.7 | 2025-04-24 | 59166 | Upgrade libraries for security patches. |
| 3.15.6 | 2025-04-24 | 58652 | Upgrade libraries for security patches. |
| 3.15.5 | 2025-03-24 | 56355 | Upgrade to airbyte/java-connector-base:2.0.1 to be M4 compatible. |
| 3.15.4 | 2025-01-10 | 51503 | Use a non root base image |
| 3.15.3 | 2024-12-18 | 49913 | Use a base image: airbyte/java-connector-base:1.0.0 |
| 3.15.2 | 2024-10-31 | #48070 | upgrade JDBC driver to 3.20.0 |
| 3.15.1 | 2024-10-20 | #46989 | add snowflake transaction wrapper for rollback support |
| 3.15.0 | 2024-09-18 | #45437 | upgrade all dependencies |
| 3.14.0 | 2024-09-18 | #45431 | truncate large records queries |
| 3.13.0 | 2024-09-17 | #45422 | speed up metadata queries |
| 3.12.0 | 2024-09-17 | #38585 | force UTF8 collation when creating schemas and tables |
| 3.11.12 | 2024-09-12 | #45370 | fix a race condition in our orphanedThreadFilter |
| 3.11.11 | 2024-08-20 | #44476 | Increase message parsing limit to 100mb |
| 3.11.10 | 2024-08-22 | #44526 | Revert protocol compliance fix |
| 3.11.9 | 2024-08-19 | #43367 | Add opt in using MERGE statement for upserts and deletes |
| 3.11.8 | 2024-08-16 | #42505 | Fix bug in refreshes logic (already mitigated in platform, just fixing protocol compliance) |
| 3.11.7 | 2024-08-09 | #43440 | remove contention on state table by deleting rows ony once every 100 updates |
| 3.11.6 | 2024-08-09 | #43332 | bump Java CDK |
| 3.11.5 | 2024-08-07 | #43348 | SnowflakeSqlGen cleanup to Kotlin string interpolation |
| 3.11.4 | 2024-07-18 | #41940 | Update host regex to allow connecting to LocalStack Snowflake |
| 3.11.3 | 2024-07-15 | #41968 | Don’t hang forever on empty stream list; shorten error message on INCOMPLETE stream status |
| 3.11.2 | 2024-07-12 | #41674 | Upgrade to latest CDK |
| 3.11.1 | 2024-07-08 | #41041 | Fix resume logic in truncate refreshes to prevent data loss |
| 3.11.0 | 2024-06-25 | #39473 | Support for refreshes and resumable full refresh. WARNING: You must upgrade to platform 0.63.7 before upgrading to this connector version. |
| 3.10.1 | 2024-06-11 | #39399 | Bug fix for _airbyte_meta not migrated in OVERWRITE mode |
| 3.10.0 | 2024-06-10 | #39107 | _airbyte_meta and _airbyte_generation_id in Raw tables and final tables |
| 3.9.1 | 2024-06-05 | #39135 | Improved error handling for Staging files |
| 3.9.0 | 2024-05-23 | #38658 | Adapting to newer interfaces from #38107 |
| 3.8.4 | 2024-05-23 | #38632 | convert all tests to kotlin |
| 3.8.3 | 2024-05-23 | #38586 | Bump CDK version |
| 3.8.2 | 2024-05-22 | #38553 | Remove SwitchingDestination and AbstractJdbcDestination dependency in destination |
| 3.8.1 | 2024-05-22 | #38568 | Adopt latest CDK |
| 3.8.0 | 2024-05-08 | #37715 | Remove option for incremental typing and deduping |
| 3.7.4 | 2024-05-07 | #38052 | Revert problematic optimization |
| 3.7.3 | 2024-05-07 | #34612 | Adopt CDK 0.33.2 |
| 3.7.2 | 2024-05-06 | #37857 | Use safe executeMetadata call |
| 3.7.1 | 2024-04-30 | #36910 | Bump CDK version |
| 3.7.0 | 2024-04-08 | #35754 | Allow configuring data_retention_time_in_days; apply to both raw and final tables. Note: Existing tables will not be affected; you must manually alter them. |
| 3.6.6 | 2024-03-26 | #36466 | Correctly hhandle instances with QUOTED_IDENTIFIERS_IGNORE_CASE enabled globally |
| 3.6.5 | 2024-03-25 | #36461 | Internal code change (use published CDK artifact instead of source dependency) |
| 3.6.4 | 2024-03-25 | #36396 | Handle instances with QUOTED_IDENTIFIERS_IGNORE_CASE enabled globally |
| 3.6.3 | 2024-03-25 | #36452 | Remove Query timeout |
| 3.6.2 | 2024-03-18 | #36240 | Hide oAuth config option |
| 3.6.1 | 2024-03-07 | #35899 | Adopt CDK 0.23.18; Null safety check in state parsing |
| 3.6.0 | 2024-03-06 | #35308 | Upgrade CDK; use utc tz for extracted_at; Migrate existing extracted_at to utc; |
| 3.5.14 | 2024-02-22 | #35456 | Adopt CDK 0.23.0; Gather initial state upfront, reduce information_schema calls |
| 3.5.13 | 2024-02-22 | #35569 | Fix logging bug. |
| 3.5.12 | 2024-02-15 | #35240 | Adopt CDK 0.20.9 |
| 3.5.11 | 2024-02-12 | #35194 | Reorder auth options |
| 3.5.10 | 2024-02-12 | #35144 | Adopt CDK 0.20.2 |
| 3.5.9 | 2024-02-12 | #35111 | Adopt CDK 0.20.1 |
| 3.5.8 | 2024-02-09 | #34574 | Adopt CDK 0.20.0 |
| 3.5.7 | 2024-02-08 | #34747 | Adopt CDK 0.19.0 |
| 3.5.6 | 2024-02-08 | #35027 | Upgrade CDK to version 0.17.1 |
| 3.5.5 | 2024-02-08 | #34502 | Reduce COPY frequency |
| 3.5.4 | 2024-01-24 | #34451 | Improve logging for unparseable input |
| 3.5.3 | 2024-01-25 | #34528 | Fix spurious check failure (UnsupportedOperationException: Snowflake does not use the native JDBC DV2 interface) |
| 3.5.2 | 2024-01-24 | #34458 | Improve error reporting |
| 3.5.1 | 2024-01-24 | #34501 | Internal code changes for Destinations V2 |
| 3.5.0 | 2024-01-24 | #34462 | Upgrade CDK to 0.14.0 |
| 3.4.22 | 2024-01-12 | #34227 | Upgrade CDK to 0.12.0; Cleanup unused dependencies |
| 3.4.21 | 2024-01-10 | #34083 | Emit destination stats as part of the state message |
| 3.4.20 | 2024-01-05 | #33948 | Skip retrieving initial table state when setup fails |
| 3.4.19 | 2024-01-04 | #33730 | Internal code structure changes |
| 3.4.18 | 2024-01-02 | #33728 | Add option to only type and dedupe at the end of the sync |
| 3.4.17 | 2023-12-20 | #33704 | Update to java CDK 0.10.0 (no changes) |
| 3.4.16 | 2023-12-18 | #33124 | Make Schema Creation Seperate from Table Creation |
| 3.4.15 | 2023-12-13 | #33232 | Only run typing+deduping for a stream if the stream had any records |
| 3.4.14 | 2023-12-08 | #33263 | Adopt java CDK version 0.7.0 |
| 3.4.13 | 2023-12-05 | #32326 | Use jdbc metadata for table existence check |
| 3.4.12 | 2023-12-04 | #33084 | T&D SQL statements moved to debug log level |
| 3.4.11 | 2023-11-14 | #32526 | Clean up memory manager logs. |
| 3.4.10 | 2023-11-08 | #32125 | Fix compilation warnings. |
| 3.4.9 | 2023-11-06 | #32026 | Add separate TRY_CAST transaction to reduce compute usage |
| 3.4.8 | 2023-11-06 | #32190 | Further improve error reporting |
| 3.4.7 | 2023-11-06 | #32193 | Adopt java CDK version 0.4.1. |
| 3.4.6 | 2023-11-02 | #32124 | Revert merge statement |
| 3.4.5 | 2023-11-02 | #31983 | Improve error reporting |
| 3.4.4 | 2023-10-30 | #31985 | Delay upgrade deadline to Nov 7 |
| 3.4.3 | 2023-10-30 | #31960 | Adopt java CDK version 0.2.0. |
| 3.4.2 | 2023-10-27 | #31897 | Further filtering on extracted_at |
| 3.4.1 | 2023-10-27 | #31683 | Performance enhancement (switch to a merge statement for incremental-dedup syncs) |
| 3.4.0 | 2023-10-25 | #31686 | Opt out flag for typed and deduped tables |
| 3.3.0 | 2023-10-25 | #31520 | Stop deduping raw table |
| 3.2.3 | 2023-10-17 | #31191 | Improve typing+deduping performance by filtering new raw records on extracted_at |
| 3.2.2 | 2023-10-10 | #31194 | Deallocate unused per stream buffer memory when empty |
| 3.2.1 | 2023-10-10 | #31083 | Fix precision of numeric values in async destinations |
| 3.2.0 | 2023-10-09 | #31149 | No longer fail syncs when PKs are null - try do dedupe anyway |
| 3.1.22 | 2023-10-06 | #31153 | Increase jvm GC retries |
| 3.1.21 | 2023-10-06 | #31139 | Bump CDK version |
| 3.1.20 | 2023-10-06 | #31129 | Reduce async buffer size |
| 3.1.19 | 2023-10-04 | #31082 | Revert null PK checks |
| 3.1.18 | 2023-10-01 | #30779 | Final table PK columns become non-null and skip check for null PKs in raw records (performance) |
| 3.1.17 | 2023-09-29 | #30938 | Upgrade snowflake-jdbc driver |
| 3.1.16 | 2023-09-28 | #30835 | Fix regression from 3.1.15 in supporting concurrent syncs with identical stream name but different namespace |
| 3.1.15 | 2023-09-26 | #30775 | Increase async block size |
| 3.1.14 | 2023-09-27 | #30739 | Fix column name collision detection |
| 3.1.13 | 2023-09-19 | #30599 | Support concurrent syncs with identical stream name but different namespace |
| 3.1.12 | 2023-09-21 | #30671 | Reduce async buffer size |
| 3.1.11 | 2023-09-19 | #30592 | Internal code changes |
| 3.1.10 | 2023-09-18 | #30546 | Make sure that the async buffer are flush every 5 minutes |
| 3.1.9 | 2023-09-19 | #30319 | Support column names that are reserved |
| 3.1.8 | 2023-09-18 | #30479 | Fix async memory management |
| 3.1.7 | 2023-09-15 | #30491 | Improve error message display |
| 3.1.6 | 2023-09-14 | #30439 | Fix a transient error |
| 3.1.5 | 2023-09-13 | #30416 | Support ${ in stream name/namespace, and in column names |
| 3.1.4 | 2023-09-12 | #30364 | Add log message |
| 3.1.3 | 2023-08-29 | #29878 | Reenable incremental typing and deduping |
| 3.1.2 | 2023-08-31 | #30020 | Run typing and deduping tasks in parallel |
| 3.1.1 | 2023-09-05 | #30117 | Type and Dedupe at sync start and then every 6 hours |
| 3.1.0 | 2023-09-01 | #30056 | Upcase final table names to allow case-insensitive references |
| 3.0.2 | 2023-09-01 | #30121 | Improve performance on very wide streams by skipping TRY_CAST on strings |
| 3.0.1 | 2023-08-27 | #30065 | Clearer error thrown when records are missing a primary key |
| 3.0.0 | 2023-08-27 | #29783 | Destinations V2 |
| 2.1.7 | 2023-08-29 | #29949 | Destinations V2: Fix checking for empty table by ensuring upper-case DB names |
| 2.1.6 | 2023-08-28 | #29878 | Destinations V2: Fix detection of existing table by ensuring upper-case DB names |
| 2.1.5 | 2023-08-28 | #29903 | Destinations V2: Performance Improvement, Changing Metadata error array construction from ARRAY_CAT to ARRAY_CONSTRUCT_COMPACT |
| 2.1.4 | 2023-08-28 | #29903 | Abort queries on crash |
| 2.1.3 | 2023-08-25 | #29881 | Destinations v2: Only run T+D once at end of sync, to prevent data loss under async conditions |
| 2.1.2 | 2023-08-24 | #29805 | Destinations v2: Don’t soft reset in migration |
| 2.1.1 | 2023-08-23 | #29774 | Destinations v2: Don’t soft reset overwrite syncs |
| 2.1.0 | 2023-08-21 | #29636 | Destinations v2: Several Critical Bug Fixes (cursorless dedup, improved floating-point handling, improved special characters handling; improved error handling) |
| 2.0.0 | 2023-08-09 | #28894 | Remove support for Snowflake GCS/S3 loading method in favor of Snowflake Internal staging |
| 1.3.3 | 2023-08-15 | #29461 | Changing a static constant reference |
| 1.3.2 | 2023-08-11 | #29381 | Destinations v2: Add support for streams with no columns |
| 1.3.1 | 2023-08-04 | #28894 | Destinations v2: Update SqlGenerator |
| 1.3.0 | 2023-08-07 | #29174 | Destinations v2: early access release |
| 1.2.10 | 2023-08-07 | #29188 | Internal code refactoring |
| 1.2.9 | 2023-08-04 | #28677 | Destinations v2: internal code changes to prepare for early access release |
| 1.2.8 | 2023-08-03 | #29047 | Avoid logging record if the format is invalid |
| 1.2.7 | 2023-08-02 | #28976 | Fix composite PK handling in v1 mode |
| 1.2.6 | 2023-08-01 | #28618 | Reduce logging noise |
| 1.2.5 | 2023-07-24 | #28618 | Add hooks in preparation for destinations v2 implementation |
| 1.2.4 | 2023-07-21 | #28584 | Install dependencies in preparation for destinations v2 work |
| 1.2.3 | 2023-07-21 | #28345 | Pull in async framework minor bug fix for race condition on state emission |
| 1.2.2 | 2023-07-14 | #28345 | Increment patch to trigger a rebuild |
| 1.2.1 | 2023-07-14 | #28315 | Pull in async framework minor bug fix to avoid Snowflake hanging on close |
| 1.2.0 | 2023-07-5 | #27935 | Enable Faster Snowflake Syncs with Asynchronous writes |
| 1.1.0 | 2023-06-27 | #27781 | License Update: Elv2 |
| 1.0.6 | 2023-06-21 | #27555 | Reduce image size |
| 1.0.5 | 2023-05-31 | #25782 | Internal scaffolding for future development |
| 1.0.4 | 2023-05-19 | #26323 | Prevent infinite retry loop under specific circumstances |
| 1.0.3 | 2023-05-15 | #26081 | Reverts splits bases |
| 1.0.2 | 2023-05-05 | #25649 | Splits bases (reverted) |
| 1.0.1 | 2023-04-29 | #25570 | Internal library update |
| 1.0.0 | 2023-05-02 | #25739 | Removed Azure Blob Storage as a loading method |
| 0.4.63 | 2023-04-27 | #25346 | Added FlushBufferFunction interface |
| 0.4.61 | 2023-03-30 | #24736 | Improve behavior when throttled by AWS API |
| 0.4.60 | 2023-03-30 | #24698 | Add option in spec to allow increasing the stream buffer size to 50 |
| 0.4.59 | 2023-03-23 | #23904 | Fail faster in certain error cases |
| 0.4.58 | 2023-03-27 | #24615 | Fixed host validation by pattern on UI |
| 0.4.56 (broken) | 2023-03-22 | #23904 | Added host validation by pattern on UI |
| 0.4.54 | 2023-03-17 | #23788 | S3-Parquet: added handler to process null values in arrays |
| 0.4.53 | 2023-03-15 | #24058 | added write attempt to internal staging Check method |
| 0.4.52 | 2023-03-10 | #23931 | Added support for periodic buffer flush |
| 0.4.51 | 2023-03-10 | #23466 | Changed S3 Avro type from Int to Long |
| 0.4.49 | 2023-02-27 | #23360 | Added logging for flushing and writing data to destination storage |
| 0.4.48 | 2023-02-23 | #22877 | Add handler for IP not in whitelist error and more handlers for insufficient permission error |
| 0.4.47 | 2023-01-30 | #21912 | Catch “Create” Table and Stage Known Permissions and rethrow as ConfigExceptions |
| 0.4.46 | 2023-01-26 | #20631 | Added support for destination checkpointing with staging |
| 0.4.45 | 2023-01-25 | #21087 | Catch Known Permissions and rethrow as ConfigExceptions |
| 0.4.44 | 2023-01-20 | #21087 | Wrap Authentication Errors as Config Exceptions |
| 0.4.43 | 2023-01-20 | #21450 | Updated Check methods to handle more possible s3 and gcs stagings issues |
| 0.4.42 | 2023-01-12 | #21342 | Better handling for conflicting destination streams |
| 0.4.41 | 2022-12-16 | #20566 | Improve spec to adhere to standards |
| 0.4.40 | 2022-11-11 | #19302 | Set jdbc application env variable depends on env - airbyte_oss or airbyte_cloud |
| 0.4.39 | 2022-11-09 | #18970 | Updated “check” connection method to handle more errors |
| 0.4.38 | 2022-09-26 | #17115 | Added connection string identifier |
| 0.4.37 | 2022-09-21 | #16839 | Update JDBC driver for Snowflake to 3.13.19 |
| 0.4.36 | 2022-09-14 | #15668 | Wrap logs in AirbyteLogMessage |
| 0.4.35 | 2022-09-01 | #16243 | Fix Json to Avro conversion when there is field name clash from combined restrictions (anyOf, oneOf, allOf fields). |
| 0.4.34 | 2022-07-23 | #14388 | Add support for key pair authentication |
| 0.4.33 | 2022-07-15 | #14494 | Make S3 output filename configurable. |
| 0.4.32 | 2022-07-14 | #14618 | Removed additionalProperties: false from JDBC destination connectors |
| 0.4.31 | 2022-07-07 | #13729 | Improve configuration field description |
| 0.4.30 | 2022-06-24 | #14114 | Remove “additionalProperties”: false from specs for connectors with staging |
| 0.4.29 | 2022-06-17 | #13753 | Deprecate and remove PART_SIZE_MB fields from connectors based on StreamTransferManager |
| 0.4.28 | 2022-05-18 | #12952 | Apply buffering strategy on GCS staging |
| 0.4.27 | 2022-05-17 | #12820 | Improved ‘check’ operation performance |
| 0.4.26 | 2022-05-12 | #12805 | Updated to latest base-java to emit AirbyteTraceMessages on error. |
| 0.4.25 | 2022-05-03 | #12452 | Add support for encrypted staging on S3; fix the purge_staging_files option |
| 0.4.24 | 2022-03-24 | #11093 | Added OAuth support (Compatible with Airbyte Version 0.35.60+) |
| 0.4.22 | 2022-03-18 | #10793 | Fix namespace with invalid characters |
| 0.4.21 | 2022-03-18 | #11071 | Switch to compressed on-disk buffering before staging to s3/internal stage |
| 0.4.20 | 2022-03-14 | #10341 | Add Azure blob staging support |
| 0.4.19 | 2022-03-11 | #10699 | Added unit tests |
| 0.4.17 | 2022-02-25 | #10421 | Refactor JDBC parameters handling |
| 0.4.16 | 2022-02-25 | #10627 | Add try catch to make sure all handlers are closed |
| 0.4.15 | 2022-02-22 | #10459 | Add FailureTrackingAirbyteMessageConsumer |
| 0.4.14 | 2022-02-17 | #10394 | Reduce memory footprint. |
| 0.4.13 | 2022-02-16 | #10212 | Execute COPY command in parallel for S3 and GCS staging |
| 0.4.12 | 2022-02-15 | #10342 | Use connection pool, and fix connection leak. |
| 0.4.11 | 2022-02-14 | #9920 | Updated the size of staging files for S3 staging. Also, added closure of S3 writers to staging files when data has been written to an staging file. |
| 0.4.10 | 2022-02-14 | #10297 | Halve the record buffer size to reduce memory consumption. |
| 0.4.9 | 2022-02-14 | #10256 | Add ExitOnOutOfMemoryError JVM flag. |
| 0.4.8 | 2022-02-01 | #9959 | Fix null pointer exception from buffered stream consumer. |
| 0.4.7 | 2022-01-29 | #9745 | Integrate with Sentry. |
| 0.4.6 | 2022-01-28 | #9623 | Add jdbc_url_params support for optional JDBC parameters |
| 0.4.5 | 2021-12-29 | #9184 | Update connector fields title/description |
| 0.4.4 | 2022-01-24 | #9743 | Fixed bug with dashes in schema name |
| 0.4.3 | 2022-01-20 | #9531 | Start using new S3StreamCopier and expose the purgeStagingData option |
| 0.4.2 | 2022-01-10 | #9141 | Fixed duplicate rows on retries |
| 0.4.1 | 2021-01-06 | #9311 | Update сreating schema during check |
| 0.4.0 | 2021-12-27 | #9063 | Updated normalization to produce permanent tables |
| 0.3.24 | 2021-12-23 | #8869 | Changed staging approach to Byte-Buffered |
| 0.3.23 | 2021-12-22 | #9039 | Added part_size configuration in UI for S3 loading method |
| 0.3.22 | 2021-12-21 | #9006 | Updated jdbc schema naming to follow Snowflake Naming Conventions |
| 0.3.21 | 2021-12-15 | #8781 | Updated check method to verify permissions to create/drop stage for internal staging; compatibility fix for Java 17 |
| 0.3.20 | 2021-12-10 | #8562 | Moving classes around for better dependency management; compatibility fix for Java 17 |
| 0.3.19 | 2021-12-06 | #8528 | Set Internal Staging as default choice |
| 0.3.18 | 2021-11-26 | #8253 | Snowflake Internal Staging Support |
| 0.3.17 | 2021-11-08 | #7719 | Improve handling of wide rows by buffering records based on their byte size rather than their count |
| 0.3.15 | 2021-10-11 | #6949 | Each stream was split into files of 10,000 records each for copying using S3 or GCS |
| 0.3.14 | 2021-09-08 | #5924 | Fixed AWS S3 Staging COPY is writing records from different table in the same raw table |
| 0.3.13 | 2021-09-01 | #5784 | Updated query timeout from 30 minutes to 3 hours |
| 0.3.12 | 2021-07-30 | #5125 | Enable additionalPropertities in spec.json |
| 0.3.11 | 2021-07-21 | #3555 | Partial Success in BufferedStreamConsumer |
| 0.3.10 | 2021-07-12 | #4713 | Tag traffic with airbyte label to enable optimization opportunities from Snowflake |