After making a few tests I got to the final conclusions:
The cron like jobs are supported by Airflow with one downside: On the the
very first job deployment (completely new DAG) an extra DAG run will be
created for the latest passed period.
When DAG is redeployed (dag name stays the same) then DB
Do not set to datetime.now(). You could set to 2019-04-18 and it will start
scheduling at 2019-04-18 2 AM.
Chen
On Thu, Apr 18, 2019, 08:55 Pawel Bartoszek
wrote:
> Ash, If I omit start_date it I get the error
> Task is missing the start_date parameter
>
> What should I set it to then?
>
> On T
Ash, If I omit start_date it I get the error
Task is missing the start_date parameter
What should I set it to then?
On Thu, Apr 18, 2019 at 1:03 PM Ash Berlin-Taylor wrote:
> Do not set start_date to now. That will _always_ be wrong.
> https://airflow.apache.org/faq.html#what-s-the-deal-with-st
Do not set start_date to now. That will _always_ be wrong.
https://airflow.apache.org/faq.html#what-s-the-deal-with-start-date
> On 18 Apr 2019, at 12:13, Pawel Bartoszek
> wrote:
>
> Hi,
>
> When I set start_date to datetime.now() ie
>
> DAG(
>dag_id="dag",
>start_date=datet
Hi,
When I set start_date to datetime.now() ie
DAG(
dag_id="dag",
start_date=datetime.now(),
schedule_interval="0 2 * * *",
default_view="graph",
orientation="TB",
concurrency=1,
max_active_runs=1,
catchup=False
)
I get following in
Hi Pawel,
I think you can change the start_date to later dates to avoid the DagRun of
2019-04-16 02:00 being scheduled.
Chao-Han
On Wed, Apr 17, 2019 at 10:13 AM Pawel Bartoszek <
pawel.bartoszek@gmail.com> wrote:
> Hi,
>
> Let's say I deploy the following DAG at 2019-04-17 5 PM
>
> DAG(
>
Hi,
Let's say I deploy the following DAG at 2019-04-17 5 PM
DAG(
dag_id="dag",
start_date=datetime(year=2018, month=1, day=1, hour=2, minute=0),
schedule_interval="0 2 * * *,
default_view="graph",
orientation="TB",
concurrency=1,
max_active_
