You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "t oo (Jira)" <ji...@apache.org> on 2020/01/18 20:56:00 UTC
[jira] [Updated] (AIRFLOW-6474) list_dag_runs cli command should
allow exec_date between start/end range and print start/end times
[ https://issues.apache.org/jira/browse/AIRFLOW-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
t oo updated AIRFLOW-6474:
--------------------------
Description:
1. accept argument exec_date_from, exec_date_to to filter execution_dates returned, ie show dag runs with exec_date between 20190901 and 20190930
2. separate to that in the output print the start_date and end_date of each dagrun (ie execdate for 20190907 had start_date 2019090804:23 and end_date 2019090804:38
3. dag_id arg should be optional
was:
1. accept argument exec_date_from, exec_date_to to filter execution_dates returned, ie show dag runs with exec_date between 20190901 and 20190930
2. separate to that in the output print the start_date and end_date of each dagrun (ie execdate for 20190907 had start_date 2019090804:23 and end_date 2019090804:38
> list_dag_runs cli command should allow exec_date between start/end range and print start/end times
> --------------------------------------------------------------------------------------------------
>
> Key: AIRFLOW-6474
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6474
> Project: Apache Airflow
> Issue Type: Improvement
> Components: cli
> Affects Versions: 1.10.7
> Reporter: t oo
> Priority: Major
>
> 1. accept argument exec_date_from, exec_date_to to filter execution_dates returned, ie show dag runs with exec_date between 20190901 and 20190930
> 2. separate to that in the output print the start_date and end_date of each dagrun (ie execdate for 20190907 had start_date 2019090804:23 and end_date 2019090804:38
> 3. dag_id arg should be optional
--
This message was sent by Atlassian Jira
(v8.3.4#803005)