[
https://issues.apache.org/jira/browse/FLINK-12585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16845494#comment-16845494
]
Dian Fu commented on FLINK-12585:
---------------------------------
Agree. Having a Python StreamExecutionEnvironment/ExecutionEnvironment is
necessary as there are a lot of important APIs for a job in the Java
StreamExecutionEnvironment/ExecutionEnvironment such as setStateBackend,
setRestartStrategy, etc.
> Align Stream/BatchTableEnvironment with JAVA Table API
> ------------------------------------------------------
>
> Key: FLINK-12585
> URL: https://issues.apache.org/jira/browse/FLINK-12585
> Project: Flink
> Issue Type: Sub-task
> Components: API / Python
> Affects Versions: 1.9.0
> Reporter: sunjincheng
> Priority: Major
>
> Initially we wanted to align with the
> [FLIP-32|[https://cwiki.apache.org/confluence/display/FLINK/FLIP-32%3A+Restructure+flink-table+for+future+contributions]]
> plan and Unify the TableEnvironment. such as:
> {code:java}
> TableConfig config = TableConfig.builder()
> .asStreamingExecution()
> // example of providing configuration that was in
> StreamExecutionEnvironment before
> .watermarkInterval(100)
> .build();
> TableEnvironment tEnv = TableEnvironment.create(config);{code}
> So, Current Python Table API as follows:
> {code:java}
> self.t_config =
> TableConfig.Builder().as_streaming_execution().set_parallelism(1).build()
> self.t_env = TableEnvironment.create(self.t_config){code}
> But, due to Java API not have done this improve yet, and the end date of
> release 1.9 is coming, So, It's better to align the
> `Stream/BatchTableEnvironment` with JAVA Table API for now. we should follow
> the current Java style, for example:
> {code:java}
> val env = StreamExecutionEnvironment.getExecutionEnvironment
> env.setStateBackend(getStateBackend)
> val tEnv = StreamTableEnvironment.create(env){code}
> What to do you think? [~dian.fu] [~WeiZhong]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
