This repository has been archived by the owner on May 2, 2023. It is now read-only.
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.
The current approach for upsert is to delete existing rows that are going to be reimported using a join between the staging stable and the target table to identify which rows have to be deleted:
This is not performing very well.
With a destination table of ~4GB and a ~60MB of import data the query takes ~255 seconds to run.
When we changed the delete query from a join to a sub-select:
with the same volume of data(~4GB destination table and ~60MB file) we reduced the query time to ~1.20s.
When trying to delete from a ~4GB staging table to a 4GB target table we observed a ~1.53s execution time.