[
https://issues.apache.org/jira/browse/FLINK-20457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17255892#comment-17255892
]
zhengyu.lou commented on FLINK-20457:
-------------------------------------
I just find
{color:#4c9aff}Date(java.sql.Date)/Time(java.sql.Time)/Timestamp(java.sql.Timestamp){color}
object do not support storage timezone information,
so my job is use Pickle converts date/time/dateTime objects and unpickle them
at Java side
then create
Date(java.sql.Date)/Time(java.sql.Time)/Timestamp(java.sql.Timestamp)
so that all of utc offset should be calculation at Java side not Python
Is that right？
So this issue in aim to let less operate at Python side ? [~dian.fu]
> Fix the handling of timestamp in DataStream.from_collection
> -----------------------------------------------------------
>
> Key: FLINK-20457
> URL: https://issues.apache.org/jira/browse/FLINK-20457
> Project: Flink
> Issue Type: Bug
> Components: API / Python
> Affects Versions: 1.12.0
> Reporter: Dian Fu
> Assignee: zhengyu.lou
> Priority: Major
> Fix For: 1.13.0, 1.12.1
>
>
> Currently, DataStream.from_collection firstly converts date/time/dateTime
> objects to int at Python side and then construct the corresponding
> Date/Time/Timestamp object at Java side. It will lose the timezone
> information. Pickle could handle date/time/datetime properly and the
> conversion could be avoided.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
