[ 
https://issues.apache.org/jira/browse/FLINK-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278180#comment-15278180
 ] 

ASF GitHub Bot commented on FLINK-3754:
---------------------------------------

Github user fhueske commented on a diff in the pull request:

    https://github.com/apache/flink/pull/1958#discussion_r62681920
  
    --- Diff: 
flink-libraries/flink-table/src/main/scala/org/apache/flink/api/table/expressions/arithmetic.scala
 ---
    @@ -25,15 +25,29 @@ import org.apache.calcite.sql.SqlOperator
     import org.apache.calcite.sql.fun.SqlStdOperatorTable
     import org.apache.calcite.tools.RelBuilder
     
    -import org.apache.flink.api.common.typeinfo.BasicTypeInfo
    -import org.apache.flink.api.table.typeutils.TypeConverter
    +import org.apache.flink.api.common.typeinfo.{BasicTypeInfo, 
NumericTypeInfo, TypeInformation}
    +import org.apache.flink.api.table.typeutils.{TypeCheckUtils, TypeConverter}
    +import org.apache.flink.api.table.validate.ExprValidationResult
     
    -abstract class BinaryArithmetic extends BinaryExpression { self: Product =>
    +abstract class BinaryArithmetic extends BinaryExpression {
       def sqlOperator: SqlOperator
     
       override def toRexNode(implicit relBuilder: RelBuilder): RexNode = {
         relBuilder.call(sqlOperator, children.map(_.toRexNode))
       }
    +
    +  override def dataType = left.dataType
    --- End diff --
    
    Is this a sensible default? Shouldn't it be the data type with the higher 
precision / larger value range of both inputs, e.g., `Double` in case of 
`Double` and `Int`, etc?


> Add a validation phase before construct RelNode using TableAPI
> --------------------------------------------------------------
>
>                 Key: FLINK-3754
>                 URL: https://issues.apache.org/jira/browse/FLINK-3754
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API
>    Affects Versions: 1.0.0
>            Reporter: Yijie Shen
>            Assignee: Yijie Shen
>
> Unlike sql string's execution, which have a separate validation phase before 
> RelNode construction, Table API lacks the counterparts and the validation is 
> scattered in many places.
> I suggest to add a single validation phase and detect problems as early as 
> possible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to