[ https://issues.apache.org/jira/browse/FLINK-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephan Ewen resolved FLINK-2508. --------------------------------- Resolution: Fixed Assignee: (was: Márton Balassi) Fix Version/s: (was: 1.0.0) 0.10.0 Was fixed as part of the streaming API rework prior to 0.10 > 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.0 > Reporter: Stephan Ewen > Fix For: 0.10.0 > > > 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)