Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

#469 Add options to fail on late and new data separately #470

Merged
merged 3 commits into from
Aug 21, 2024
Merged

#469 Add options to fail on late and new data separately #470

merged 3 commits into from
Aug 21, 2024

Conversation

yruslan
Copy link
Collaborator

@yruslan yruslan commented Aug 20, 2024

Closes #469

@github-actions GitHub Actions
Copy link

github-actions bot commented Aug 20, 2024 •
edited
Loading

Unit Test Coverage

File Coverage [85.61%] 🍏
TransferJob.scala 96.67% 🍏
TransformationJob.scala 96.36% 🍏
SinkJob.scala 93.57% 🍏
PythonTransformationJob.scala 91.8% 🍏
JobBase.scala 87.12% 🍏
TaskRunnerBase.scala 82.95% 🍏
IngestionJob.scala 80.85% 🍏
Total Project Coverage 82.25% 🍏

@yruslan yruslan merged commit 393c4bc into main Aug 21, 2024
8 checks passed
@yruslan yruslan deleted the feature/469-fail-on-no-late-new-data branch August 21, 2024 06:46
@yruslan yruslan mentioned this pull request Aug 21, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@VladimirRybalko VladimirRybalko Awaiting requested review from VladimirRybalko

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Add an option that does not threat late or new data as errors separately
1 participant
@yruslan