Avery Ching commented on GIRAPH-27:

That is actually intentional, since I need to have access to the 
get/setGraphState() internally and I removed the get/setGraphState() from 
BasicVertex.  So rather than expose get/setGraphState() to the user 
(BasicVertex), I opted to to this.  I suppose we could have another interface 
internally that extended BasicVertex to allow getting and setting the graph 
state if you're concerned about exposed the vertex to the internals.  Let me 
know what you think.

> Mutable static global state in Vertex.java should be refactored
> ---------------------------------------------------------------
>                 Key: GIRAPH-27
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-27
>             Project: Giraph
>          Issue Type: Improvement
>          Components: graph
>    Affects Versions: 0.70.0
>            Reporter: Jake Mannix
>            Assignee: Jake Mannix
>         Attachments: GIRAPH-27.patch, GIRAPH-27.patch
> Vertex.java has a bunch of static methods for getting/setting global graph 
> state (total number of vertices, edges, a reference to the GraphMapper, etc). 
>  Refactoring this into a GraphState object, which every Vertex can hold onto 
> a reference to (yes, a tiny bit more memory per Vertex, but in comparison to 
> what's already in there...)

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to