You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Keisuke Kawamura (JIRA)" <ji...@apache.org> on 2019/04/19 18:02:00 UTC
[jira] [Updated] (AIRFLOW-4359) Add a check for start_date when
webserver shows dag list
[ https://issues.apache.org/jira/browse/AIRFLOW-4359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keisuke Kawamura updated AIRFLOW-4359:
--------------------------------------
Description:
If like this dag_run data is in airflow database, the toppage would be crush.
mysql> select execution_date, start_date from dag_run where dag_id = '__masked___' order by execution_date desc limit 1;
+----------------------------+------------+
| execution_date | start_date |
+----------------------------+------------+
| 2017-04-03 18:00:00.000000 | NULL |
+----------------------------+------------+
1 row in set (0.05 sec)
It's caused the code in webserver doesn't check start_date.
I think we need to add a check for start_date
> Add a check for start_date when webserver shows dag list
> ---------------------------------------------------------
>
> Key: AIRFLOW-4359
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4359
> Project: Apache Airflow
> Issue Type: Bug
> Components: webserver
> Affects Versions: 1.10.2, 1.10.3
> Reporter: Keisuke Kawamura
> Assignee: Keisuke Kawamura
> Priority: Major
>
> If like this dag_run data is in airflow database, the toppage would be crush.
> mysql> select execution_date, start_date from dag_run where dag_id = '__masked___' order by execution_date desc limit 1;
> +----------------------------+------------+
> | execution_date | start_date |
> +----------------------------+------------+
> | 2017-04-03 18:00:00.000000 | NULL |
> +----------------------------+------------+
> 1 row in set (0.05 sec)
> It's caused the code in webserver doesn't check start_date.
> I think we need to add a check for start_date
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)