aws / aws/aws-step-functions-data-science-sdk-python

Execution inputs as container arguments for processing jobs

未关闭
#197 6 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
Python
星标
299
派生
84
PR 合并指标
30 天内没有已合并 PR

描述

I'm trying to use execution inputs as container arguements for my processing job:

```
execution_input = ExecutionInput(
schema={
"IngestaJobName": str,
"PreprocessingJobName": str,
"InferenceJobName": str,
"Fecha": str,
}
)
```

```
#Call step
ingesta_step = ProcessingStep(
inference_config["ingesta_step_name"],
processor=ingesta_processor,
job_name=execution_input['IngestaJobName'],
inputs=inputs_ingesta,
outputs=outputs_ingesta,
container_arguments=["--fecha", "$$.Execution.Input['Fecha']"],
container_entrypoint=["python3", "/opt/ml/processing/input/code/"+inference_config["ingesta_function"]],
)
```

I've also tried to replace container_arguments for `["--fecha", execution_input["Fecha"]] `

But in both cases it doesn't work.

### Use Case

When I lunch a new execution of my state machine, it would be useful to get some execution inputs as a container argument in order to define some parameters of intereset that will be define the behaviour of the step directly by the execution input without updating the state machine definition

---

This is a :rocket: Feature Request

贡献指南

打开贡献指南

调研方向

Start by tracing the ProcessingStep container_arguments entry point and how ExecutionInput values are represented in the SDK. Reproduce the supplied processing-job example, then inspect the related implementation and tests if available. Done means an execution input can reach the processing container as an argument without changing the state machine definition.

由索引模型根据 Issue 内容生成。

评估

技术栈
aws, python
领域
cloud, machine-learning
Issue 类型
功能
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
基本清楚
新手友好度
35/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。