You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Timo Walther (JIRA)" <ji...@apache.org> on 2018/11/27 08:43:00 UTC

[jira] [Reopened] (FLINK-10009) Fix the casting problem for function TIMESTAMPADD in Table

     [ https://issues.apache.org/jira/browse/FLINK-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timo Walther reopened FLINK-10009:
----------------------------------

The fix version is missing. And the fix should be ported to the last 2 releases as well.

> Fix the casting problem for function TIMESTAMPADD in Table
> ----------------------------------------------------------
>
>                 Key: FLINK-10009
>                 URL: https://issues.apache.org/jira/browse/FLINK-10009
>             Project: Flink
>          Issue Type: Bug
>          Components: Table API &amp; SQL
>            Reporter: Xingcan Cui
>            Assignee: Ruidong Li
>            Priority: Major
>              Labels: pull-request-available
>
> There seems to be a bug in {{TIMESTAMPADD}} function. For example, {{TIMESTAMPADD(MINUTE, 1, DATE '2016-06-15')}} throws a {{ClassCastException}} ( java.lang.Integer cannot be cast to java.lang.Long). Actually, it tries to cast an integer date to a long timestamp in RexBuilder.java:1524 - {{return TimestampString.fromMillisSinceEpoch((Long) o)}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)