[
https://issues.apache.org/jira/browse/FLINK-15384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17007362#comment-17007362
]
Timo Walther commented on FLINK-15384:
--------------------------------------
[~zjffdu] we are in the process of simplifying the whole table environment
architecture. At the end of this process, we envision just two table
environments `TableEnvironment` and `StreamTableEnvironment`. The first is not
connected to DataStream API at all, thus, if we want to expose `JobListener` we
need to come up with a new design. `StreamTableEnvironment` is closely coupled
to DataStream API for both bounded and unbounded streams.
`BatchTableEnvironment` will be deprecated soon. I think using
`StreamTableEnvironment` is the correct way you are looking for.
> Allow to pass ExecutionEnvironment/StreamExecutionEnvironment to
> TableEnvironment
> ----------------------------------------------------------------------------------
>
> Key: FLINK-15384
> URL: https://issues.apache.org/jira/browse/FLINK-15384
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Affects Versions: 1.10.0
> Reporter: Jeff Zhang
> Priority: Major
>
> In the new approach of creating TableEnvironement, it is not possible to pass
> ExecutionEnvironment/StreamExecutionEnvironment to TableEnvironement. This
> cause the all the features in ExecutionEnvironment/StreamExecutionEnvironment
> is not available in table api. Such as add JobListener, execute Job async. So
> I suggest to allow to pass ExecutionEnvironment/StreamExecutionEnvironment to
> TableEnvironment
> {code}
> EnvironmentSettings bbSettings =
> EnvironmentSettings.newInstance().useBlinkPlanner().inBatchMode().build();
> TableEnvironment bbTableEnv = TableEnvironment.create(bbSettings);
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
