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 2017/07/28 22:51:00 UTC

[jira] [Commented] (AIRFLOW-1349) Max active dagrun check for backfills shouldn't include the backfilled dagrun

    [ https://issues.apache.org/jira/browse/AIRFLOW-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16105815#comment-16105815 ] 

ASF subversion and git services commented on AIRFLOW-1349:
----------------------------------------------------------

Commit 547f8184be1e0b3f902faf354fa39579d2f08af2 in incubator-airflow's branch refs/heads/master from [~erod]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=547f818 ]

[AIRFLOW-1349] Refactor BackfillJob _execute

BackfillJob._execute is doing multiple things - it is pretty hard to
follow and maintain.

Changes included are just a re-org of the code, no logic has been
changed.

Refactor includes:
- Break BackfillJob._execute into functions
- Add a Status object to track BackfillJob
internal status while
  executing the job.

Closes #2463 from edgarRd/erod-backfill-refactor


> Max active dagrun check for backfills shouldn't include the backfilled dagrun
> -----------------------------------------------------------------------------
>
>                 Key: AIRFLOW-1349
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-1349
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: backfill
>            Reporter: Dan Davydov
>            Assignee: Edgar Rodriguez
>
> When you backfill a dag with e.g. 1 max active dagrun, if that dagrun is already running then it shouldn't count against the max active dagruns of the backfill and make the backfill fail.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)