adding skip exit code for lightbeam #12
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
… state tracking is enabled and no payloads have changed
jayckaiser
reviewed
Jun 13, 2023
| with open(self.lightbeam.results_file, 'w') as fp: | ||
| fp.write(json.dumps(self.metadata, indent=4)) | ||
|
|
||
| if self.metadata["total_records_processed"] == self.metadata["total_records_skipped"]: |
There was a problem hiding this comment.
I believe this will work, assuming that rows are added to both lists at the same time (and hence are in the same order).
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.
If
lightbeamskips sending all payloads because state tracking is enabled and no payloads have changed, we now exit with code 99 to signal Airflow (or other apps) to skip downstream tasks.