[
https://issues.apache.org/jira/browse/FLINK-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15366112#comment-15366112
]
ASF GitHub Bot commented on FLINK-4172:
---------------------------------------
GitHub user greghogan opened a pull request:
https://github.com/apache/flink/pull/2213
[FLINK-4172] [gelly] Don't proxy a ProxiedObject
Retrieve the proxied object and wrap in a new proxy.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/greghogan/flink
4172_dont_proxy_a_proxiedobject
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2213.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2213
----
commit 91526d6ce6989dc65863b414c3ae074f33476046
Author: Greg Hogan <[email protected]>
Date: 2016-07-07T13:35:29Z
[FLINK-4172] [gelly] Don't proxy a ProxiedObject
Retrieve the proxied object and wrap in a new proxy.
----
> Don't proxy a ProxiedObject
> ---------------------------
>
> Key: FLINK-4172
> URL: https://issues.apache.org/jira/browse/FLINK-4172
> Project: Flink
> Issue Type: Bug
> Components: Gelly
> Affects Versions: 1.1.0
> Reporter: Greg Hogan
> Assignee: Greg Hogan
> Fix For: 1.1.0
>
>
> Some graph algorithms pass through a DataSet unmodified (at least, until we
> have VertexSet and EdgeSet). We need to prevent a DataSet from being proxied
> twice. Allowing two methods to own a single object sounds brittle, so we can
> instead provide access to the original DataSet which can be wrapped in a new
> proxy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
