[
https://issues.apache.org/jira/browse/FLINK-11068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771210#comment-16771210
]
Timo Walther commented on FLINK-11068:
--------------------------------------
I would like to avoid multiple language-specific classes for table and table
environment. This avoids confusion and code duplication.
Currently, \{{Table}} is used by Java and Scala users at the same time and I
don't think this was ever a problem. As [~dawidwys] already mentioned in some
other Jira ticket, in a long-term vision we might introduce a programmatic
approach of creating expressions in Java instead of using strings: e.g.
\{{table.select(field("myField").add($(12)))}}
Then we can deprecate the string methods in the future.
> Convert the API classes *Table, *Window to interfaces
> -----------------------------------------------------
>
> Key: FLINK-11068
> URL: https://issues.apache.org/jira/browse/FLINK-11068
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Reporter: Timo Walther
> Assignee: vinoyang
> 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].
> This includes: Table, GroupedTable, WindowedTable, WindowGroupedTable,
> OverWindowedTable, Window, OverWindow
> We can keep the "Table" Scala implementation in a planner module until it has
> been converted to Java.
> We can add a method to the planner later to give us a concrete instance. This
> is one possibility to have a smooth transition period instead of changing all
> classes at once.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
