From f118c253dc51844c6dea000f74f71b1ae8a02c4b Mon Sep 17 00:00:00 2001 From: Louis Pieterse Date: Fri, 20 Sep 2024 01:36:58 +0100 Subject: [PATCH] Notice of PipelineWise being shrank (#434) * PipelineWise shrink Notice * Create CODEOWNERS --------- Co-authored-by: Luke Tang <113184527+ltang-wise@users.noreply.github.com> --- .github/CODEOWNERS | 1 + .github/dependabot.yml | 10 ---------- README.md | 9 ++++++++- 3 files changed, 9 insertions(+), 11 deletions(-) create mode 100644 .github/CODEOWNERS delete mode 100644 .github/dependabot.yml diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS new file mode 100644 index 00000000..8382fd1f --- /dev/null +++ b/.github/CODEOWNERS @@ -0,0 +1 @@ +* @transferwise/analytics-platform diff --git a/.github/dependabot.yml b/.github/dependabot.yml deleted file mode 100644 index b6736570..00000000 --- a/.github/dependabot.yml +++ /dev/null @@ -1,10 +0,0 @@ -# This is an automatically generated base configuration -# For further configuration options and tuning: -# https://docs.github.com/en/free-pro-team@latest/github/administering-a-repository/configuration-options-for-dependency-updates - -version: 2 -updates: - - package-ecosystem: "pip" - directory: "/" - schedule: - interval: "weekly" diff --git a/README.md b/README.md index 0a7d3674..ee8ef70d 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,10 @@ +# Notice +To better serve Wise business and customer needs, the PipelineWise codebase needs to shrink. +We have made the difficult decision that, going forward many components of PipelineWise will be removed or incorporated in the main repo. +The last version before this decision is [v0.64.1](https://github.com/transferwise/pipelinewise/tree/v0.64.1) + +We thank all in the open-source community, that over the past 6 years, have helped to make PipelineWise a robust product for heterogeneous replication of many many Terabytes, daily + # pipelinewise-target-snowflake [![PyPI version](https://badge.fury.io/py/pipelinewise-target-snowflake.svg)](https://badge.fury.io/py/pipelinewise-target-snowflake) @@ -175,7 +182,7 @@ Full list of options in `config.json`: | temp_dir | String | | (Default: platform-dependent) Directory of temporary files with RECORD messages. | | no_compression | Boolean | | (Default: False) Generate uncompressed files when loading to Snowflake. Normally, by default GZIP compressed files are generated. | | query_tag | String | | (Default: None) Optional string to tag executed queries in Snowflake. Replaces tokens `{{database}}`, `{{schema}}` and `{{table}}` with the appropriate values. The tags are displayed in the output of the Snowflake `QUERY_HISTORY`, `QUERY_HISTORY_BY_*` functions. | -| archive_load_files | Boolean | | (Default: False) When enabled, the files loaded to Snowflake will also be stored in `archive_load_files_s3_bucket` under the key `/{archive_load_files_s3_prefix}/{schema_name}/{table_name}/`. All archived files will have `tap`, `schema`, `table` and `archived-by` as S3 metadata keys. When incremental replication is used, the archived files will also have the following S3 metadata keys: `incremental-key`, `incremental-key-min` and `incremental-key-max`. +| archive_load_files | Boolean | | (Default: False) When enabled, the files loaded to Snowflake will also be stored in `archive_load_files_s3_bucket` under the key `/{archive_load_files_s3_prefix}/{schema_name}/{table_name}/`. All archived files will have `tap`, `schema`, `table` and `archived-by` as S3 metadata keys. When incremental replication is used, the archived files will also have the following S3 metadata keys: `incremental-key`, `incremental-key-min` and `incremental-key-max`. | archive_load_files_s3_prefix | String | | (Default: "archive") When `archive_load_files` is enabled, the archived files will be placed in the archive S3 bucket under this prefix. | archive_load_files_s3_bucket | String | | (Default: Value of `s3_bucket`) When `archive_load_files` is enabled, the archived files will be placed in this bucket.