public static class ProgramTest.TestProgram extends Object implements VertexProgram
VertexProgram.Builder, VertexProgram.FeaturesVERTEX_PROGRAM| Constructor and Description |
|---|
TestProgram() |
| Modifier and Type | Method and Description |
|---|---|
ProgramTest.TestProgram |
clone()
When multiple workers on a single machine need VertexProgram instances, it is possible to use clone.
|
void |
execute(Vertex vertex,
Messenger messenger,
Memory memory)
This method denotes the main body of the computation and is executed on each vertex in the graph.
|
Set<MemoryComputeKey> |
getMemoryComputeKeys()
The
Memory keys that will be used during the computation. |
Set<MessageScope> |
getMessageScopes(Memory memory)
This method returns all the
MessageScope possibilities for a particular iteration of the vertex program. |
GraphComputer.Persist |
getPreferredPersist() |
GraphComputer.ResultGraph |
getPreferredResultGraph() |
Set<VertexComputeKey> |
getVertexComputeKeys()
The
Element properties that will be mutated during the computation. |
void |
loadState(Graph graph,
Configuration configuration)
When it is necessary to load the state of the VertexProgram, this method is called.
|
void |
setup(Memory memory)
The method is called at the beginning of the computation.
|
void |
storeState(Configuration configuration)
When it is necessary to store the state of the VertexProgram, this method is called.
|
boolean |
terminate(Memory memory)
The method is called at the end of each iteration to determine if the computation is complete.
|
void |
workerIterationEnd(Memory memory)
This method is called at the end of each iteration of each "computational chunk."
The set of vertices in the graph are typically not processed with full parallelism.
|
void |
workerIterationStart(Memory memory)
This method is called at the start of each iteration of each "computational chunk."
The set of vertices in the graph are typically not processed with full parallelism.
|
equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitcreateVertexProgram, getFeatures, getMapReducers, getMessageCombiner, getTraverserRequirementspublic void loadState(Graph graph, Configuration configuration)
VertexProgramloadState in interface VertexProgramgraph - the graph that the VertexProgram will run againstconfiguration - the configuration to load the state of the VertexProgram from.public void storeState(Configuration configuration)
VertexProgramstoreState in interface VertexProgramconfiguration - the configuration to store the state of the VertexProgram in.public void setup(Memory memory)
VertexProgramGraphComputer and as such, is not called for each vertex.
During this stage, the Memory should be initialized to to its "start state."setup in interface VertexProgrammemory - The global memory of the GraphComputerpublic void execute(Vertex vertex, Messenger messenger, Memory memory)
VertexProgramMemory is read, it is according to the aggregated state yielded in the previous iteration.
When the Memory is written, the data will be aggregated at the end of the iteration for reading in the next iteration.execute in interface VertexProgramvertex - the Vertex to execute the VertexProgram onmessenger - the messenger that moves data between verticesmemory - the shared state between all vertices in the computationpublic boolean terminate(Memory memory)
VertexProgramGraphComputer and as such, is not called for each Vertex.
The Memory maintains the aggregated data from the last execute() iteration.terminate in interface VertexProgrammemory - The global memory of the GraphComputerpublic void workerIterationStart(Memory memory)
VertexProgramVertexProgram.execute(org.apache.tinkerpop.gremlin.structure.Vertex, org.apache.tinkerpop.gremlin.process.computer.Messenger<M>, org.apache.tinkerpop.gremlin.process.computer.Memory) method.
The default implementation is a no-op.workerIterationStart in interface VertexProgrammemory - The memory at the start of the iteration.public void workerIterationEnd(Memory memory)
VertexProgramVertexProgram.execute(org.apache.tinkerpop.gremlin.structure.Vertex, org.apache.tinkerpop.gremlin.process.computer.Messenger<M>, org.apache.tinkerpop.gremlin.process.computer.Memory) method.
The default implementation is a no-op.workerIterationEnd in interface VertexProgrammemory - The memory at the end of the iteration.public Set<VertexComputeKey> getVertexComputeKeys()
VertexProgramElement properties that will be mutated during the computation.
All properties in the graph are readable, but only the keys specified here are writable.
The default is an empty set.getVertexComputeKeys in interface VertexProgrampublic Set<MemoryComputeKey> getMemoryComputeKeys()
VertexProgramMemory keys that will be used during the computation.
These are the only keys that can be read or written throughout the life of the GraphComputer.
The default is an empty set.getMemoryComputeKeys in interface VertexProgrampublic Set<MessageScope> getMessageScopes(Memory memory)
VertexProgramMessageScope possibilities for a particular iteration of the vertex program.
The returned messages scopes are the scopes that will be used to send messages during the stated iteration.
It is not a requirement that all stated messages scopes be used, just that it is possible that they be used during the iteration.getMessageScopes in interface VertexProgrammemory - an immutable form of the Memorypublic ProgramTest.TestProgram clone()
VertexProgramVertexProgram.storeState(Configuration) and VertexProgram.loadState(org.apache.tinkerpop.gremlin.structure.Graph, Configuration) model.
The default implementation simply returns the object as it assumes that the VertexProgram instance is a stateless singleton.clone in interface VertexProgramclone in class Objectpublic GraphComputer.ResultGraph getPreferredResultGraph()
getPreferredResultGraph in interface VertexProgrampublic GraphComputer.Persist getPreferredPersist()
getPreferredPersist in interface VertexProgramCopyright © 2013–2016 Apache Software Foundation. All rights reserved.