[
https://issues.apache.org/jira/browse/FLINK-11449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761816#comment-16761816
]
Timo Walther commented on FLINK-11449:
--------------------------------------
Hi [~sunjincheng121], yes you are right. We cannot put
{{TableReferenceExpression}} in {{flink-table-api-java}} until {{Table}} has
been touched. I'm fine with putting it into {{flink-table-planner}} as a
temporary solution.
{{TableReferenceExpression}} is a special case, it must not be put into common
because:
1. It depends on an API class.
2. The reference is decorrelated by the planner such that this expression will
never be pushed into a FilterableTableSource.
> Uncouple the Expression class from RexNodes
> -------------------------------------------
>
> Key: FLINK-11449
> URL: https://issues.apache.org/jira/browse/FLINK-11449
> Project: Flink
> Issue Type: New Feature
> Components: Table API & SQL
> Reporter: Timo Walther
> Assignee: sunjincheng
> Priority: Major
>
> A more detailed description can be found in
> [FLIP-32|https://cwiki.apache.org/confluence/display/FLINK/FLIP-32%3A+Restructure+flink-table+for+future+contributions].
> Calcite will not be part of any API module anymore. Therefore, RexNode
> translation must happen in a different layer. This issue will require a new
> design document.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
