Mailing-List: contact dev-help@giraph.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@giraph.apache.org
Date: Fri, 2 Nov 2012 15:57:13 +0000 (UTC)
From: "Alessandro Presta (JIRA)" <jira@apache.org>
To: giraph-dev@incubator.apache.org
Message-ID: <858513404.60775.1351871833805.JavaMail.jiratomcat@arcas>
In-Reply-To: 
 <346513910.18679.1331811818312.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (GIRAPH-155) Allow creation of graph by adding
 edges that span multiple workers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/GIRAPH-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alessandro Presta updated GIRAPH-155:
-------------------------------------

    Attachment: GIRAPH-155.patch

Integrated Nitay's suggestions.
                
> Allow creation of graph by adding edges that span multiple workers
> ------------------------------------------------------------------
>
>                 Key: GIRAPH-155
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-155
>             Project: Giraph
>          Issue Type: New Feature
>          Components: graph, lib
>    Affects Versions: 0.2.0
>            Reporter: Dionysios Logothetis
>            Assignee: Alessandro Presta
>         Attachments: GIRAPH-155.patch, GIRAPH-155.patch, GIRAPH-155.patch
>
>
> Currently a graph is created only be adding vertices. The typical way is to read input text files line-by-line with each line describing a vertex (its value, its edges etc). The current API allows for the creation of a vertex only if all the information for the vertex is available in a single line.
> However, it's common to have graphs described in the form of edges. Edges might span multiple lines in an input file or even span multiple workers. The current API doesn't allow this. In the input superstep, a vertex must be created by a single worker.
> Instead, it should be possible for multiple workers to mutate the graph during the input superstep.
> This has the following implications:
> 1) Instead of just instantiating a vertex, a vertex reader should be able to do vertex addition and edge addition requests.
> 2) Multiple workers might try to create the same vertex. Any conflicts should be handled with a VertexResolver. So the resolver has to be instantiated before load time.

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