[jira] [Closed] (FLINK-13088) Support lazy query transformation & execution on TableEnvironment

["Dawid Wysakowicz (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-13088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dawid Wysakowicz closed FLINK-13088.
------------------------------------
    Resolution: Fixed

Implemented in 593ff73d903f4e8147f11601e85abefef27fb62e

> Support lazy query transformation & execution on TableEnvironment
> -----------------------------------------------------------------
>
>                 Key: FLINK-13088
>                 URL: https://issues.apache.org/jira/browse/FLINK-13088
>             Project: Flink
>          Issue Type: New Feature
>          Components: Table SQL / API
>    Affects Versions: 1.9.0
>            Reporter: godfrey he
>            Assignee: godfrey he
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.9.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> in [FLINK-13081|https://issues.apache.org/jira/browse/FLINK-13081], {{explain}} method will be introduced to support explain multiple-sinks plan, this issue aims to introduce {{execute}} method into {{TableEnvironment}} to trigger the program execution. and in blink planner, queries will not be optimized immediately in {{insertInto}}/{{sqlUpdate}} methods, and will be optimized together in this method.
> {code:java}
> // Triggers the program execution
> JobExecutionResult execute(String jobName) throws Exception;
> {code}
> there are two concerns about this method: 
> 1. which {{execute}} methods ({{TableEnvironment#execute}} or {{StreamExecutionEnvironment#execute}}) users should use?
> 2.  how to make sure users only use {{TableEnvironment#execute}} method if their code only depends on planner module instead of bridge module？



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)