[jira] [Commented] (GIRAPH-96) Support for Graphs with Huge adjacency lists
[ https://issues.apache.org/jira/browse/GIRAPH-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152101#comment-13152101 ] Gianmarco De Francisci Morales commented on GIRAPH-96: -- In my opinion this would make things too complex. I wouldn't like to keep my graph in HBase to run Giraph on it. Also, this makes HBase a dependency. I agree that this is a nice option to have but I wouldn't make it the default. Finally, a similar goal could be attained by streaming edges to disk and reading them with sequential scans when performing supersteps. This requires no network connection and should be much faster. You just need good out-of-core data structures and algorithms. > Support for Graphs with Huge adjacency lists > > > Key: GIRAPH-96 > URL: https://issues.apache.org/jira/browse/GIRAPH-96 > Project: Giraph > Issue Type: Improvement > Components: bsp >Affects Versions: 0.70.0 >Reporter: Arun Suresh > > Currently the vertex initialize() method is passed the complete adjacency > list as a HashMap. All the current concrete implementations of Vertex iterate > over the adjacency list and recreate new Data Structures within the Vertex > instance to hold/manipulate the adjacency list. This would seize to be > feasible once the size of the adjacency list becomes really huge. > I propose storing the adjacency list and all vertex information (and incoming > messages ?) in a distributed data store such as HBase. The adjacency list can > be lazily loaded via HBase Scans. I was thinking of an HBase schema where the > row Id is a concatenation of VertexID+OutboundVertexId with a single column > containing the edge. -- 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
[jira] [Commented] (GIRAPH-74) GIRAPH-36 missed a couple of liners when passing from Vertex to BasicVertex
[ https://issues.apache.org/jira/browse/GIRAPH-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150498#comment-13150498 ] Gianmarco De Francisci Morales commented on GIRAPH-74: -- Just my 2 cents. Having a field instead of a method is generally a bad thing. If you want to later change this, you need to break the API. I personally like the idea to use the return value of compute instead of having a separate halting procedure, it makes the whole process look more "functional". > GIRAPH-36 missed a couple of liners when passing from Vertex to BasicVertex > --- > > Key: GIRAPH-74 > URL: https://issues.apache.org/jira/browse/GIRAPH-74 > Project: Giraph > Issue Type: Bug > Components: graph >Affects Versions: 0.70.0 >Reporter: Claudio Martella >Assignee: Claudio Martella > Fix For: 0.70.0 > > Attachments: GIRAPH-36-cleaup.diff, GIRAPH-70.diff > > > After GIRAPH-36, in a couple of places Vertex was left instead of > BasicVertex. To achieve the fix a BasicVertex was extended with a new boolean > isHalted(boolean state) method that totally hides boolean halt field. I > believe this unifies the voteToHalt() and isHalted() methods totally hiding > the halting management of Vertices (before it was relying on the existence of > boolean halt field). -- 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
[jira] [Commented] (GIRAPH-79) Change the menu layout of the site
[ https://issues.apache.org/jira/browse/GIRAPH-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13149295#comment-13149295 ] Gianmarco De Francisci Morales commented on GIRAPH-79: -- It looks nice. But why keep project reports in the home page? Are they so important for new users? To me they look confusing, I would put them somewhere else deeper in the site. > Change the menu layout of the site > -- > > Key: GIRAPH-79 > URL: https://issues.apache.org/jira/browse/GIRAPH-79 > Project: Giraph > Issue Type: Task > Components: site >Reporter: Hyunsik Choi > Labels: site > Attachments: GIRAPH-79_1.patch > > > The current site has the basic menu layout generated by maven site plugin. > This layout is restricted to embrace new contents. > I would like to suggest the following menu layout. > http://people.apache.org/~hyunsik/giraph/site/index.html > Although the layout includes most existing contents, it has two addition > categories, Giraph and Documentation. I think that this layout is simpler and > is good to add new contents. > Anyone has any other suggestions? -- 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
