[
https://issues.apache.org/jira/browse/FLINK-33594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787915#comment-17787915
]
xy commented on FLINK-33594:
----------------------------
if user want to use many timezone in one sql with TO_TIMESTAMP，they can not
choose timezone for it. In a global view，they would use udf for it. this is not
friendly to platform developers. Add the timezone arguments can aviod it and
not bring any risk. [@MartijnVisser|https://github.com/MartijnVisser] as I know
many users occur the problem which confused them for a long time
> Support BuiltInMethod TO_TIMESTAMP with timezone options
> --------------------------------------------------------
>
> Key: FLINK-33594
> URL: https://issues.apache.org/jira/browse/FLINK-33594
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Affects Versions: 1.8.4
> Reporter: xy
> Priority: Major
> Labels: pull-request-available
>
> Support BuiltInMethod TO_TIMESTAMP with timezone options，TO_TIMESTAMPS now
> only use utc timezone，but many scenarios we need timzone to choose，so need a
> pr to support it as TO_TIMESTAMP('2023-08-10', 'yyyy-MM-dd', 'Asia/Shanghai')
> this scenario in presto，starrocks，trino：
> as presto,trino,starrocks:
> SELECT timestamp '2012-10-31 01:00 UTC' AT TIME ZONE 'America/Los_Angeles';
> 2012-10-30 18:00:00.000 America/Los_Angeles
> so we maybe need this function in to_timestamps
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
