vdk-trino: Create new SCD Upsert VDK Trino template #3429
+441
−0
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
What: Adding new way to process data. It is meant to update target table rows based on id column that are coming from the source view and also insert the new rows that are not present in the target table already. Why: It will be used mainly for optimizing the scd1 template in order to avoid calculating the whole table logic on every run.
for more information, see https://pre-commit.ci
sbuldeev
changed the title
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.
What:
Adding new way to process data. It is meant to update target table rows based on id column that are coming from the source view and also insert the new rows that are not present in the target table already.
Why:
It will be used mainly for optimizing the scd1 template in order to avoid calculating the whole table logic on every run.
Tests:
Tested base functionality by executing the template locally and verified the following scenarios:
- Base scenario without checks provided
- Scenario with provided positive checks
- Scenario with provided negative checks
- Scenario to check if the target table comments are being kept