Recover Quarantine using releases #152
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
added 8 commits
January 4, 2024 08:18
…n addition this line was blocking the CI because when the data goes to quarantine it returns error.
alexon1234
approved these changes
Jan 4, 2024
|
@albertojuan Looks fine. It would be way nicer if we could add a data quality test to verify that the actual data was moved from the quarantine to the correct table successfully. |
alexon1234
reviewed
Jan 5, 2024
added 9 commits
January 5, 2024 12:09
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.
Example on how to recover information in quarantine.
There's no much difference on how to recover information from quarantine using or not using Releases. In this example we take advantage of Releases to perform the copy of the data in the preview release, avoiding to pollute the main workspace with a temporary copy pipe.