qidewenwhen

Hi @AndreiVoinovTR , thanks for using SageMaker Pipeline! Can you also provide us the code snippet on how you defined hyperparameters as PipelineVariable so that we can reproduce the issue?

> Expected behavior Should PipelineVariable(s) be supported for hyperparametes? In Estimator's constructor hyperparameters are defined as: Optional[Dict[str, Union[str, sagemaker.workflow.entities.PipelineVariable]]] = None. Currently PipelineVariable only supports to replace Python primitive types,...

Hi @amitpeshwani , thanks for using SageMaker! I've tried your code snippet with both `LocalPipelineSession` and `PipelineSession` under v2.105.0 but I'm not able to reproduce the issue. Both cases passed...

I tried one more time to test with the normal session: ``` from sagemaker import Session sagemaker_session = Session() script_processor = SKLearnProcessor( framework_version='0.20.0', instance_count=1, instance_type=processing_instance_type, role=role, sagemaker_session=sagemaker_session, #

**Note: only `PipelineSession` or `LocalPipelineSession` supports to generate the step arguments: `processor_step_args = script_processor.run(...)` as they prevent the `.run` from creating a processing job in sdk compile time and return...

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...

The [fix](https://github.com/aws/sagemaker-python-sdk/commit/766e8ecd20a9c6720620097beae2d6f37f90c712) has been merged in [v2.109.0](https://github.com/aws/sagemaker-python-sdk/releases/tag/v2.109.0) a month ago. Closing this issue. Feel free to reopen if you have any questions.

Thanks for reaching out! Sorry that we don't support it at this point. Marked this issue as feature request and added an action item in our backlog to track.

Hi @uwaisiqbal, sorry that I'm not able to give an ETA for it but will let you know if we have any updates. Thanks for trying to help us to...

Hi @nadasaiyed , thanks for reaching out! Sorry that we don't allow parameterized `code` for ProcessingStep at this point that's why you saw the error thrown. The reason is to...