[
https://issues.apache.org/jira/browse/GIRAPH-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152373#comment-13152373
]
Jake Mannix commented on GIRAPH-83:
-----------------------------------
bq. In that Vertex is responsible for maintaining the destEdgeMap for an
implementation of Vertex, rather than implementers having to do this
themselves. For each compute invocation, the vertex shouldn't assume anything
about its outgoing edges, as they may have been mutated since the last call.
You mean that in the current Vertex class, we have the map of edges right
there? It's not really in the framework, it's in the superclass, but ok,
you're saying we *shouldn't* take care of the bookkeeping about this, and leave
it always up to the implementations (like the way that
LongDoubleFloatDoubleVertex does it with primitives)? Or that there should be
some other structure which handles them?
> Is Vertex correct yet?
> ----------------------
>
> Key: GIRAPH-83
> URL: https://issues.apache.org/jira/browse/GIRAPH-83
> Project: Giraph
> Issue Type: Improvement
> Reporter: Jakob Homan
>
> I'm seeing a number of people run into oddities with Vertex and am thinking
> we may not have it quite correct yet...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
