You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Ash Berlin-Taylor (JIRA)" <ji...@apache.org> on 2018/12/17 17:09:00 UTC
[jira] [Resolved] (AIRFLOW-698) dag_run "scheduled" property should
be it's own DB column
[ https://issues.apache.org/jira/browse/AIRFLOW-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ash Berlin-Taylor resolved AIRFLOW-698.
---------------------------------------
Resolution: Fixed
This has been changed since - and the scheduler will now pick up any dag run _unless_ it starts with {{backfill_}}
> dag_run "scheduled" property should be it's own DB column
> ---------------------------------------------------------
>
> Key: AIRFLOW-698
> URL: https://issues.apache.org/jira/browse/AIRFLOW-698
> Project: Apache Airflow
> Issue Type: Improvement
> Reporter: Dan Davydov
> Priority: Major
> Labels: beginner, starter
>
> The airflow schedule only executes dag_runs that have a run_id that start with "scheduled__". This can be very confusing, especially when manually creating a dagrun and forgetting the "scheduled__" prefix. The "scheduled" part should be pulled into a separate column so that it is very clear in the UI that a user is creating a DAG that isn't scheduled.
> cc [~maxime.beauchemin@apache.org]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)