Optimize load to snowflake process #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ivanovyordan
approved these changes
Aug 9, 2023
nezd
approved these changes
Aug 9, 2023
While reading replication data from postgres just create s3 files and do not load them in snowflake. When the replication is finished load all files for each table at once - this way will limit import calls to snowflake abd import bigger batches - which is alwais better in snowflake. Also files will not be deleted when they are loaded, but we will keep them in s3 for a week - cleaned later using lifecycle Also update the S3 prefix to include hour and minutes - to avoid having data imported mutiuple times when we have same pid in the same day.
pslavov
force-pushed
the
snowflake-imports-in-only-after-all-changes-are-read
branch
from
01b0a0c
to
32f32a4
Compare
ivanovyordan
deleted the
snowflake-imports-in-only-after-all-changes-are-read
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Background and why
While reading replication data from postgres just create s3 files and
do not load them in snowflake. When the replication is finished load all
files for each table at once - this way will limit import calls to
snowflake and import bigger batches - which is always better in
snowflake.
Also files will not be deleted when they are loaded, but we will keep
them in s3 for a week - cleaned later using lifecycle
Also update the S3 prefix to include hour and minutes - to avoid having
data imported multiple times when we have same pid in the same day.