logistics

airbytehq · Aug 23, 2023 · 4d10768 · 4d10768
1 parent d9aa4d1
commit 4d10768
Show file tree

Hide file tree

Showing 9 changed files with 45 additions and 26 deletions.
diff --git a/airbyte-integrations/connectors/destination-bigquery/Dockerfile b/airbyte-integrations/connectors/destination-bigquery/Dockerfile
@@ -47,7 +47,7 @@ ENV AIRBYTE_NORMALIZATION_INTEGRATION bigquery
 
 COPY --from=build /airbyte /airbyte
 
-LABEL io.airbyte.version=1.10.1
+LABEL io.airbyte.version=2.0.0
 LABEL io.airbyte.name=airbyte/destination-bigquery
 
 ENV AIRBYTE_ENTRYPOINT "/airbyte/run_with_normalization.sh"

diff --git a/airbyte-integrations/connectors/destination-bigquery/metadata.yaml b/airbyte-integrations/connectors/destination-bigquery/metadata.yaml
@@ -2,16 +2,12 @@ data:
   connectorSubtype: database
   connectorType: destination
   definitionId: 22f6c74f-5699-40ff-833c-4a879ea40133
-  dockerImageTag: 1.10.1
+  dockerImageTag: 2.0.0
   dockerRepository: airbyte/destination-bigquery
   githubIssueLabel: destination-bigquery
   icon: bigquery.svg
   license: ELv2
   name: BigQuery
-  normalizationConfig:
-    normalizationIntegrationType: bigquery
-    normalizationRepository: airbyte/normalization
-    normalizationTag: 0.4.3
   registries:
     cloud:
       enabled: true
@@ -24,6 +20,11 @@ data:
         resourceRequirements:
           memory_limit: 1Gi
           memory_request: 1Gi
+  releases:
+    breakingChanges:
+      2.0.0:
+        message: Destinations V2 includes enhanced final table structures, better error handling, and other usability improvements. Learn more about what's new [here](https://docs.airbyte.com/understanding-airbyte/typing-deduping) and how to upgrade [here](https://docs.airbyte.com/release_notes/upgrading_to_destinations_v2). This breaking change will change the format of your final tables.
+        upgradeDeadline: "2023-11-01"
   documentationUrl: https://docs.airbyte.com/integrations/destinations/bigquery
   supportsDbt: true
   tags:

diff --git a/airbyte-integrations/connectors/destination-snowflake/Dockerfile b/airbyte-integrations/connectors/destination-snowflake/Dockerfile
@@ -49,7 +49,7 @@ RUN tar xf ${APPLICATION}.tar --strip-components=1
 ENV ENABLE_SENTRY true
 
 
-LABEL io.airbyte.version=2.1.1
+LABEL io.airbyte.version=3.0.0
 LABEL io.airbyte.name=airbyte/destination-snowflake
 
 ENV AIRBYTE_ENTRYPOINT "/airbyte/run_with_normalization.sh"

diff --git a/airbyte-integrations/connectors/destination-snowflake/metadata.yaml b/airbyte-integrations/connectors/destination-snowflake/metadata.yaml
@@ -2,16 +2,12 @@ data:
   connectorSubtype: database
   connectorType: destination
   definitionId: 424892c4-daac-4491-b35d-c6688ba547ba
-  dockerImageTag: 2.1.1
+  dockerImageTag: 3.0.0
   dockerRepository: airbyte/destination-snowflake
   githubIssueLabel: destination-snowflake
   icon: snowflake.svg
   license: ELv2
   name: Snowflake
-  normalizationConfig:
-    normalizationIntegrationType: snowflake
-    normalizationRepository: airbyte/normalization-snowflake
-    normalizationTag: 0.4.3
   registries:
     cloud:
       enabled: true
@@ -33,6 +29,9 @@ data:
       2.0.0:
         message: "Remove GCS/S3 loading method support."
         upgradeDeadline: "2023-08-31"
+      3.0.0:
+        message: Destinations V2 includes enhanced final table structures, better error handling, and other usability improvements. Learn more about what's new [here](https://docs.airbyte.com/understanding-airbyte/typing-deduping) and how to upgrade [here](https://docs.airbyte.com/release_notes/upgrading_to_destinations_v2). This breaking change will change the format of your final tables.
+        upgradeDeadline: "2023-11-01"
   ab_internal:
     sl: 200
     ql: 400

diff --git a/docs/integrations/destinations/bigquery-migrations.md b/docs/integrations/destinations/bigquery-migrations.md
@@ -0,0 +1,12 @@
+# BigQuery Migration Guide
+
+## Upgrading to 2.0.0
+
+Destinations V2 includes enhanced final table structures, better error handling, and other usability improvements. Learn more about what's new [here](/understanding-airbyte/typing-deduping) and how to upgrade [here](/release_notes/upgrading_to_destinations_v2). This breaking change will change the format of your final tables.
+
+Worthy of specific mention:
+
+- Per-record error handling
+- Clearer table structure
+- Removal of sub-tables for nested properties
+- Removal of SCD tables
diff --git a/docs/integrations/destinations/bigquery.md b/docs/integrations/destinations/bigquery.md
@@ -135,6 +135,7 @@ Now that you have set up the BigQuery destination connector, check out the follo
 
 | Version | Date       | Pull Request                                               | Subject                                                                                                                                                         |
 |:--------|:-----------|:-----------------------------------------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 2.0.0   | 2023-08-27 | [29783](https://github.com/airbytehq/airbyte/pull/29783)   | Destinations V2                                                                                                          |
 | 1.10.1  | 2023-08-23 | [\#29774](https://github.com/airbytehq/airbyte/pull/29774) | Destinations v2: Don't soft reset overwrite syncs                                                                                                               |
 | 1.10.0  | 2023-08-21 | [\#29636](https://github.com/airbytehq/airbyte/pull/29636) | Destinations v2: Several Critical Bug Fixes (cursorless dedup, improved floating-point handling, improved special characters handling; improved error handling) |
 | 1.9.1   | 2023-08-21 | [\#28687](https://github.com/airbytehq/airbyte/pull/28687) | Under the hood: Add dependency on Java CDK v0.0.1.                                                                                                              |

diff --git a/docs/integrations/destinations/snowflake-migrations.md b/docs/integrations/destinations/snowflake-migrations.md
@@ -1,4 +1,16 @@
 # Snowflake Migration Guide
 
+## Upgrading to 3.0.0
+
+Destinations V2 includes enhanced final table structures, better error handling, and other usability improvements. Learn more about what's new [here](/understanding-airbyte/typing-deduping) and how to upgrade [here](/release_notes/upgrading_to_destinations_v2). This breaking change will change the format of your final tables.
+
+Worthy of specific mention:
+
+- Per-record error handling
+- Clearer table structure
+- Removal of sub-tables for nested properties
+- Removal of SCD tables
+
 ## Upgrading to 2.0.0
+
 Snowflake no longer supports GCS/S3. Please migrate to the Internal Staging option. This is recommended by Snowflake and is cheaper and faster.
diff --git a/docs/integrations/destinations/snowflake.md b/docs/integrations/destinations/snowflake.md
@@ -271,6 +271,7 @@ Otherwise, make sure to grant the role the required permissions in the desired n
 
 | Version         | Date       | Pull Request                                               | Subject                                                                                                                                                         |
 |:----------------|:-----------|:-----------------------------------------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 3.0.0           | 2023-08-27 | [29783](https://github.com/airbytehq/airbyte/pull/29783)   | Destinations V2                                                                                                                                     |
 | 2.1.1           | 2023-08-23 | [\#29774](https://github.com/airbytehq/airbyte/pull/29774) | Destinations v2: Don't soft reset overwrite syncs                                                                                                               |
 | 2.1.0           | 2023-08-21 | [\#29636](https://github.com/airbytehq/airbyte/pull/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](https://github.com/airbytehq/airbyte/pull/29236) | Remove support for Snowflake GCS/S3 loading method in favor of Snowflake Internal staging                                                                       |

diff --git a/docs/release_notes/upgrading_to_destinations_v2.md b/docs/release_notes/upgrading_to_destinations_v2.md
@@ -51,12 +51,6 @@ After upgrading the out-of-date destination to a [Destinations V2 compatible ver
 4. The new raw tables will be typed and de-duplicated according to the Destinations V2 format.
 5. Once typing and de-duplication has completed successfully, your previous final table will be replaced with the updated data.
 
-:::note
-
-The first sync after the upgade to Destination V2 will be longer than normal, as your tables will be migrated to the new format.  After the migtration, subsequent syncs will return to thier normal speed. 
-
-:::
-
 Pre-existing raw tables, SCD tables and "unnested" tables will always be left untouched. You can delete these at your convenience, but these tables will no longer be kept up-to-date by Airbyte syncs.
 Each destination version is managed separately, so if you have multiple destinations, they all need to be upgraded one by one.
 
@@ -147,7 +141,7 @@ For each destination connector, Destinations V2 is effective as of the following
 | Destination Connector | Safe Rollback Version | Destinations V2 Compatible |
 | --------------------- | --------------------- | -------------------------- |
 | BigQuery              | 1.4.4                 | 2.0.0+                     |
-| Snowflake             | 0.4.1                 | 2.0.0+                     |
+| Snowflake             | 2.0.0                 | 3.0.0+                     |
 | Redshift              | 0.4.8                 | 2.0.0+                     |
 | MSSQL                 | 0.1.24                | 2.0.0+                     |
 | MySQL                 | 0.1.20                | 2.0.0+                     |
@@ -156,18 +150,17 @@ For each destination connector, Destinations V2 is effective as of the following
 | DuckDB                | 0.1.0                 | 2.0.0+                     |
 | Clickhouse            | 0.2.3                 | 2.0.0+                     |
 
-## Destinations V2 Implementation Differences 
+## Destinations V2 Implementation Differences
 
 In addtion to the the common fixes for all destinations described above, there are some per-destination fixes and updates included in Destinations V2:
 
 ### BigQuery
 
-1. [Object and array properties](https://docs.airbyte.com/understanding-airbyte/supported-data-types/#the-types) are properly stored as JSON columns.  Previously, we had used TEXT, which made querying sub-properties more difficult.
-     * In certain cases, numbers within sub-properties with long decimal values will need to be converted to float representations due to a *quirk* of Bigquery.  Learn more [here](https://github.com/airbytehq/airbyte/issues/29594). 
+1. [Object and array properties](https://docs.airbyte.com/understanding-airbyte/supported-data-types/#the-types) are properly stored as JSON columns. Previously, we had used TEXT, which made querying sub-properties more difficult.
+   - In certain cases, numbers within sub-properties with long decimal values will need to be converted to float representations due to a _quirk_ of Bigquery. Learn more [here](https://github.com/airbytehq/airbyte/issues/29594).
 
 ### Snowflake
 
-1. `destination-snowflake` is now case sensitive, and was not previously.  This means that if you have a source stream "users", `destination-snowflake` would have previously created a "USERS" table in your data warehouse.  We now correctly create a "users" table.
-    * Note that to properly query case-sensitive tables and columns in Snowflake, you will need to quote your table and column names, e.g. `select "first_name" from "users";`
-    * If you are migrating from Destinations v1 to Destinations V2, we will leave your old "USERS" table, and create a new "users" table - please note the case sensitivity.
-
+1. `destination-snowflake` is now case sensitive, and was not previously. This means that if you have a source stream "users", `destination-snowflake` would have previously created a "USERS" table in your data warehouse. We now correctly create a "users" table.
+   - Note that to properly query case-sensitive tables and columns in Snowflake, you will need to quote your table and column names, e.g. `select "first_name" from "users";`
+   - If you are migrating from Destinations v1 to Destinations V2, we will leave your old "USERS" table, and create a new "users" table - please note the case sensitivity.