You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The users can also write the spec manually. See real e2e example. The specification and structures for the graph components have been present in KFP since the first G.A. release.
To use a graph component simply load it the same way as container components: using load_component_from_url or load_component_from_file. The user does not need to know whether the component is implemented as a single container or as a task graph.
Are there new clients that ask for this feature? (We can talk offline)
Are there any additional features that should be supported?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This will allow reusing a subset of the pipeline in other pipelines, similar to the function
https://airflow.apache.org/docs/stable/concepts.html?highlight=subdag#subdags
The text was updated successfully, but these errors were encountered: