2012/2/3 Avery Ching :
> We can diverge from the Pregel API as long as we have a good reason for it.
> I do agree that while we can support multi-graphs with a user-chosen edge
> type, some built-in support that makes programming easier sounds like a good
> goal. Andre or Claudio, feel free to op
We can diverge from the Pregel API as long as we have a good reason for
it. I do agree that while we can support multi-graphs with a
user-chosen edge type, some built-in support that makes programming
easier sounds like a good goal. Andre or Claudio, feel free to open a
JIRA to discuss this.
On Fri, Feb 3, 2012 at 6:07 PM, André Kelpe
wrote:
> 2012/2/3 Claudio Martella :
>> Hi Andre,
>
> Hi!
>
>> As I see it, we'd basically have to move all the API about edges from
>> single object to Iterable (i.e. returning multiple edges for a given
>> vertex endpoint as you suggested), and maybe a
2012/2/3 Claudio Martella :
> Hi Andre,
Hi!
> As I see it, we'd basically have to move all the API about edges from
> single object to Iterable (i.e. returning multiple edges for a given
> vertex endpoint as you suggested), and maybe also returning multiple
> vertices for a given edge(label).
If
I've certainly had multi-graph use cases in the past. I think such an
extension would be generally useful.
-- Owen
Hi Andre,
I'd be also very interested in the type of extension you're proposing.
As a matter of fact I ended up implementing that kind of vertex by
myself,
you can have an example here:
https://github.com/claudiomartella/graffiti/blob/master/src/main/java/org/acaro/graffiti/processing/Vertex.java
