airflow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kaxil Naik <kaxiln...@gmail.com>
Subject Re: [DISCUSS] Change all example_dags's start_date to specific datetime
Date Sat, 11 May 2019 09:27:26 GMT
I don't think any example dag contains ".now()" date. If it foes we need to
change. But the others contains dynamic dates before 2 days which are
sensible as catchup=True be default

On Fri, May 10, 2019, 15:07 zhongjiajie955@gmail.com <
zhongjiajie955@gmail.com> wrote:

> Hi Airflower:
>     I start this thread proposal to change all example_dags's start_date
> to specific datetime, including airflow/example_dag and
> airflow/contrib/example_dags.
> I proposal that because in
> https://airflow.apache.org/faq.html#what-s-the-deal-with-start-date
>
> > We recommend against using dynamic values as start_date, especially
> datetime.now() as it can be quite confusing. The task is triggered once the
> period closes, and in theory an @hourly DAG would never get to an hour
> after now as now() moves along.
>
> we suggest to set start_date to specific datetime, but all example_dags in
> code base are use dynamic values like `airflow.utils.dates.days_ago(2)` or
> `datetime.utcnow()`. Most of Airflow starter will use example dag as they
> template to create their own dag, so I think should change them in correct
> values.
>
> But if we use a specific datetime in example dag, for example 2019-01-01,
> starter will use them as template and confuse "Why my dag start run in
> 2019-01-01?".
>
> So, should we change start_date?
>
> This proposal start in slack #users-china channel
> https://apache-airflow.slack.com/archives/CGQ4A9DCZ/p1557467228006100 .
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message