GitHub user ankurdave opened a pull request:
https://github.com/apache/spark/pull/368
SPARK-1329: Create pid2vid with correct number of partitions
Each vertex partition is co-located with a pid2vid array created in
RoutingTable.scala. This array maps edge partition IDs to the list of vertices
in the current vertex partition that are mentioned by edges in that partition.
Therefore the pid2vid array should have one entry per edge partition.
GraphX currently creates one entry per *vertex* partition, which is a bug
that leads to an ArrayIndexOutOfBoundsException when there are more edge
partitions than vertex partitions. This commit fixes the bug and adds a test
for this case.
Resolves SPARK-1329. Thanks to Daniel Darabos for reporting this bug.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ankurdave/spark fix-pid2vid-size
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/368.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 #368
----
commit 5a5c52a575bceb1286c38146f81f81c244bb3beb
Author: Ankur Dave <[email protected]>
Date: 2014-04-09T06:30:53Z
SPARK-1329: Create pid2vid with correct number of partitions
Each vertex partition is co-located with a pid2vid array created in
RoutingTable.scala. This array maps edge partition IDs to the list of
vertices in the current vertex partition that are mentioned by edges in
that partition. Therefore the pid2vid array should have one entry per
edge partition.
GraphX currently creates one entry per vertex partition, which is a bug
that leads to an ArrayIndexOutOfBoundsException when there are more edge
partitions than vertex partitions. This commit fixes the bug and adds a
test for this case.
Resolves SPARK-1329. Thanks to Daniel Darabos for reporting this bug.
----
---
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.
---
