You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Bas Harenslak (Jira)" <ji...@apache.org> on 2019/10/31 18:16:00 UTC
[jira] [Updated] (AIRFLOW-5825) SageMakerEndpointOperator is not
idempotent
[ https://issues.apache.org/jira/browse/AIRFLOW-5825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bas Harenslak updated AIRFLOW-5825:
-----------------------------------
Description:
The SageMakerEndpointOperator currently taken an argument "operation" with value "create"/"update" which determines whether to create or update a SageMaker endpoint. However this doesn't work in the following situation:
* DAG run #1 create the endpoint (have to provide operation="create" here)
* Following DAG runs will update the endpoint created by DAG run #1 (would have to edit DAG and set operation="update" here)
Which should be a very valid use case IMO.
The SageMakerEndpointOperator should check itself if an endpoint with name X already exists and overwrite it (configurable desired by the user).
was:
The SageMakerEndpointOperator currently taken an argument "operation" with value "create"/"update" which determines whether to create or update a SageMaker endpoint. However this doesn't work in the following situation:
* DAG run #1 create the endpoint
* Following DAG runs will update the endpoint created by DAG run #1
Which should be a very valid use case IMO.
The SageMakerEndpointOperator should check itself if an endpoint with name X already exists and overwrite it (configurable desired by the user).
> SageMakerEndpointOperator is not idempotent
> -------------------------------------------
>
> Key: AIRFLOW-5825
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5825
> Project: Apache Airflow
> Issue Type: Improvement
> Components: aws
> Affects Versions: 2.0.0, 1.10.7
> Reporter: Bas Harenslak
> Priority: Major
>
> The SageMakerEndpointOperator currently taken an argument "operation" with value "create"/"update" which determines whether to create or update a SageMaker endpoint. However this doesn't work in the following situation:
> * DAG run #1 create the endpoint (have to provide operation="create" here)
> * Following DAG runs will update the endpoint created by DAG run #1 (would have to edit DAG and set operation="update" here)
> Which should be a very valid use case IMO.
> The SageMakerEndpointOperator should check itself if an endpoint with name X already exists and overwrite it (configurable desired by the user).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)