[
https://issues.apache.org/jira/browse/GIRAPH-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13658668#comment-13658668
]
Avery Ching commented on GIRAPH-667:
------------------------------------
This is a huge improvement on the current situation where we have to hack
stages into our compute methods. Love the idea. Given that this is a
user-facing API change, others should take a look, but I am happy to see us
moving in this direction.
> Decouple Vertex data and Computation, make Computation and Combiner classes
> switchable
> --------------------------------------------------------------------------------------
>
> Key: GIRAPH-667
> URL: https://issues.apache.org/jira/browse/GIRAPH-667
> Project: Giraph
> Issue Type: New Feature
> Reporter: Maja Kabiljo
> Assignee: Maja Kabiljo
> Attachments: GIRAPH-667.patch
>
>
> Currently, our Vertex class holds a lot of stuff which shouldn't be there,
> related to global graph and worker state. We should decouple vertex and
> computation, vertex should be provided by the infrastructure and user should
> implement the computation.
> In many real-world applications there are several different stages, where
> different kind of computation is done and different type of messages are
> sent. This can be done currently by having complicated compute() and encoding
> the message type inside of the message. Much better would be to provide a way
> to change which Computation is used by Giraph. Applications can then be
> considered as pieces which can be put together in a pipeline coordinated by
> master.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
