airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From san...@apache.org
Subject incubator-airflow git commit: [AIRFLOW-1761] Fix type in scheduler.rst
Date Fri, 27 Oct 2017 15:18:31 GMT
Repository: incubator-airflow
Updated Branches:
  refs/heads/master 635ab01a7 -> efdc4d3b4


[AIRFLOW-1761] Fix type in scheduler.rst

Closes #2707 from mhue/patch-1


Project: http://git-wip-us.apache.org/repos/asf/incubator-airflow/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-airflow/commit/efdc4d3b
Tree: http://git-wip-us.apache.org/repos/asf/incubator-airflow/tree/efdc4d3b
Diff: http://git-wip-us.apache.org/repos/asf/incubator-airflow/diff/efdc4d3b

Branch: refs/heads/master
Commit: efdc4d3b418a27d7808b17026ce271fe416646f0
Parents: 635ab01
Author: Martial Hue <martial.hue@gmail.com>
Authored: Fri Oct 27 08:17:25 2017 -0700
Committer: Siddharth Anand <siddharthanand@yahoo.com>
Committed: Fri Oct 27 08:17:36 2017 -0700

----------------------------------------------------------------------
 docs/scheduler.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-airflow/blob/efdc4d3b/docs/scheduler.rst
----------------------------------------------------------------------
diff --git a/docs/scheduler.rst b/docs/scheduler.rst
index 8029eb0..7e4e544 100644
--- a/docs/scheduler.rst
+++ b/docs/scheduler.rst
@@ -84,7 +84,7 @@ Airflow is that these DAG Runs are atomic, idempotent items, and the scheduler,
 the lifetime of the DAG (from start to end/now, one interval at a time) and kick off a DAG
Run for any
 interval that has not been run (or has been cleared). This concept is called Catchup.
 
-If your DAG is written to handle it's own catchup (IE not limited to the interval, but instead
to "Now"
+If your DAG is written to handle its own catchup (IE not limited to the interval, but instead
to "Now"
 for instance.), then you will want to turn catchup off (Either on the DAG itself with ``dag.catchup
=
 False``) or by default at the configuration file level with ``catchup_by_default = False``.
What this
 will do, is to instruct the scheduler to only create a DAG Run for the most current instance
of the DAG


Mime
View raw message