baolsen commented on a change in pull request #6999: [AIRFLOW-XXXX] Clarify 
wait_for_downstream and execution_date
URL: https://github.com/apache/airflow/pull/6999#discussion_r362745923
 
 

 ##########
 File path: docs/concepts.rst
 ##########
 @@ -341,62 +471,21 @@ is equivalent to:
     [op4, op5] >> op6
 
 
-Tasks
-=====
-
-Once an operator is instantiated, it is referred to as a "task". The
-instantiation defines specific values when calling the abstract operator, and
-the parameterized task becomes a node in a DAG.
-
-Task Instances
-==============
-
-A task instance represents a specific run of a task and is characterized as the
-combination of a DAG, a task, and a point in time. Task instances also have an
-indicative state, which could be "running", "success", "failed", "skipped", "up
-for retry", etc.
-
-Task Lifecycle
-==============
-
-A task goes through various stages from start to completion. In the Airflow UI
-(graph and tree views), these stages are displayed by a color representing each
-stage:
-
-.. image:: img/task_stages.png
-
-The complete lifecycle of the task looks like this:
-
-.. image:: img/task_lifecycle_diagram.png
-
-The happy flow consists of the following stages:
-
-1. No status (scheduler created empty task instance)
-2. Scheduled (scheduler determined task instance needs to run)
-3. Queued (scheduler sent task to executor to run on the queue)
-4. Running (worker picked up a task and is now running it)
-5. Success (task completed)
-
-There is also visual difference between scheduled and manually triggered
-DAGs/tasks:
-
-.. image:: img/task_manual_vs_scheduled.png
-
-The DAGs/tasks with a black border are scheduled runs, whereas the non-bordered
-DAGs/tasks are manually triggered, i.e. by ``airflow dags trigger``.
-
 Workflows
 =========
 
 You're now familiar with the core building blocks of Airflow.
 Some of the concepts may sound very similar, but the vocabulary can
 be conceptualized like this:
 
-- DAG: a description of the order in which work should take place
 
 Review comment:
   Changed wording for some of these and added others

----------------------------------------------------------------
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]


With regards,
Apache Git Services

Reply via email to