Joh, Etienne and Avery,
Thank you all for your replies. I have settled on using a container class with
different functionalities implemented with in it, and one message type that
wraps all the different types of messages.
Avery and Jon: I ended up with the same conclusion that a parametrized
Hi Nick,
Giraph needs to have be able to instantiate the vertex id, value,
edges, and messages and there can only be a single type for each
of them.
That being said, since all the types are user chosen, you can
basically implement types that su
Nick,
I am guessing it is because Giraph needs to move vertices around and needs
to construct them before it reads in their serialization. I am new to
Giraph myself so this may be incorrect. Maybe Avery could comment.
Jon
On Fri, Jul 27, 2012 at 6:32 AM, Nick West wrote:
> Thanks for the quic
Hi,
I am not sure to say something stupid or not but if you have two kind of
vertexes,
meaning is there are different in there values... I would looking at doing
something
this way. Have a Writable type which offer options and different
functionalities.
Accessing it from a getVertexValue(). You ca
Thanks for the quick reply.
That (using one uber-class) was my initial thought when I ran into this
problem, however I was wondering if there was a solution that would use the
type hierarchy (which admittedly is a bit more flexible in scala than java, so
this may not be possible). Is there som
Nick,
You may want to reconsider your approach as I don't think Giraph will be
happy with this.
How about using a new vertex value class with BasicVertex which can do both
behaviours for you? Same for edge and message classes. This should be
enough do what you want.
Jon
On Wed, Jul 25, 2012 at
Hi,
I'm working on implementing a belief propagation algorithm over Giraph. (Do
you know if anyone has done this before?) This requires having (at least) two
different types of vertices implemented (values and factors) and different
types of messages sent between different vertices.
I've bee
