[
https://issues.apache.org/jira/browse/AIRFLOW-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17038556#comment-17038556
]
ASF GitHub Bot commented on AIRFLOW-6474:
-----------------------------------------
AlexandrKhabarov commented on pull request #7446: [AIRFLOW-6474] list_dag_runs
cli command should allow exec_date between start/end range and print start/end
times
URL: https://github.com/apache/airflow/pull/7446
---
Issue link:
[AIRFLOW-6474](https://issues.apache.org/jira/projects/AIRFLOW/issues/AIRFLOW-6474?filter=myopenissues)
Make sure to mark the boxes below before creating PR: [x]
- [x] Description above provides context of the change
- [x] Commit message/PR title starts with `[AIRFLOW-NNNN]`. AIRFLOW-NNNN =
JIRA ID<sup>*</sup>
- [x] Unit tests coverage for changes (not needed for documentation changes)
- [x] Commits follow "[How to write a good git commit
message](http://chris.beams.io/posts/git-commit/)"
- [x] Relevant documentation is updated including usage instructions.
- [x] I will engage committers as explained in [Contribution Workflow
Example](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#contribution-workflow-example).
<sup>*</sup> For document-only changes commit message can start with
`[AIRFLOW-XXXX]`.
---
In case of fundamental code change, Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
is needed.
In case of a new dependency, check compliance with the [ASF 3rd Party
License Policy](https://www.apache.org/legal/resolved.html#category-x).
In case of backwards incompatible changes please leave a note in
[UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md).
Read the [Pull Request
Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)
for more information.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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
> Assignee: alexander
> Priority: Major
> Labels: gsoc, gsoc2020, mentor
>
> 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)
