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

オープン
#200 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る
bug
主要言語
Python
スター
299
フォーク
84
PR マージ指標
30日以内にマージされた PR はありません

説明

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

コントリビューションガイド

コントリビューションガイドを開く

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

評価

技術スタック
aws, jupyter-notebook, python
領域
cloud, machine-learning
issue の種類
バグ
難易度
4/5
見積もり時間
3〜5日
活発さ
停滞
明瞭さ
おおむね明確
初心者へのやさしさ
45/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。