Get desktop application:
View/edit binary Protocol Buffers messages
Used in: ,
Contains common fiels between GiraphVertexScenario.VertexContext and GiraphMasterScenario.
Used in: ,
Information related to the exception thrown.
Used in: ,
GiraphMasterScenario captures the necessary information to replicate the environment under which user's Master.compute() function was called.
GiraphVertexScenario captures necessary information to replicate the environment under which user's Computation.compute() function was called on a particular vertex and superstep.
VertexContext encapsulates a particular pair of inputs and outputs of Computation.compute().
Used in:
TODO: We might have to break neighbor also to neighborsBefore and neighborsAfter.
The outgoing neighbors of the current vertex.
Used in:
Messages sent by the current vertex.
Used in:
VertexScenarioClasses contains the names of the user's Computation, Vertex, Vertex ID, Vertex Value, Edge Value, Incoming Message, and Outgoing Message.
Used in:
The class under test. Must implement org.apache.giraph.graph.Computation interface.
The vertex ID class (usually denoted as I). Must implement org.apache.hadoop.io.WritableComparable.
The vertex value class (usually denoted as V). Must implement org.apache.hadoop.io.Writable.
The edge value class (usually denoted as E). Must implement org.apache.hadoop.io.Writable.
The incoming message class (usually denoted as M1). Must implement org.apache.hadoop.io.Writable.
The outgoing message class (usually denoted as M2). Must implement org.apache.hadoop.io.Writable.
Stores a list of messages that are violating an integrity constraint designed by the user.
Called Extended because in scenario.proto there is another message called OutgoingMessage, which does not have the srcId.
Used in: