You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Akshesh Doshi (JIRA)" <ji...@apache.org> on 2019/07/04 09:58:00 UTC

[jira] [Commented] (AIRFLOW-2819) Clarify the Timezone support for Cron schedules

    [ https://issues.apache.org/jira/browse/AIRFLOW-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16878509#comment-16878509 ] 

Akshesh Doshi commented on AIRFLOW-2819:
----------------------------------------

Can someone please clarify this.

 

With _AIRFLOW__CORE__DEFAULT_TIMEZONE=Asia/Bangkok_, I created the following DAG
{code:java}
dag = DAG(
dag_id='checktimezone',
default_args=args,
schedule_interval='0 16 * * *',
catchup=False,
){code}
But my dag still doesn't run at 4PM.

 

Also, if I have _schedule_interval='0 9 * * *'_, it runs at 4PM (because 9AM UTC = 4PM Bangkok time).

 

 

Would appreciate if someone could point out what I am missing here - I think Airflow is not respecting the time zone for the *_schedule_interval_* parameter.

 

 

> Clarify the Timezone support for Cron schedules
> -----------------------------------------------
>
>                 Key: AIRFLOW-2819
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2819
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: scheduler
>    Affects Versions: 1.10.0
>            Reporter: Le Van Giap
>            Assignee: Le Van Giap
>            Priority: Major
>             Fix For: 1.10.0
>
>
> h3. [https://airflow.readthedocs.io/en/v1-10-test/timezone.html#cron-schedules]
> The explanation here is quite hard to understand.
> May I know what is the behavior (running time) of the Scheduler when I have a *America/New_York* Timezone aware DAG? For example: "5 9 * * *" with timezone *America/New_York*



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)