[
https://issues.apache.org/jira/browse/FLINK-11449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761656#comment-16761656
]
sunjincheng commented on FLINK-11449:
-------------------------------------
Hi [~twalthr] I have encountered a dependency problem. Before FLINK-11067 is
resolved, we should have no way to put Expression into the common. For example,
TableReferenceExpression will depend on Table, and Table implementation will be
in Planner.
BTW. Why we do not put `TableReferenceExpression` put into
`flink-table-api-common` after FLINK-11067 ?
So I feel that now we have two choices:
1. In this PR put all the Expressions into the `flink-table-planner`
temporarily.
2. Complete FLINK-11067 first, then open current PR.
What do you think ?
> 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)
