-
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
[feature] Setting a task group name #10274
Comments
You can customize the group name via the |
@chensun thanks for the info! The group is created automatically in kfp 2.4, i don't create it myself in the code, that's why I can't assign a name to it. I don't have this UI issue in kfp 2.3. Code snippet:
these if/else conditions are automatically grouped together in the UI in kfp 2.4. Not sure about 2.5, not happening in 2.3 tho. I like the grouping, but I don't like the automatically assigned name.. |
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 issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it. |
Feature Area
/area backend
What feature would you like to see?
Able to set a custom name for a task group:
https://github.com/kubeflow/pipelines/blob/master/sdk/python/kfp/dsl/tasks_group.py#L78
What is the use case or pain point?
when using dsl.If and dsl.Else, they get grouped in a task group with an automatically generated name, which makes the pipeline less readable
Is there a workaround currently?
Custom "head" if component (instead of deprecated dsl.Condition) to mimic a task group, I guess
Love this idea? Give it a 👍.
The text was updated successfully, but these errors were encountered: