-
Notifications
You must be signed in to change notification settings - Fork 1.2k
sagemaker.workflow.conditions.ConditionNot does not seem to be working #2746
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
Comments
Have the same problem. Sagemaker v 2.74 botocore.exceptions.ClientError: An error occurred (ValidationException) when calling the CreatePipeline operation: Unable to parse pipeline definition. Cannot parse object, unknown property 'Expression'.
|
This bug still exists in sagemaker v2.76 |
Adding a note:
Tracking the fix in backlog |
Describe the bug
I would like to use
sagemaker.workflow.conditions.ConditionNot
to negate asagemaker.workflow.conditions.ConditionEquals
. However, use ofsagemaker.workflow.conditions.ConditionNot
triggers the following exception:The workaround we are using for now is to use
else_steps
instead ofif_steps
in theConditionStep
, and avoid usingConditionNot
.To reproduce
The following Python script can be used to reproduce the bug:
Expected behavior
I would expect the above Python script to upsert the pipeline without any exceptions.
Screenshots or logs
Full traceback:
System information
A description of your system. Please provide:
Thanks in advance for taking the time to look at this report.
The text was updated successfully, but these errors were encountered: