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

Posted to issues@flink.apache.org by "Márton Balassi (JIRA)" <ji...@apache.org> on 2015/08/13 15:47:46 UTC

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

     [ https://issues.apache.org/jira/browse/FLINK-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Márton Balassi reassigned FLINK-2508:
-------------------------------------

    Assignee: Márton Balassi

> 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
>            Assignee: Márton Balassi
>             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)