You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2015/08/11 14:54:45 UTC

[jira] [Created] (FLINK-2508) Confusing sharing of StreamExecutionEnvironment

Stephan Ewen created FLINK-2508:
-----------------------------------

             Summary: 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)