-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Not able to have the value of the output_path in TensorFlow estimator as pipeline parameter #3149
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
@mouhannadali thanks for using SageMaker Pipeline! I'm not able to reproduce the issue based on the code snippets in this issue. Could you please do the following and see if the issue still persists?
Please let us know if you have any questions. |
Hi @qidewenwhen thanks for the replay. I did update the SDK package to sagemaker-2.92.2 and hard coded the training_instance_type. Now I am getting the following error: |
Thanks @mouhannadali for the quick update! This pending PR should be able to fix it: #3146 |
Thanks @qidewenwhen for the fast reply. one more question: is there a notebook/script example (best practice) where it shows how to pass all the parameters of an estimator (Tesorflow estimator) including hyperparameters as training pipeline parameters? |
We have this sample notebook with Tensorflow estimator: https://github.com/aws/amazon-sagemaker-examples/blob/main/sagemaker-pipelines/tabular/tensorflow2-california-housing-sagemaker-pipelines-deploy-endpoint/tensorflow2-california-housing-sagemaker-pipelines-deploy-endpoint.ipynb |
It is working now after updating to the last SDK version. Thanks for the support |
Describe the bug
I am not able to have the value of the output_path in TensorFlow estimater as pipeline parameter
To reproduce
I created the following Sagemaker workflow parameters:
created the following TF estimator:
created the training step:
and finally created the pipeline and tried to print the pipeline.definition()
Expected behavior
The pipeline should be created without any problem
Screenshots or logs

Additional context
Now if I hardcode the output_path in the estimator then it is working correctly:
The text was updated successfully, but these errors were encountered: