aws / aws/aws-step-functions-data-science-sdk-python
adding tags to a Sagemaker estimator in the training step does not seem to be supported
- Langage dominant
- Python
- Étoiles
- 299
- Forks
- 84
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
Extract from the workbook "machine_learning_workflow_abalone.ipynb"
When adding tags in the following estimator :
mes_tags = [{'key': 'cart', 'value': 'dataengineering'}]
xgb = sagemaker.estimator.Estimator(
image_uris.retrieve("xgboost", region, "1.2-1"),
sagemaker_execution_role,
train_instance_count=1,
train_instance_type="ml.m4.4xlarge",
train_volume_size=5,
output_path=bucket_path + "/" + prefix + "/single-xgboost",
base_job_name=base_job_name,
tags=mes_tags,
sagemaker_session=session,
)
No error when creating the sagemaker.estimator object
The workflow creation fails
When running the command (later in the notebook):
workflow.create()
I got the exception :
"InvalidDefinition: An error occurred (InvalidDefinition) when calling the CreateStateMachine operation: Invalid State Machine Definition: 'SCHEMA_VALIDATION_FAILED: The field "key" is not supported by Step Functions at /States/Train Step/Parameters"
Which is clearly related to the tags I previously added.
Apparently, adding tags to a Sagemaker estimator in the training step does not seem to be supported by the current version of the SDK.
To reproduce
You can comment "tags=mes_tags" and re-rerun the notebook and the state machine is created without any errors.
Logs
Only the stack trace in the notebook
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Start with machine_learning_workflow_abalone.ipynb and compare workflow.create() with and without the estimator's tags argument. Inspect the generated Train Step Parameters around the reported key validation error and the estimator/workflow entry points involved. Done means the tagged training workflow is accepted by Step Functions without the reported InvalidDefinition error.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- aws, jupyter-notebook, python
- Domaine
- cloud, machine-learning
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 45/100