Re: New vertex allocation and messages

2013-08-19 Thread Avery Ching 
Yes, you can control this behavior with the VertexResolver.  It handles 
all mutations to the graph and resolves them in a user defined way.


Avery

On 8/19/13 9:21 AM, Marco Aurelio Barbosa Fagnani Lotz wrote:

Hello all :)

I am programming an application that has to create and destroy a few 
vertices. I was wondering if there is any protection in Giraph to 
prevent a vertex to send a message to another vertex that does not 
exist (i.e. provide a vertex id that is not associated with a vertex yet).


Is there a way to test if the destination vertex exists before sending 
the message to it?


Also, when a vertex is created, is there any source of load balancing 
or it is always kept in the worker that created it?


Best Regards,
Marco Lotz

New vertex allocation and messages

2013-08-19 Thread Marco Aurelio Barbosa Fagnani Lotz 
Hello all :)

I am programming an application that has to create and destroy a few vertices. 
I was wondering if there is any protection in Giraph to prevent a vertex to 
send a message to another vertex that does not exist (i.e. provide a vertex id 
that is not associated with a vertex yet).

Is there a way to test if the destination vertex exists before sending the 
message to it?

Also, when a vertex is created, is there any source of load balancing or it is 
always kept in the worker that created it?

Best Regards,
Marco Lotz