Github user ankurdave commented on the pull request:
https://github.com/apache/spark/pull/3866#issuecomment-68906303
I'm not sure I understand the problems you're trying to solve in this PR.
Is this an accurate summary:
1. Activeness based on whether a vertex attribute changed from one
superstep to the next (not implemented in the code yet?). An alternative to
using an `isAttrChanged` flag could be to use a VertexRDD join such as
[VertexRDD#diff](https://github.com/apache/spark/blob/master/graphx/src/main/scala/org/apache/spark/graphx/VertexRDD.scala#L128).
2. Arbitrary convergence tests based on iteration number and number of
active messages (implemented using `isTerminal`). What is the use case for this?
3. Optional initial message (implemented by making `initialMsg` an
`Option`).
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
