[jira] [Created] (GIRAPH-121) BasicVertexResolver should implementation and VertexResolver should be interface
BasicVertexResolver should implementation and VertexResolver should be interface Key: GIRAPH-121 URL: https://issues.apache.org/jira/browse/GIRAPH-121 Project: Giraph Issue Type: Improvement Components: graph Affects Versions: 0.70.0 Reporter: Claudio Martella Assignee: Claudio Martella Priority: Trivial After change of naming in Vertex, VertexResolver and BasicVertexResolver naming should be synched. -- 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] [Created] (GIRAPH-119) VertexCombiner should work on IterableM instead of ListM
VertexCombiner should work on IterableM instead of ListM Key: GIRAPH-119 URL: https://issues.apache.org/jira/browse/GIRAPH-119 Project: Giraph Issue Type: Improvement Components: graph Affects Versions: 0.70.0 Reporter: Claudio Martella Assignee: Claudio Martella Currently VertexCombiner expects a ListM. It should be refactored to IterableM to sync with Iterable-based BasicVertex messages logics. -- 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] [Created] (GIRAPH-97) TestIdWithValueTextOutputFormat.java and IdWithValueTextOutputFormat.java missing license header
TestIdWithValueTextOutputFormat.java and IdWithValueTextOutputFormat.java missing license header Key: GIRAPH-97 URL: https://issues.apache.org/jira/browse/GIRAPH-97 Project: Giraph Issue Type: Bug Affects Versions: 0.70.0 Reporter: Claudio Martella Assignee: Claudio Martella Priority: Trivial Fix For: 0.70.0 Attachments: GIRAPH-97.diff As reported by Yingyi Bu on user mailinglist. -- 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] [Created] (GIRAPH-98) Add Claudio Martella to site
Add Claudio Martella to site Key: GIRAPH-98 URL: https://issues.apache.org/jira/browse/GIRAPH-98 Project: Giraph Issue Type: Task Reporter: Claudio Martella Attachments: GIRAPH-98.diff -- 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] [Created] (GIRAPH-94) Loading vertex ranges from HBase
Loading vertex ranges from HBase Key: GIRAPH-94 URL: https://issues.apache.org/jira/browse/GIRAPH-94 Project: Giraph Issue Type: New Feature Reporter: Claudio Martella Assignee: Claudio Martella Loading vertices from an HTable would be an option. A possible schema for storing the graph would be Hexastore (http://www.vldb.org/pvldb/1/1453965.pdf). Also, as vertices whom messages are sent to get created on the fly (if they don't exist already), we could potentially have a HBaseVertex that fetches the adjacency list + vertex value from HBase. That would be kind of a Lazy-load approach, if you can define the initial split as an HBase query. -- 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] [Created] (GIRAPH-95) vertex resolution expects MutableVertex instead of BasicVertex
vertex resolution expects MutableVertex instead of BasicVertex -- Key: GIRAPH-95 URL: https://issues.apache.org/jira/browse/GIRAPH-95 Project: Giraph Issue Type: Bug Components: graph Reporter: Claudio Martella At the beginning of the superstep, when a message is sent to non-existing vertex, the new vertex is created. This new vertex id is set through setVertexId() which belongs to MutableVertex. Should use initialize() instead. See BspRPCCommunication:948 (on my local trunk) -- 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
