-
Notifications
You must be signed in to change notification settings - Fork 18
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.
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
Do not schedule execution of save operator if other computer operator… #1253
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like it'll work to me! Mainly had some naming/readability concerns. I also will need an integration test for this.
2e209db
to
4d88042
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to still be missing the new integration test for this?
92245da
to
676da4b
Compare
676da4b
to
caa09f7
Compare
done |
740eeb4
to
009829c
Compare
…s fail in a DAG Add unit test case Some linter related fixes for python llm module
009829c
to
b998201
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM thanks!
…s fail in a DAG
Describe your changes and why you are making these changes
Schedule the Load (Save) operator for execution only if all other compute operators have succeeded
Related issue number (if any)
ENG-2661
Loom demo (if any)
Checklist before requesting a review
python3 scripts/run_linters.py -h
for usage).run_integration_test
: Runs integration testsskip_integration_test
: Skips integration tests (Should be used when changes are ONLY documentation/UI)