You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 04:02:21 UTC
[jira] [Updated] (SPARK-22459) EdgeDirection "Either" Does Not
Considerate Real "Either" Direction
[ https://issues.apache.org/jira/browse/SPARK-22459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon updated SPARK-22459:
---------------------------------
Labels: bulk-closed (was: )
> EdgeDirection "Either" Does Not Considerate Real "Either" Direction
> -------------------------------------------------------------------
>
> Key: SPARK-22459
> URL: https://issues.apache.org/jira/browse/SPARK-22459
> Project: Spark
> Issue Type: Bug
> Components: GraphX
> Affects Versions: 2.1.1, 2.1.2, 2.2.0
> Environment: Windows 7. Yarn cluster / client mode. Tested with 2.2.0, 2.1.1 and 2.1.2 spark versions.
> Reporter: Tom
> Priority: Major
> Labels: bulk-closed
>
> When running functions involving [EdgeDirection|https://github.com/apache/spark/blob/master/graphx/src/main/scala/org/apache/spark/graphx/EdgeDirection.scala], the _EdgeDirection.Either_ type does not truly perform the actual specified direction (_either_).
> For instance, when using _Pregel API_ with a simple graph as shown:
> !http://www.icodeguru.com/CPP/10book/books/book9/images/fig6_1.gif!
> With _EdgeDirection.Either_ you would guess that vertex #3 will send a message (when activated) to vertices 1, 2, and 4, but in reality it does not.
> This might be bypassed, but in an expansive and ineffective way.
> Tested with 2.2.0, 2.1.1 and 2.1.2 spark versions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org