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 2019/04/23 08:56:00 UTC
[jira] [Updated] (AIRFLOW-4387) airflow 'clear' command handling
for hourly exec dates
[ https://issues.apache.org/jira/browse/AIRFLOW-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
t oo updated AIRFLOW-4387:
--------------------------
Description:
Airflow clear has below options now:
-s, --start_date
Override start_date YYYY-MM-DD
-e, --end_date
Override end_date YYYY-MM-DD
But this does not allow clearing 2019-01-01T10:00 exec date while not clearing 2019-01-01T11:00 or 2019-01-01T09:00 exec dates
UPDATE: Perhaps just the documentation is wrong and needs updating
was:
Airflow clear has below options now:
-s, --start_date
Override start_date YYYY-MM-DD
-e, --end_date
Override end_date YYYY-MM-DD
But this does not allow clearing 2019-01-01T10:00 exec date while not clearing 2019-01-01T11:00 or 2019-01-01T09:00 exec dates
> airflow 'clear' command handling for hourly exec dates
> ------------------------------------------------------
>
> Key: AIRFLOW-4387
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4387
> Project: Apache Airflow
> Issue Type: New Feature
> Components: cli, scheduler
> Affects Versions: 1.10.3
> Reporter: t oo
> Priority: Major
>
> Airflow clear has below options now:
> -s, --start_date
> Override start_date YYYY-MM-DD
> -e, --end_date
> Override end_date YYYY-MM-DD
>
> But this does not allow clearing 2019-01-01T10:00 exec date while not clearing 2019-01-01T11:00 or 2019-01-01T09:00 exec dates
>
> UPDATE: Perhaps just the documentation is wrong and needs updating
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)