[ETL-677] Add bootstrap script for Snowflake Parquet tables #133
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This script will load data into each of our Parquet tables one by one. It's expected to take a few hours to run on an xsmall warehouse.
You can test this script yourself by creating a testing branch from this branch, pushing your new branch (triggering the Snowflake deployment), copying dev Parquet data from the
main
namespace over to your namespace in S3s3://recover-dev-processed-data/my_test_branch/parquet/
, and then using the Snowflake CLI to invoke this script:It's important to note that the current behavior of this script and the stored procedure which it invokes is meant to fulfill the needs of doing a one-time initial load of our Parquet data for demonstration/sandbox purposes. Because our Parquet datasets are overwritten in S3, running this script on different days would load duplicate records – although we wouldn't have a way to differentiate them (e.g., there is no field indicating the Glue workflow which produced them or any other indicator of their ordinality).