Return-Path: X-Original-To: apmail-giraph-user-archive@www.apache.org Delivered-To: apmail-giraph-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3387710501 for ; Fri, 25 Jul 2014 17:04:52 +0000 (UTC) Received: (qmail 82745 invoked by uid 500); 25 Jul 2014 17:04:52 -0000 Delivered-To: apmail-giraph-user-archive@giraph.apache.org Received: (qmail 82693 invoked by uid 500); 25 Jul 2014 17:04:51 -0000 Mailing-List: contact user-help@giraph.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@giraph.apache.org Delivered-To: mailing list user@giraph.apache.org Received: (qmail 82683 invoked by uid 99); 25 Jul 2014 17:04:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Jul 2014 17:04:51 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Lukas.Nalezenec@firma.seznam.cz designates 77.75.74.246 as permitted sender) Received: from [77.75.74.246] (HELO posta.szn.cz) (77.75.74.246) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Jul 2014 17:04:49 +0000 Received: from [10.0.4.229] (10.0.4.229) by posta.szn.cz (10.0.3.149) with Microsoft SMTP Server id 14.3.195.1; Fri, 25 Jul 2014 19:04:23 +0200 Message-ID: <53D28E17.2050006@firma.seznam.cz> Date: Fri, 25 Jul 2014 19:04:23 +0200 From: Lukas Nalezenec User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Subject: Re: concept of vertex in giraph References: <53D21ACA.8070208@firma.seznam.cz>, <9B590560869E3741B7665052119D02421FF059@DEN-EXDDA-S52.corp.ebay.com> In-Reply-To: <9B590560869E3741B7665052119D02421FF059@DEN-EXDDA-S52.corp.ebay.com> Content-Type: multipart/alternative; boundary="------------060602080505070907040502" X-Originating-IP: [10.0.4.229] X-Virus-Checked: Checked by ClamAV on apache.org --------------060602080505070907040502 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Hi IMHO third way, overriding method combine in own Partition is best. Lukas On 25.7.2014 18:47, Schweiger, Tom wrote: > Edges "combine" differently than vertexes. > > By default, each edge you read is added to the adjacency set of the > source vertex (all edges are directed in Giraph, if you had not > realized that yet). So if you read multiple edge for the same source > -> target, they will all be represented in the source vertex's edges. > > If you actually need to combine edges there are two way to go about it. > > 1) (easy but unelegant) deal with the fact in your compute > > 2) (more involved but efficient) write your own OutEdges class, unless > one already exists that does what you need. > > > ------------------------------------------------------------------------ > *From:* Carmen Manzulli [carmenmanzulli@gmail.com] > *Sent:* Friday, July 25, 2014 1:56 AM > *To:* user@giraph.apache.org > *Subject:* Re: concept of vertex in giraph > > ah ok, thanksa lot!...so is the same for edgevalues and > targetvertexids??? i need to use combiners, can you show me where can > i read more information about? > > > 2014-07-25 10:52 GMT+02:00 Lukas Nalezenec > >: > > Hi, > Afaik vertex ids must be unique but you can combine vertexes with > same ID to one using VertexValueCombiner. > > Lukas > > > On 25.7.2014 10:33, Carmen Manzulli wrote: >> Hi experts, >> i would like to ask you if , in the graph rapresentation, every >> time a vertexId is reapeated, would giraph consider just one time >> that vertexId? >> >> for example: >> >> Carmen (vertexId) 24 (vertex value) ..... >> Carmen (vertexId) 1,60 m (vertex value)... >> >> does it became >> >> Carmen -->24 >> -->1,60 >> >> from a point of view conceptual? > > --------------060602080505070907040502 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit
Hi
IMHO third way, overriding method combine in own Partition is best.
Lukas

On 25.7.2014 18:47, Schweiger, Tom wrote:
Edges "combine" differently than vertexes.

By default, each edge you read is added to the adjacency set of the source vertex (all edges are directed in Giraph, if you had not realized that yet).  So if you read multiple edge for the same source -> target, they will all be represented in the source vertex's edges. 

If you actually need to combine edges there are two way to go about it. 

1) (easy but unelegant) deal with the fact in your compute

2) (more involved but efficient) write your own OutEdges class, unless one already exists that does what you need.


From: Carmen Manzulli [carmenmanzulli@gmail.com]
Sent: Friday, July 25, 2014 1:56 AM
To: user@giraph.apache.org
Subject: Re: concept of vertex in giraph

ah ok, thanksa lot!...so is the same for edgevalues and targetvertexids??? i need to use combiners, can you show me where can i read more information about?


2014-07-25 10:52 GMT+02:00 Lukas Nalezenec <lukas.nalezenec@firma.seznam.cz>:
Hi,
Afaik vertex ids must be unique but you can combine vertexes with same ID to one using VertexValueCombiner.

Lukas


On 25.7.2014 10:33, Carmen Manzulli wrote:
 Hi experts,
i would like to ask you if , in the graph rapresentation, every time a vertexId is reapeated, would giraph consider just one time that vertexId?

for example:

Carmen (vertexId) 24 (vertex value) .....
Carmen (vertexId) 1,60 m (vertex value)...

does it became

Carmen -->24
            -->1,60

from a point of view conceptual?



--------------060602080505070907040502--