You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2017/01/13 21:52:26 UTC

[jira] [Resolved] (SPARK-18568) vertex attributes in the edge triplet not getting updated in super steps for Pregel API

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

Sean Owen resolved SPARK-18568.
-------------------------------
    Resolution: Not A Problem

Yes, the result of updating a mutable object in an RDD is undefined. If that's the essence of this, then it's not a problem.

> vertex attributes in the edge triplet not getting updated in super steps for Pregel API
> ---------------------------------------------------------------------------------------
>
>                 Key: SPARK-18568
>                 URL: https://issues.apache.org/jira/browse/SPARK-18568
>             Project: Spark
>          Issue Type: Bug
>          Components: GraphX
>    Affects Versions: 2.0.2
>            Reporter: Rohit
>
> When running the Pregel API with vertex attribute as complex objects. The vertex attributes are not getting updated in the triplet view. For example if the vertex attributes changes in first superstep for vertex"a" the triplet src attributes in the send msg program for the first super step gets the latest attributes of the vertex "a" but on 2nd super step if the vertex attributes changes in the vprog the edge triplets are not updated with this new state of the vertex for all the edge triplets having the vertex "a" as src or destination. if I re-create the graph using g = Graph(g.vertices, g.edges) in the while loop before the next super step then its getting updated. But this fix is not good performance wise. A detailed description of the bug along with the code to recreate it is in the attached URL.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org