airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bolke de Bruin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-504) datetime.now() has microseconds Mysql does not store these resulting in issues
Date Wed, 28 Jun 2017 20:52:00 GMT

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

Bolke de Bruin commented on AIRFLOW-504:
----------------------------------------

It is in updating.md

> datetime.now() has microseconds Mysql does not store these resulting in issues
> ------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-504
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-504
>             Project: Apache Airflow
>          Issue Type: Bug
>            Reporter: Bolke de Bruin
>            Priority: Critical
>             Fix For: 1.8.0
>
>
> >>> datetime.datetime.utcnow()
> datetime.datetime(2016, 9, 11, 12, 22, 22, 483998)
> >>> datetime.datetime.now()
> datetime.datetime(2016, 9, 11, 14, 22, 31, 363392)
> >>>
> Mysql rounds those to "2016-05-13 00:00:00". If sqlalchemy now tries to find the the
record by primary key (eg. session.merge) it cannot find them due to lost precision.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message