Open dipanjank opened 1 year ago
Any update on this issue? Getting the same problem when using any ScriptProcessor.
Only work around is to go back to a loaded ProcessingStep() which has now been marked as deprecated.
Hi @martinRenou, This is causing some pretty big issues for us at the moment. Do you have any helpful updates on this please?
I'm not working with the Sagemaker team at the moment, you may have better luck pinging people who work on this code-base these days.
Thanks for getting back. I tagged you as it says you are assigned to it? Can you assign to someone on the team? There's 425 contributors so any help knowing who to link to this would be greatly appreciated. The best I can think of is to ping people who have done recent commits 🤷
Friendly ping @knikure
Any response at all? We would really like to continue using sagemaker but working around this issue is taking it's tole. @knikure
@martinRenou Is there anyone else to friendly ping on this? knikure unassigned 👎
Describe the bug If I use a ParameterString or any other PipelineVariable object in the list passed to the
arguments
argument in PySparkProcessor.run method, I get a TypeError (TypeError: Object of type ParameterString is not JSON serializable).According to the documentation, arguments can be a list of
PipelineVariable
s, so expecting this to work. Is this not supported?To reproduce A clear, step-by-step set of instructions to reproduce the bug.
Expected behavior A clear and concise description of what you expected to happen.
Expect a SageMaker ProcessingJob to be created.
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 Add any other context about the problem here.