-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Passing Pipeline Variable for entry_point while using XGBoost Estimator in script mode fails #3078
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
Let me just add this happens with TensorFlow estimator as well. |
I'm seeing this error as well, for any pipeline parameter. Even just basic example in a jupyter notebook: x = ParameterString(name="something", default_value="hello")
|
Start seeing this issue today after I upgraded sagemaker python sdk. |
+1 on this. Using |
Thanks for using SageMaker Model Building Pipeline, the SageMaker Estimator is expecting the https://sagemaker.readthedocs.io/en/stable/api/training/estimators.html
|
sorry, this is a known limitation, python built-in functions can not be applied to pipeline parameters directly. You can use In addition, we are preparing a comprehensive |
This is not happening because of the entry_point. But rather, when entry point is specified, the pipeline would try to upload the code to a S3 location, during the pipeline initialization (rather than at run time). As you can see in line 701 of /opt/conda/lib/python3.7/site-packages/sagemaker/estimator.py in _stage_user_code_in_s3(self) , its trying to upload the code to a location that location is specified using a PipelineParameter which cannot be resolved during pipeline initiation. This only happens when we specify entry_point to the estimator and not during other scenarios. |
Does anyone know how to bypass this error? I'm trying to build a model but this error is stopping me completely in my tracks. I'm getting the same error here and I've tried many things but to no avail:
Where |
Hi @rypoll have you tried Join from from sagemaker.workflow.functions? |
thanks @jessieweiyi, yea, python built-in function cannot be applied on pipeline variable. Instead do this:
|
@rohangpatil, PR 3111 should fix this issue, can you try it out and let us know? |
Hi @jessieweiyi , I have the same problem. I am doing the following:
running pipeline.definition() will result in an error: any idea? |
Describe the bug
Passing Pipeline Variable (e.g. S3 URL) for entry_point while using XGBoost Estimator in script mode fails to generate a pipeline definition. As the estimator tries to parse the variable and fails at url parsing.
To reproduce
generates the error
Expected behavior
The pipeline definition has to be generated.
Screenshots or logs
N/A
System information
A description of your system. Please provide:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: