GitHub user ankurdave opened a pull request:

    https://github.com/apache/spark/pull/885

    [SPARK-1931] Reconstruct routing tables in Graph.partitionBy

    905173df57b90f90ebafb22e43f55164445330e6 introduced a bug in partitionBy
    where, after repartitioning the edges, it reuses the VertexRDD without
    updating the routing tables to reflect the new edge layout. Subsequent
    accesses of the triplets contain nulls for many vertex properties.
    
    This commit adds a test for this bug and fixes it by introducing
    `VertexRDD#withEdges` and calling it in `partitionBy`.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ankurdave/spark SPARK-1931

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/885.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 #885
    
----
commit 9bdbaa41a4b93caf3352089b59704231bd4be8ef
Author: Ankur Dave <[email protected]>
Date:   2014-05-26T16:35:02Z

    [SPARK-1931] Reconstruct routing tables in Graph.partitionBy
    
    905173df57b90f90ebafb22e43f55164445330e6 introduced a bug in partitionBy
    where, after repartitioning the edges, it reuses the VertexRDD without
    updating the routing tables to reflect the new edge layout. Subsequent
    accesses of the triplets contain nulls for many vertex properties.
    
    This commit adds a test for this bug and fixes it by introducing
    `VertexRDD#withEdges` and calling it in `partitionBy`.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to