-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Passing ParameterString for Processor arguments fails in Pipeline definition #3323
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
Seems similar to my problem. I would also add the label: "component pipelines". Have you tried just passing in a string rather than a ParameterString? |
Hi @amitpeshwani , thanks for using SageMaker! I've tried your code snippet with both To help us for further investigation, could you please provide information below:
|
I tried one more time to test with the normal session:
This time I can reproduce the error you've seen, see below.
|
Note: only Please replace the
|
Hey @qidewenwhen , Thanks for looking into the issue. As specified in the Additional context section, I'm passing Issue is occurring due to passing Pipeline ParameterString parameter ( |
Folllowing is the code snippet:
Error Message:
|
Thanks for the details! Seems the error was raised during Pipeline local mode execution time rather than the compile time. I can reproduce the issue when starting an execution. The issue may relate to these code lines: sagemaker-python-sdk/src/sagemaker/local/pipeline.py Lines 94 to 102 in 855552c
Engaging the feature owner to look into it |
Describe the bug
Passing a ParameterString parameter in the arguments for Processor throws an error when defining it as part of a pipeline.
Getting
TypeError: Object of type ParameterString is not JSON serializable
errorTo reproduce
Expected behavior
The pipeline definition printed out
Screenshots or logs
If applicable, add screenshots or logs to help explain your problem.
System information
A description of your system. Please provide:
Additional context
from sagemaker.workflow.pipeline_context import LocalPipelineSession
The text was updated successfully, but these errors were encountered: