[
https://issues.apache.org/jira/browse/FLINK-32871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17756690#comment-17756690
]
xy edited comment on FLINK-32871 at 8/21/23 6:18 AM:
-----------------------------------------------------
engines I mean some engines in bigdata scope，such as presto、trino、starrocks and
so on，these engine had function to compute timestamp but name is not
to_timestamp，and these engines support timezone argument. Oracle/SQL Server may
not used in bigdata scope，so i add the function with it，otherwise user can only
use udf for it，and it would increase maintenance cost [~libenchao]
was (Author: xuzifu):
engines I mean some engines in bigdata scope，such as presto、trino、starrocks and
so on，these engine had function to compute timestamp but name is not
to_timestamp，and support timezone argument. Oracle/SQL Server may not used in
bigdata scope，so i add the function with it，otherwise user can only use udf for
it，and it would increase maintenance cost [~libenchao]
> Support BuiltInMethod TO_TIMESTAMP with timezone options
> --------------------------------------------------------
>
> Key: FLINK-32871
> URL: https://issues.apache.org/jira/browse/FLINK-32871
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Reporter: xy
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.19.0
>
>
> 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)
