You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "Arlo Purcell (JIRA)" <ji...@apache.org> on 2019/07/17 14:30:01 UTC

[jira] [Updated] (AIRFLOW-4981) execution_date in macro is not a pendulum DateTime for fixed cron schedules

     [ https://issues.apache.org/jira/browse/AIRFLOW-4981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arlo Purcell updated AIRFLOW-4981:
----------------------------------
    Description: When using a fixed cron schedule_interval such as "0 12 * * *", the execution_date (as well as next_execution_date) available in macros is a python datetime object, not a pendulum DateTime as indicated in the macro docs. For my purposes, this means that methods such as in_timezone are not available.  (was: When using a fixed cron schedule_interval such as {{"0 12 * * *", the execution_date (as well as next_execution_date) available in macros is a python datetime object, not a pendulum DateTime as indicated in the macro docs. For my purposes, this means that methods such as in_timezone are not available. }})

> execution_date in macro is not a pendulum DateTime for fixed cron schedules
> ---------------------------------------------------------------------------
>
>                 Key: AIRFLOW-4981
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-4981
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: DAG
>    Affects Versions: 1.10.3
>            Reporter: Arlo Purcell
>            Assignee: Arlo Purcell
>            Priority: Minor
>
> When using a fixed cron schedule_interval such as "0 12 * * *", the execution_date (as well as next_execution_date) available in macros is a python datetime object, not a pendulum DateTime as indicated in the macro docs. For my purposes, this means that methods such as in_timezone are not available.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)