You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Hequn Cheng (JIRA)" <ji...@apache.org> on 2019/06/06 01:42:00 UTC
[jira] [Commented] (FLINK-12737) Loosen Table class dependencies
[ https://issues.apache.org/jira/browse/FLINK-12737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16857204#comment-16857204 ]
Hequn Cheng commented on FLINK-12737:
-------------------------------------
Hi [~dawidwys], +1 for this!
As for the `insertInto`, what's the api looks like? Currently, `sqlUpdate` in `TableEnvironment` can achieve similar things. And we can also use Table.insertInto() to insert tables if users have a table instance. Will these APIs also be changed?
Best, Hequn
> Loosen Table class dependencies
> -------------------------------
>
> Key: FLINK-12737
> URL: https://issues.apache.org/jira/browse/FLINK-12737
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / API, Table SQL / Legacy Planner
> Reporter: Dawid Wysakowicz
> Assignee: Dawid Wysakowicz
> Priority: Major
> Fix For: 1.9.0
>
>
> The aim of this task is to remove dependencies on actual implementation of {{TableEnvironment}}. This includes:
> * drop generating unique attribute generation (it sufficient to index aggregates within a single operation)
> * make the transformation from {{Table}} on the caller side rather than on the callee (a.k.a remove getRelNode)
> * Add {{insertInto}} method to {{TableEnvironment}}
> Additionally move the TemporalTableFunctionImpl to api-java module.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)