-
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
Support logical operators in conditions (and, or, not) #482
Comments
What is the status on this? |
Not implemented yet. |
I hear no user requests fro this feature. It's not that hard to implement, but not trivial either (needs to build and traverse the logical expression graph). |
Workaround or simple '&&' and '||' is possible with the current conditions. For example, users can write two conditions(one in another one) to represent the '&&' logic. |
/unassign @gaoning777 |
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. |
…low#482) Updated test case too since now we just need check there's runtime error
@dkletran: You can't reopen an issue/PR unless you authored it or you are a collaborator. In response to this:
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. |
We are currently using KFP Pipelines v2, and the conditional branching options with dsl.If, dsl.Elif, and dsl.Else are not sufficient for our needs. The ability to combine conditions logically is essential for us, and we are currently patching KFP compiling code to achieve this functionality. It would be very helpful to have this feature available in Kubeflow Pipelines. Could this issue be reopened, or would it be better to create a new one? |
No description provided.
The text was updated successfully, but these errors were encountered: