You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Joy Gao (JIRA)" <ji...@apache.org> on 2016/06/05 04:59:59 UTC
[jira] [Commented] (AIRFLOW-184) Add clear/mark success to CLI
[ https://issues.apache.org/jira/browse/AIRFLOW-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15315728#comment-15315728 ]
Joy Gao commented on AIRFLOW-184:
---------------------------------
Agree with point above.
The Airflow UI provides the visual granularity that makes selecting a specific Task Instance at a point in time easy, and consequently ‘future’ and ‘past’ are relative to the TI selected.
The CLI for 'clear' does offer past/future functionalities (recursive is easy to add). Omitting start_date/end_date is the equivalent of selecting past/future. This is not very intuitive, but there doesn't seem to be a good way to select a specific Task Instance other than pinning it down with start_date and end_date (which may be confused with the started/ended timestamp of the job being run, when in reality it is referring to the execution_date). AFAIK, the only unique identifier for a task instance is the job_id, but that is incrementally assigned by the job scheduler from the job queue and is global to all jobs in Airflow.
As for the --only_failed flag, personally it is more intuitive to treat 'upstream_failed' the same as 'failed' and have those tasks cleared as well (right now it is ignored).
> Add clear/mark success to CLI
> -----------------------------
>
> Key: AIRFLOW-184
> URL: https://issues.apache.org/jira/browse/AIRFLOW-184
> Project: Apache Airflow
> Issue Type: Bug
> Components: cli
> Reporter: Chris Riccomini
> Assignee: Joy Gao
>
> AIRFLOW-177 pointed out that the current CLI does not allow us to clear or mark success a task (including upstream, downstream, past, future, and recursive) the way that the UI widget does. Given a goal of keeping parity between the UI and CLI, it seems like we should support this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)