[
https://issues.apache.org/jira/browse/FLINK-11447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16756311#comment-16756311
]
sunjincheng edited comment on FLINK-11447 at 1/30/19 4:45 PM:
--------------------------------------------------------------
Hi [~twalthr] adding a `JoinLateral` operator is indeed a good way to find a
way out. In this way we don't break the semantics of traditional JOIN. And
introduce the a new operator to handle the TableFunction problem, so we have
more self-definition space.
Currently I like the solution which [~twalthr] and [~pnowojski] mentioned
above.
Please give me some time to check out more information， so that to make our
decision more confident. will feedback later(Before Friday night).
Thanks, Jincheng
was (Author: sunjincheng121):
Hi guys, adding a `JoinLateral` operator is indeed a good way to find a way
out. In this way we don't break the semantics of traditional JOIN. And
introduce the a new operator to handle the TableFunction problem, so we have
more self-definition space. currently I like the solution which [~twalthr] and
[~pnowojski] mentioned above.
Please give me some time to check out more information， so that to make our
decision more confident. will feedback later(Before Friday night).
Thanks, Jincheng
> Deprecate "new Table(TableEnvironment, String)"
> -----------------------------------------------
>
> Key: FLINK-11447
> URL: https://issues.apache.org/jira/browse/FLINK-11447
> Project: Flink
> Issue Type: New Feature
> Components: Table API & SQL
> Reporter: Timo Walther
> Assignee: Dian Fu
> 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].
> Once table is an interface we can easily replace the underlying
> implementation at any time. The constructor call prevents us from converting
> it into an interface.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
