[
https://issues.apache.org/jira/browse/FLINK-16533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17057841#comment-17057841
]
Kostas Kloudas commented on FLINK-16533:
----------------------------------------
In general, we avoid adding methods to public APIs, especially public ones.
Are you sure that introducing a new {{Executor}} (see
[FLIP-73|https://cwiki.apache.org/confluence/display/FLINK/FLIP-73%3A+Introducing+Executors+for+job+submission])
cannot do the job? I think that this could work.
What do you think [~aljoscha][~twalthr]?
> ExecutionEnvironment supports execution of existing plan
> --------------------------------------------------------
>
> Key: FLINK-16533
> URL: https://issues.apache.org/jira/browse/FLINK-16533
> Project: Flink
> Issue Type: Sub-task
> Components: Client / Job Submission
> Reporter: godfrey he
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, {{ExecutionEnvironment}} only supports executing the plan
> generated by self.
> FLIP-84 proposes {{TableEnvironment}} can only trigger the table program and
> the {{StreamExecutionEnvironment}}/{{ExecutionEnvironment}} can only trigger
> {{DataStream}}/{{DataSet}} program. This requires that
> {{ExecutionEnvironment}} can execute the plan generated by
> {{TableEnvironment}}. We propose to add two methods in
> {{ExecutionEnvironment}}: (which are similar to
> {{StreamExecutionEnvironment}}#execute(StreamGraph) and
> {{StreamExecutionEnvironment}}#executeAsync(StreamGraph))
> {code:java}
> public class ExecutionEnvironment {
> @Internal
> public JobExecutionResult execute(Plan plan) throws Exception {
> .....
> }
> @Internal
> public JobClient executeAsync(Plan plan) throws Exception {
> .....
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
