You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Viktor Vlasov (JIRA)" <ji...@apache.org> on 2018/05/31 14:38:00 UTC

[jira] [Updated] (FLINK-9482) Not applicable functions for TIME

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

Viktor Vlasov updated FLINK-9482:
---------------------------------
    Description: 
Due to work on https://issues.apache.org/jira/browse/FLINK-9432 I have faced with question how to check DECADE function with tests in

_org/apache/flink/table/expressions/validation/ScalarFunctionsValidationTest.scala._ 


Because I have used CENTURY function as an example, first of all I have check it. During the test I figured out that when we use it with TIME it returns 0.
I suppose arguments for such functions (also it works for YEAR, MONTH, MILLENNIUM, etc) need to be checked and throw some exception if type is not suitable.

As an example, in Apache Calcite project (checked in sqlline shell), when I am trying to use CENTURY with TIME it throw:
{code:java}
java.lang.AssertionError: unexpected TIME
{code}
Need to determine, why such check is not exists and add it.

> Not applicable functions for TIME
> ---------------------------------
>
>                 Key: FLINK-9482
>                 URL: https://issues.apache.org/jira/browse/FLINK-9482
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Viktor Vlasov
>            Priority: Minor
>
> Due to work on https://issues.apache.org/jira/browse/FLINK-9432 I have faced with question how to check DECADE function with tests in
> _org/apache/flink/table/expressions/validation/ScalarFunctionsValidationTest.scala._ 
> Because I have used CENTURY function as an example, first of all I have check it. During the test I figured out that when we use it with TIME it returns 0.
> I suppose arguments for such functions (also it works for YEAR, MONTH, MILLENNIUM, etc) need to be checked and throw some exception if type is not suitable.
> As an example, in Apache Calcite project (checked in sqlline shell), when I am trying to use CENTURY with TIME it throw:
> {code:java}
> java.lang.AssertionError: unexpected TIME
> {code}
> Need to determine, why such check is not exists and add it.



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