[
https://issues.apache.org/jira/browse/FLINK-11447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16756199#comment-16756199
]
Dawid Wysakowicz commented on FLINK-11447:
------------------------------------------
I guess you meant those signatures:
{code}
joinLateral(Expression)
joinLateral(String)
joinLateral(Expression, Expression)
joinLateral(String, String)
leftOuterJoinLateral(Expression)
leftOuterJoinLateral(String)
leftOuterJoinLateral(Expression, Expression)
leftOuterJoinLateral(String, String)
{code}
I also still prefer this option it clearly states what is supported, and that
it cannot exist on its own, but is only applicable in case of those kind of
joins.
> 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)
