[
https://issues.apache.org/jira/browse/CALCITE-3252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde resolved CALCITE-3252.
----------------------------------
Fix Version/s: 1.21.0
Resolution: Fixed
Fixed in
[e8b08c49|https://github.com/apache/calcite/commit/e8b08c490ab4270945c35f31846cd36b5788cc23];
thanks for the PR, [~lindseycat]!
> Add CONVERT_TIMEZONE, TO_DATE, TO_TIMESTAMP functions to Redshift operator
> library
> ----------------------------------------------------------------------------------
>
> Key: CALCITE-3252
> URL: https://issues.apache.org/jira/browse/CALCITE-3252
> Project: Calcite
> Issue Type: Bug
> Reporter: Lindsey Meyer
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.21.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Syntax error while parsing CONVERT_TIMEZONE, TO_DATE, TO_TIMESTAMP functions
> on Redshift. Example queries that error for these functions:
> {code:java}
> SELECT CONVERT_TIMEZONE('UTC', 'America/Los_Angeles', CAST('2019-01-01
> 01:00:00' AS TIMESTAMP) FROM mytable {code}
> {code:java}
> SELECT TO_DATE('2019-01-01', 'YYYY-MM-DD') FROM mytable {code}
> {code:java}
> SELECT TO_TIMESTAMP('2019-01-01 01:00:00', 'YYYY-MM-DD HH:MM:SS') FROM
> mytable
> {code}
> With errors like:
> {code:java}
> No match found for function signature CONVERT_TIMEZONE(<CHARACTER>,
> <CHARACTER>, <TIMESTAMP>)
> {code}
> These are valid in Redshift and Postgres, except for CONVERT_TIMEZONE, which
> I believe is only valid on Redshift.
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
