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

Posted to dev@gobblin.apache.org by "Abhishek Tiwari (Jira)" <ji...@apache.org> on 2020/08/03 21:31:03 UTC

[jira] [Updated] (GOBBLIN-1182) Incorrect datetime value error on mysql 5.7

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

Abhishek Tiwari updated GOBBLIN-1182:
-------------------------------------
    Fix Version/s:     (was: 0.15.0)
                   0.16.0

> Incorrect datetime value error on mysql 5.7
> -------------------------------------------
>
>                 Key: GOBBLIN-1182
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1182
>             Project: Apache Gobblin
>          Issue Type: Improvement
>          Components: gobblin-core
>    Affects Versions: 0.15.0
>            Reporter: Jay Sen
>            Assignee: Abhishek Tiwari
>            Priority: Major
>             Fix For: 0.16.0
>
>
> jobExecution record insertion with default value of epoch timestamp throws error on MySql 5.7+ 
> the reason is MySQL 5.7+ will convert timestamp to local for internal storage and by default errors out anything less than epoch time unless server sets the zero or negative time allowed explicitly.
> as a quick fix, Gobblin can use 1970-01-02 00:00:00 which ensures all world's localtime is covered. alternate solution can be not to set the end_Date at all and allow null to indicate "not set".



--
This message was sent by Atlassian Jira
(v8.3.4#803005)