Skip to content

Conversation

@adeandrade
Copy link

What changes were proposed in this pull request?

Suppose a sendMsg function depends on the state of a edge's vertices to send messages, and those Pregel messages update such state. In this scenario, initialMsg will initially enforce the same message on all vertices, effectively removing a custom initialization one may have per vertex.

To deal with this situation, we must define a dummy initMsg (i.e. None), and all Pregel functions must be modified to handle this type of message. A simpler and less cumbersome solution is to make initMsg and the initialization step in Pregel optional.

How was this patch tested?

No new tests were added. Some tests were updated. Previous functionality was kept.

@adeandrade adeandrade force-pushed the pregel-optional-initmessage branch from dd9123d to 1613dae Compare April 12, 2016 02:09
@AmplabJenkins
Copy link

Can one of the admins verify this patch?

@maropu
Copy link
Member

maropu commented Jan 15, 2020

I'll close this cuz the corresponding jira has been already closed.

@maropu maropu closed this Jan 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants