-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
create_component_from_func vs func_to_container_op #7794
Comments
What is the difference between create_component_from_func and func_to_container_op? Credit: Alexandre Brown in Community Slack ref: https://journal.arrikto.com/kubeflow-tips-tricks-january-2022-238fde12f7d0 |
We are moving away from For KFPv2, we are moving away from both approaches above. We recommend using Feel free to reopen this issue if you need more help. |
@zijianjoy will create_component_from_func add |
cc @connor-mccarthy Do we support |
|
This won't work as we need to add extra code before the function is instantiated in order to avoid issues on default values from the parsed function. |
@casassg, I see. Yes, unfortunately that's one of the use-cases where this workaround will not work. The other approach is creating a containerized component that implements this. I suspect this is a fairly common use-case. If you feel strongly about having |
I don't seem to understand the behavior behind these two functions.
I have been using
create_component_from_func
for all of my pipelines, however all tutorials and guides I'm seeing online usefunc_to_container_op
and the docstrings don't explain them enough (They both sayConverts a Python function to a component and returns a task
).Can anyone elaborate on this as the documentation doesn't include much info about this?
The text was updated successfully, but these errors were encountered: