You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Weike Dong (JIRA)" <ji...@apache.org> on 2018/05/29 14:52:00 UTC
[jira] [Commented] (FLINK-8353) Add support for timezones
[ https://issues.apache.org/jira/browse/FLINK-8353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493639#comment-16493639 ]
Weike Dong commented on FLINK-8353:
-----------------------------------
I strongly support these features, preferably there could be a way to set a specific timezone for a particular job, so that all the subsequent temporal processing could be based on that. As user's input data are often collected from other systems that do not follow the rules set by Flink (UTC+0), currently some temporal UDFs are needed to perform such transformations, which adds the complexity for the whole system, especially in case of watermark generation or output of processing time into external database, etc.
> Add support for timezones
> -------------------------
>
> Key: FLINK-8353
> URL: https://issues.apache.org/jira/browse/FLINK-8353
> Project: Flink
> Issue Type: New Feature
> Components: Table API & SQL
> Reporter: Timo Walther
> Priority: Major
>
> This is an umbrella issue for adding support for timezones in the Table & SQL API.
> Usually companies work with different timezones simultaneously. We could add support for the new time classes introduced with Java 8 and enable our scalar functions to also work with those (or some custom time class implementations like those from Calcite). We need a good design for this to address most of the problems users face related to timestamp and timezones.
> It is up for discussion how to ship date, time, timestamp instances through the cluster.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Re: [jira] [Commented] (FLINK-8353) Add support for timezones
Posted by Kaibo Zhou <zk...@gmail.com>.
Time zone is a very useful feature, I think there are three levels of time
zone settings (priority from high to low):
1. connectors: For example, the time zone of the time field in the kafaka
data
2. job level: Specifies which time zone the current job uses, perhaps
specified by TableConfig or StreamQueryConfig
3. The system default, effective for all jobs, can be specified by
flink_conf.yaml
2018-05-29 22:52 GMT+08:00 Weike Dong (JIRA) <ji...@apache.org>:
>
> [ https://issues.apache.org/jira/browse/FLINK-8353?page=
> com.atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel&focusedCommentId=16493639#comment-16493639 ]
>
> Weike Dong commented on FLINK-8353:
> -----------------------------------
>
> I strongly support these features, preferably there could be a way to set
> a specific timezone for a particular job, so that all the subsequent
> temporal processing could be based on that. As user's input data are often
> collected from other systems that do not follow the rules set by Flink
> (UTC+0), currently some temporal UDFs are needed to perform such
> transformations, which adds the complexity for the whole system, especially
> in case of watermark generation or output of processing time into external
> database, etc.
>
> > Add support for timezones
> > -------------------------
> >
> > Key: FLINK-8353
> > URL: https://issues.apache.org/jira/browse/FLINK-8353
> > Project: Flink
> > Issue Type: New Feature
> > Components: Table API & SQL
> > Reporter: Timo Walther
> > Priority: Major
> >
> > This is an umbrella issue for adding support for timezones in the Table
> & SQL API.
> > Usually companies work with different timezones simultaneously. We could
> add support for the new time classes introduced with Java 8 and enable our
> scalar functions to also work with those (or some custom time class
> implementations like those from Calcite). We need a good design for this to
> address most of the problems users face related to timestamp and timezones.
> > It is up for discussion how to ship date, time, timestamp instances
> through the cluster.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v7.6.3#76005)
>