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

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

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

    https://github.com/apache/flink/pull/3791#discussion_r114063055
  
    --- Diff: 
flink-libraries/flink-table/src/main/scala/org/apache/flink/table/plan/logical/LogicalNode.scala
 ---
    @@ -79,15 +79,21 @@ abstract class LogicalNode extends 
TreeNode[LogicalNode] {
       protected[logical] def construct(relBuilder: RelBuilder): RelBuilder
     
       def validate(tableEnv: TableEnvironment): LogicalNode = {
    -    val resolvedNode = resolveExpressions(tableEnv)
    -    resolvedNode.expressionPostOrderTransform {
    -      case a: Attribute if !a.valid =>
    -        val from = children.flatMap(_.output).map(_.name).mkString(", ")
    -        failValidation(s"Cannot resolve [${a.name}] given input [$from].")
    -
    -      case e: Expression if e.validateInput().isFailure =>
    -        failValidation(s"Expression $e failed on input check: " +
    -          s"${e.validateInput().asInstanceOf[ValidationFailure].message}")
    +    // A tableFunction may not contain the tableEnv when created by scala 
user
    +    // We do not validate operators (select, as etc.)
    +    // if they are applied on such TableFunction with empty tableEnv.
    +    if (tableEnv == null) this
    --- End diff --
    
    This looks like a potentially problematic condition which relies on the 
fact that `tableEnv` may only be `null` in case of a `TableFunction`. It would 
be much better if we could avoid such special casing in method which are called 
from many different places.


> Refactoring UDTF interface
> --------------------------
>
>                 Key: FLINK-6334
>                 URL: https://issues.apache.org/jira/browse/FLINK-6334
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API & SQL
>            Reporter: Ruidong Li
>            Assignee: Ruidong Li
>
> The current UDTF leverages the table.join(expression) interface, which is not 
> a proper interface in terms of semantics. We would like to refactor this to 
> let UDTF use table.join(table) interface. Very briefly,  UDTF's apply method 
> will return a Table Type, so Join(UDTF('a, 'b, ...) as 'c) shall be viewed as 
> join(Table)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to