You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "sunjincheng (JIRA)" <ji...@apache.org> on 2019/06/27 01:39:00 UTC
[jira] [Closed] (FLINK-12990) Date type doesn't consider the local
TimeZone
[ https://issues.apache.org/jira/browse/FLINK-12990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
sunjincheng closed FLINK-12990.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.9.0
Fixed in master:Â 731c38baf1e72f963db1c067ada20dc23e9fc23c
> Date type doesn't consider the local TimeZone
> ---------------------------------------------
>
> Key: FLINK-12990
> URL: https://issues.apache.org/jira/browse/FLINK-12990
> Project: Flink
> Issue Type: Bug
> Components: API / Python
> Reporter: Dian Fu
> Assignee: Dian Fu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, the python DateType is converted by an `int` which indicates the days passed since 1970-1-1 and then the Java side will create a Java Date by call `new Date(days * 86400)`. As we know that the Date constructor expected milliseconds since 1970-1-1 00:00:00 GMT and so we should convert `days * 86400` to GMTÂ milliseconds.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)