[
https://issues.apache.org/jira/browse/FLINK-13419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16892541#comment-16892541
]
godfrey he commented on FLINK-13419:
------------------------------------
{{StreamExecutionEnvironment}} can not be reused between batch job and stream
job now, because only unfied TableEnvironment can be used for batch job, and
{{StreamExecutionEnvironment}} is created in {{ExecutorFactory}}, users can not
get {{StreamExecutionEnvironment}} instance from {{TableEnvironment}}
interface. the batch properties in {{StreamExecutionEnvironment}} will not not
changed (the properties is hard code) even {{TableEnvironment.explain()}} is
called many times.
unless user implements a new {{TableEnvironment}} which exposes the
{{StreamExecutionEnvironment}}, I think user should handle this case
> TableEnvironment.explain() has side-effects on ExecutionConfig
> --------------------------------------------------------------
>
> Key: FLINK-13419
> URL: https://issues.apache.org/jira/browse/FLINK-13419
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Reporter: Timo Walther
> Priority: Major
> Fix For: 1.9.0, 1.10.0
>
>
> The Blink Planner seems to set batch properties in
> {{org.apache.flink.table.planner.delegation.BatchExecutor#generateStreamGraph}}
> which remain after {{TableEnvironment.explain()}}.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
