[
https://issues.apache.org/jira/browse/FLINK-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693282#comment-14693282
]
Márton Balassi commented on FLINK-2508:
---------------------------------------
Thanks for spotting this, I think the purpose of having the current environment
cached was to be able to set the `TestStreamEnvironment` as context, but the
current state of the code seems a bit messy.
> Confusing sharing of StreamExecutionEnvironment
> -----------------------------------------------
>
> Key: FLINK-2508
> URL: https://issues.apache.org/jira/browse/FLINK-2508
> Project: Flink
> Issue Type: Bug
> Components: Streaming
> Affects Versions: 0.10
> Reporter: Stephan Ewen
> Fix For: 0.10
>
>
> In the {{StreamExecutionEnvironment}}, the environment is once created and
> then shared with a static variable to all successive calls to
> {{getExecutionEnvironment()}}. But it can be overridden by calls to
> {{createLocalEnvironment()}} and {{createRemoteEnvironment()}}.
> This seems a bit un-intuitive, and probably creates confusion when
> dispatching multiple streaming jobs from within the same JVM.
> Why is it even necessary to cache the "current" execution environment?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
