[
https://issues.apache.org/jira/browse/FLINK-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727411#comment-14727411
]
Stephan Ewen commented on FLINK-2602:
-------------------------------------
Actually, I saw this in one spot that was actually already fixed here (by
sachin as part of another pull request) :
https://github.com/apache/flink/commit/5d98e77cd740dc991978dbb1d026954f733786a8
Maybe you find more cases, if not, feel free to close this issue.
> Gelly algorithms obtain new execution environments.
> ---------------------------------------------------
>
> Key: FLINK-2602
> URL: https://issues.apache.org/jira/browse/FLINK-2602
> Project: Flink
> Issue Type: Bug
> Components: Gelly
> Affects Versions: 0.10
> Reporter: Stephan Ewen
> Assignee: Martin Junghanns
>
> I have seen that Gelly occasionally uses
> {{ExecutionEnvironment.getExecutionEnvironment()}} to obtain en execution
> environment.
> That easily leads to problems as it creates new execution environments in
> many cases. For example if the original execution environment was created via
> {{ExecutionEnvironment.createRemoteEnvironment(...)}}, it will inevitably
> give you a wrong execution environment.
> If new sources need to be created, they should be created with the execution
> environment of the other data sets in the computation, for example via
> {{vertexDataSet.getExecutionEnvironment().fromElementx(a, b, c)}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
