Re: [graphframes]how Graphframes Deal With Bidirectional Relationships

[Ramon Bejar]

But, is it not possible to compute with both directions of an edge like 
it happens with graphX ?



On 02/20/2018 03:01 AM, Felix Cheung wrote:

Generally that would be the approach.
But since you have effectively double the number of edges this will 
likely affect the scale your job will run.



*From:* xiaobo 
*Sent:* Monday, February 19, 2018 3:22:02 AM
*To:* user@spark.apache.org
*Subject:* [graphframes]how Graphframes Deal With Bidirectional 
Relationships

Hi,
To represent a bidirectional relationship, one solution is to insert 
two edges for the vertices pair, my question is do the algorithms of 
graphframes still work when we doing this.


Thanks

[Spark GraphX pregel] default value for EdgeDirection not consistent between programming guide and API documentation

[Ramon Bejar Torres]

Hi,

I just wanted to notice that in the API doc page for the pregel operator 
(graphX API for spark 2.2.1):


http://spark.apache.org/docs/latest/api/scala/index.html#org.apache.spark.graphx.GraphOps@pregel[A](A,Int,EdgeDirection)((VertexId,VD,A)%E2%87%92VD,(EdgeTriplet[VD,ED])%E2%87%92Iterator[(VertexId,A)],(A,A)%E2%87%92A)(ClassTag[A]):Graph[VD,ED] 



It says that the default value for the activeDir parameter is 
EdgeDirection.Either



However, in the GraphX programming guide:

http://spark.apache.org/docs/latest/graphx-programming-guide.html#pregel-api 



in the type signature for the pregel operator the default value 
indicated is EdgeDirection.Out. For consistency, I think that it should 
be changed in the programming guide to the actual default value (Either).



Regards,

Ramon Béjar

DIEI - UdL


-
To unsubscribe e-mail: user-unsubscr...@spark.apache.org