Mailing-List: contact giraph-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: giraph-user@incubator.apache.org
Message-ID: <4F2C2EAF.8060804@apache.org>
Date: Fri, 03 Feb 2012 10:59:59 -0800
From: Avery Ching <aching@apache.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
 rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: giraph-user@incubator.apache.org
Subject: Re: creating non existing vertices by sending messages
References: 
 <CAFJOoJfRDKqBzUeXcrmVxn-8jS5OOETTRDAk0j25x-HxPeKtig@mail.gmail.com>
 <CB5166A6.6277%dgarcia@potomacfusion.com>
 <CAFJOoJdrhXBBGSE24AfE+nvQ0ZmqrJ2DXhLqwp1vZ0LZUztObg@mail.gmail.com>
In-Reply-To: 
 <CAFJOoJdrhXBBGSE24AfE+nvQ0ZmqrJ2DXhLqwp1vZ0LZUztObg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Thanks for the comments David.  The behavior of what happens is 
completely defined by the chosen VertexResolver, see 
(GiraphJob#setWorkerContextClass).  Developers can implement any 
behavior they want.  I believe the only reason to bypass was as a 
performance optimization.

Avery

On 2/3/12 8:34 AM, Claudio Martella wrote:
> Agreed, probably making the path configurable is the way to go.
>
> On Fri, Feb 3, 2012 at 5:30 PM, David Garcia<dgarcia@potomacfusion.com>  wrote:
>> I just wanted to send this out because I remember reading a discussion on
>> this topic.  Currently, graph will create a vertex in the graph if a
>> message is sent to a vertexID that doesn't exist.  Personally, I really
>> really like this behavior.  It enables me to forgo vertex creation if I
>> don't need it.  If I need the vertex, I can simply send a message to
>> create it, and process the message that was sent.  I understand that there
>> are some concerns with this. . .I would suggest making this behavior
>> configurable at job creation.  This would be an awesome compromise, and
>> would not preclude either type of behavior.
>>
>> -David
>>
>
>