From 60d0b1b68355b685101e3df7ea76226267baabad Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Piotr=20Poniedzia=C5=82ek?= Date: Mon, 13 May 2024 10:07:39 +0200 Subject: [PATCH] Update docs/pipeline-components-and-applications/loaders-storage-targets/bigquery-loader/upgrade-guides/2-0-0-upgrade-guide/index.md Co-authored-by: Nick --- .../upgrade-guides/2-0-0-upgrade-guide/index.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/pipeline-components-and-applications/loaders-storage-targets/bigquery-loader/upgrade-guides/2-0-0-upgrade-guide/index.md b/docs/pipeline-components-and-applications/loaders-storage-targets/bigquery-loader/upgrade-guides/2-0-0-upgrade-guide/index.md index 2b5d6c7346..3896f4a7b0 100644 --- a/docs/pipeline-components-and-applications/loaders-storage-targets/bigquery-loader/upgrade-guides/2-0-0-upgrade-guide/index.md +++ b/docs/pipeline-components-and-applications/loaders-storage-targets/bigquery-loader/upgrade-guides/2-0-0-upgrade-guide/index.md @@ -124,9 +124,10 @@ Because `1-0-1` events cannot be loaded into the same column with `1-0-0`, the d If you create a new schema `1-0-2` that reverts the offending changes and is again compatible with `1-0-0`, the data for events with that schema will be written to the original column as expected. -### Notes +:::note -- If events with incorrectly evolved schemas do not arrive, then the recovery column would not be created. -- It is still possible to break loading by overwriting version `1-0-0` of the schema. Please, avoid doing that. +If events with incorrectly evolved schemas never arrive, then the recovery column would not be created. + +::: You can read more about schema evolution and how recovery columns work [here](/docs/storing-querying/schemas-in-warehouse/index.md?warehouse=bigquery#versioning).