You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/04/06 09:41:00 UTC
[jira] [Commented] (AIRFLOW-4120) SLA of zero timedelta is not
respected
[ https://issues.apache.org/jira/browse/AIRFLOW-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811527#comment-16811527 ]
ASF subversion and git services commented on AIRFLOW-4120:
----------------------------------------------------------
Commit d48cd67e8ca8cc5517912fe4f1e27572205e1a24 in airflow's branch refs/heads/v1-10-test from Markan Patel
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=d48cd67 ]
[AIRFLOW-4120] Modify SchedulerJob.manage_slas to respect zero timedelta SLAs (#4939)
Modify SchedulerJob.manage_slas to respect zero timedelta SLAs
> SLA of zero timedelta is not respected
> --------------------------------------
>
> Key: AIRFLOW-4120
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4120
> Project: Apache Airflow
> Issue Type: Bug
> Components: models
> Reporter: Markan Patel
> Priority: Minor
> Fix For: 2.0.0
>
>
> When passing a zero timedelta SLA to any operator, it is not properly respected if the task misses it.
>
> {code:python}
> BaseOperator(
> sla=timedelta(), # or timedelta(0)
> **kwargs)
> {code}
> The cause can be narrowed down to the fact that
> {code:python}
> bool(timedelta()) == False
> {code}
> So any code that checks if the SLA parameter is falsy should be updated accordingly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)