Use unique staging paths for BigQuery source#4411
Merged
Merged
Conversation
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
A very good write-up of the situation is in DBI-790.
To resolve the conflicts between the previous snapshot cleanup and the new snapshot sync, add a subfolder with the workflow's run id. Use the same temporal session mechanism that's used to pass PG snapshot name to the QRep flows, it's great that we have it. It won't help us on the future snapshot+CDC path but we'll get there when we get there, the whole "return string as an
anytransaction" situation is already a mess.Validated locally and as a hotfix on the customer service that hit this.
Closes DBI-790