Fix resuming the transform process. #348
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
When the streaming is interrupted in the middle of a JSON/SQL file and then resumes in replay mode, the transform process needs to read and parse the latest JSON/SQL file in case it's being restarted in the middle of a transaction. The transform process rewrites the SQL file even when it was done previously, as a way of implementing "cache invalidation" where the source of truth is the JSON file. This PR implements the same approach to the replay mode start-up sequence.
This was referenced Jun 29, 2023
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.
When the streaming is interrupted in the middle of a JSON/SQL file and then resumes in replay mode, the transform process needs to read and parse the latest JSON/SQL file in case it's being restarted in the middle of a transaction.
The transform process rewrites the SQL file even when it was done previously, as a way of implementing "cache invalidation" where the source of truth is the JSON file. This PR implements the same approach to the replay mode start-up sequence.
Should fix #331.