-
Notifications
You must be signed in to change notification settings - Fork 310
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
The container image of spark task should be immutable #2956
Conversation
Signed-off-by: Kevin Su <[email protected]>
Signed-off-by: Kevin Su <[email protected]>
the failures in the different plugins tests are real. Can you take a look? |
Signed-off-by: Kevin Su <[email protected]>
fixed it |
Signed-off-by: Kevin Su <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2956 +/- ##
==========================================
- Coverage 51.25% 46.62% -4.63%
==========================================
Files 200 200
Lines 20835 20851 +16
Branches 2688 2691 +3
==========================================
- Hits 10678 9722 -956
- Misses 9559 10652 +1093
+ Partials 598 477 -121 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Kevin Su <[email protected]>
Signed-off-by: Kevin Su <[email protected]>
Tracking issue
NA
Why are the changes needed?
flytekit overwrites the
default_executor_path
when the base_image of ImageSpec is None.When running two Spark tasks in a workflow, flytekit overwrites the
default_executor_path
only for the first task. This happens because flytekit modifies the base_image of the imageSpec during the compilation of the first task. As a result, when compiling the second task, the base_image is no longer None, preventing Flytekit from overwriting the default_executor_path for the second task.What changes were proposed in this pull request?
Deep copy the image spec and modify it.
How was this patch tested?
Setup process
Screenshots
Check all the applicable boxes
Related PRs
NA
Docs link
NA