-
Notifications
You must be signed in to change notification settings - Fork 343
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
Support disabling node output caching for custom KFP components #2905
Conversation
Thanks for making a pull request to Elyra! To try out this branch on binder, follow this link: |
The property labels and descriptions still require editing for clarity. |
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.
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! All scenarios testing as expected (with the known limitation re: the Boolean handling in mind)
Pipeline default property is displayed in generic pipeline editor and airflow pipeline editor even though it is not supported in those runtime environments
An upcoming PR of mine should address that - this will be a good test of that PR's functionality 🙂
Co-authored-by: Alan Chin <akchin@us.ibm.com>
Final doc updates are done. |
Pipeline nodes produce output, such as files. Some runtime environments support caching of these outputs, eliminating the need to re-execute nodes, which can improve performance and reduce resource usage. If a node does not produce output in a deterministic way - that is given the same inputs the generated output is different - re-using the output from previous executions might lead to unexpected results.
This PR enables users to optionally disable caching for nodes for Kubeflow Pipelines pipelines. Caching can be disabled by defining a pipeline default or by explicitly disabling it for individual nodes.
Example: Kubeflow Central Dashboard: cached output was re-used
Example: Kubeflow Central Dashboard: cached output was not re-used
Closes #2894
What changes were proposed in this pull request?
Add new pipeline default property in new section 'custom node defaults'
Add new node property for custom KFP components
Updated relevant documentation in pipelines documentation topic
Known limitations:
How was this pull request tested?
make docs
(user_guide/pipelines.html
)Developer's Certificate of Origin 1.1