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.

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

How do we specify which function objects are being returned as Artifacts using the v2 @component decorator? #3277

Closed
tmbluth opened this issue Jun 10, 2022 · 4 comments

Comments

@tmbluth
Copy link

tmbluth commented Jun 10, 2022

In the code example here (https://www.kubeflow.org/docs/components/pipelines/sdk-v2/v2-component-io/#use-v2-component-decorator-for-python-function-based-components) the output that is specified is Output[Model] and OutputPath. Its unclear what objects are going to be returned to these 2 outputs given there are no objects being returned. How do we tell this code what those output objects are? Are they inferred?

If so, we'd run into an issue if a component trains several models but only want one of those models as output (or it could be several evaluations, datasets, paths, etc). Perhaps the answer is documented elsewhere, but I've been unable to find it. I had assumed the v2 component I/O page might have that detail.

Could someone help me understand this or point me in the right direction? It would be greatly appreciated.

@varodrig
Copy link
Contributor

varodrig commented Jan 17, 2025

@tmbluth documentation has changed please review https://www.kubeflow.org/docs/components/pipelines/user-guides/data-handling/artifacts/ and https://www.kubeflow.org/docs/components/pipelines/user-guides/core-functions/

let us know if you are still facing issues otherwise this issue will be closed soon.
are you still facing issues? Issue will be closed if there's no activity. Due date is Jan 31th.

@varodrig
Copy link
Contributor

varodrig commented Feb 2, 2025

/close

Copy link

@varodrig: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@varodrig
Copy link
Contributor

varodrig commented Feb 2, 2025

@tmbluth we are closing this issue due to the inactivity and it seems the issue was resolved. Please let us know if you are still facing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants