Mailing-List: contact dev-help@giraph.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@giraph.apache.org
Date: Wed, 15 May 2013 18:07:17 +0000 (UTC)
From: "Maja Kabiljo (JIRA)" <jira@apache.org>
To: giraph-dev@incubator.apache.org
Message-ID: <JIRA.12647794.1368641165865.325193.1368641237230@arcas>
In-Reply-To: <JIRA.12647794.1368641165865@arcas>
References: <JIRA.12647794.1368641165865@arcas>
Subject: [jira] [Created] (GIRAPH-667) Decouple Vertex data and Computation,
 make Computation and Combiner classes switchable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Maja Kabiljo created GIRAPH-667:
-----------------------------------

             Summary: 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


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