Class TraversalVertexProgram
- java.lang.Object
-
- org.apache.tinkerpop.gremlin.process.computer.traversal.TraversalVertexProgram
-
- All Implemented Interfaces:
Cloneable,VertexProgram<TraverserSet<Object>>
public final class TraversalVertexProgram extends Object implements VertexProgram<TraverserSet<Object>>
TraversalVertexProgramenables the evaluation of aTraversalon aGraphComputer. At the start of the computation, eachVertex(orEdge) is assigned a singleTraverser. For each traverser that is local to the vertex, the vertex looks up its current location in the traversal and processes that step. If the outputted traverser of the step references a local structure on the vertex (e.g. the vertex, an incident edge, its properties, or an arbitrary object), then the vertex continues to compute the next traverser. If the traverser references another location in the graph, then the traverser is sent to that location in the graph via a message. The messages of TraversalVertexProgram are traversers. This continues until all traversers in the computation have halted.- Author:
- Marko A. Rodriguez (http://markorodriguez.com)
-
-
Nested Class Summary
Nested Classes Modifier and Type Class Description static classTraversalVertexProgram.Builder-
Nested classes/interfaces inherited from interface org.apache.tinkerpop.gremlin.process.computer.VertexProgram
VertexProgram.Features
-
-
Field Summary
Fields Modifier and Type Field Description static StringACTIVE_TRAVERSERSstatic StringHALTED_TRAVERSERSprotected static StringMUTATED_MEMORY_KEYSstatic StringTRAVERSAL-
Fields inherited from interface org.apache.tinkerpop.gremlin.process.computer.VertexProgram
VERTEX_PROGRAM
-
-
Method Summary
All Methods Static Methods Instance Methods Concrete Methods Modifier and Type Method Description static TraversalVertexProgram.Builderbuild()TraversalVertexProgramclone()When multiple workers on a single machine need VertexProgram instances, it is possible to use clone.voidexecute(Vertex vertex, Messenger<TraverserSet<Object>> messenger, Memory memory)This method denotes the main body of the computation and is executed on each vertex in the graph.VertexProgram.FeaturesgetFeatures()Set<MapReduce>getMapReducers()The set ofMapReducejobs that are associated with theVertexProgram.Set<MemoryComputeKey>getMemoryComputeKeys()TheMemorykeys that will be used during the computation.Optional<MessageCombiner<TraverserSet<Object>>>getMessageCombiner()Combine the messages in route to a particular vertex.Set<MessageScope>getMessageScopes(Memory memory)This method returns all theMessageScopepossibilities for a particular iteration of the vertex program.GraphComputer.PersistgetPreferredPersist()GraphComputer.ResultGraphgetPreferredResultGraph()PureTraversal<?,?>getTraversal()Get thePureTraversalassociated with the current instance of theTraversalVertexProgram.Set<VertexComputeKey>getVertexComputeKeys()TheElementproperties that will be mutated during the computation.static <R> TraverserSet<R>loadHaltedTraversers(org.apache.commons.configuration2.Configuration configuration)voidloadState(Graph graph, org.apache.commons.configuration2.Configuration configuration)When it is necessary to load the state of the VertexProgram, this method is called.voidsetup(Memory memory)The method is called at the beginning of the computation.static <R> voidstoreHaltedTraversers(org.apache.commons.configuration2.Configuration configuration, TraverserSet<R> haltedTraversers)voidstoreState(org.apache.commons.configuration2.Configuration configuration)When it is necessary to store the state of the VertexProgram, this method is called.booleanterminate(Memory memory)The method is called at the end of each iteration to determine if the computation is complete.StringtoString()voidworkerIterationEnd(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.voidworkerIterationStart(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.-
Methods inherited from class java.lang.Object
equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
-
Methods inherited from interface org.apache.tinkerpop.gremlin.process.computer.VertexProgram
getTraverserRequirements
-
-
-
-
Field Detail
-
TRAVERSAL
public static final String TRAVERSAL
- See Also:
- Constant Field Values
-
HALTED_TRAVERSERS
public static final String HALTED_TRAVERSERS
- See Also:
- Constant Field Values
-
ACTIVE_TRAVERSERS
public static final String ACTIVE_TRAVERSERS
- See Also:
- Constant Field Values
-
MUTATED_MEMORY_KEYS
protected static final String MUTATED_MEMORY_KEYS
- See Also:
- Constant Field Values
-
-
Method Detail
-
getTraversal
public PureTraversal<?,?> getTraversal()
Get thePureTraversalassociated with the current instance of theTraversalVertexProgram.- Returns:
- the pure traversal of the instantiated program
-
loadHaltedTraversers
public static <R> TraverserSet<R> loadHaltedTraversers(org.apache.commons.configuration2.Configuration configuration)
-
storeHaltedTraversers
public static <R> void storeHaltedTraversers(org.apache.commons.configuration2.Configuration configuration, TraverserSet<R> haltedTraversers)
-
loadState
public void loadState(Graph graph, org.apache.commons.configuration2.Configuration configuration)
Description copied from interface:VertexProgramWhen it is necessary to load the state of the VertexProgram, this method is called. This is typically required when the VertexProgram needs to be serialized to another machine. Note that what is loaded is simply the instance state, not any processed data.- Specified by:
loadStatein interfaceVertexProgram<TraverserSet<Object>>- Parameters:
graph- the graph that the VertexProgram will run againstconfiguration- the configuration to load the state of the VertexProgram from.
-
storeState
public void storeState(org.apache.commons.configuration2.Configuration configuration)
Description copied from interface:VertexProgramWhen it is necessary to store the state of the VertexProgram, this method is called. This is typically required when the VertexProgram needs to be serialized to another machine. Note that what is stored is simply the instance/configuration state, not any processed data. The default implementation provided simply stores the VertexProgram class name for reflective reconstruction. It is typically a good idea to VertexProgram.super.storeState().- Specified by:
storeStatein interfaceVertexProgram<TraverserSet<Object>>- Parameters:
configuration- the configuration to store the state of the VertexProgram in.
-
setup
public void setup(Memory memory)
Description copied from interface:VertexProgramThe method is called at the beginning of the computation. The method is global to theGraphComputerand as such, is not called for each vertex. During this stage, theMemoryshould be initialized to to its "start state."- Specified by:
setupin interfaceVertexProgram<TraverserSet<Object>>- Parameters:
memory- The global memory of the GraphComputer
-
getMessageScopes
public Set<MessageScope> getMessageScopes(Memory memory)
Description copied from interface:VertexProgramThis method returns all theMessageScopepossibilities 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.- Specified by:
getMessageScopesin interfaceVertexProgram<TraverserSet<Object>>- Parameters:
memory- an immutable form of theMemory- Returns:
- all possible message scopes during said vertex program iteration
-
execute
public void execute(Vertex vertex, Messenger<TraverserSet<Object>> messenger, Memory memory)
Description copied from interface:VertexProgramThis method denotes the main body of the computation and is executed on each vertex in the graph. This method is logically executed in parallel on all vertices in the graph. When theMemoryis read, it is according to the aggregated state yielded in the previous iteration. When theMemoryis written, the data will be aggregated at the end of the iteration for reading in the next iteration.- Specified by:
executein interfaceVertexProgram<TraverserSet<Object>>- Parameters:
vertex- theVertexto execute theVertexProgramonmessenger- the messenger that moves data between verticesmemory- the shared state between all vertices in the computation
-
terminate
public boolean terminate(Memory memory)
Description copied from interface:VertexProgramThe method is called at the end of each iteration to determine if the computation is complete. The method is global to theGraphComputerand as such, is not called for eachVertex. TheMemorymaintains the aggregated data from the last execute() iteration.- Specified by:
terminatein interfaceVertexProgram<TraverserSet<Object>>- Parameters:
memory- The global memory of theGraphComputer- Returns:
- whether or not to halt the computation
-
workerIterationStart
public void workerIterationStart(Memory memory)
Description copied from interface:VertexProgramThis 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. The vertex set is split into subsets and a worker is assigned to call theVertexProgram.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.- Specified by:
workerIterationStartin interfaceVertexProgram<TraverserSet<Object>>- Parameters:
memory- The memory at the start of the iteration.
-
workerIterationEnd
public void workerIterationEnd(Memory memory)
Description copied from interface:VertexProgramThis 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. The vertex set is split into subsets and a worker is assigned to call theVertexProgram.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.- Specified by:
workerIterationEndin interfaceVertexProgram<TraverserSet<Object>>- Parameters:
memory- The memory at the end of the iteration.
-
getVertexComputeKeys
public Set<VertexComputeKey> getVertexComputeKeys()
Description copied from interface:VertexProgramTheElementproperties 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.- Specified by:
getVertexComputeKeysin interfaceVertexProgram<TraverserSet<Object>>- Returns:
- the set of element keys that will be mutated during the vertex program's execution
-
getMemoryComputeKeys
public Set<MemoryComputeKey> getMemoryComputeKeys()
Description copied from interface:VertexProgramTheMemorykeys that will be used during the computation. These are the only keys that can be read or written throughout the life of theGraphComputer. The default is an empty set.- Specified by:
getMemoryComputeKeysin interfaceVertexProgram<TraverserSet<Object>>- Returns:
- the set of memory keys that will be read/written
-
getMapReducers
public Set<MapReduce> getMapReducers()
Description copied from interface:VertexProgramThe set ofMapReducejobs that are associated with theVertexProgram. This is not necessarily the exhaustive list over the life of theGraphComputer. If MapReduce jobs are declared by GraphComputer.mapReduce(), they are not contained in this set. The default is an empty set.- Specified by:
getMapReducersin interfaceVertexProgram<TraverserSet<Object>>- Returns:
- the set of
MapReducejobs associated with thisVertexProgram
-
getMessageCombiner
public Optional<MessageCombiner<TraverserSet<Object>>> getMessageCombiner()
Description copied from interface:VertexProgramCombine the messages in route to a particular vertex. Useful to reduce the amount of data transmitted over the wire. For example, instead of sending two objects that will ultimately be merged at the vertex destination, merge/combine into one and send that object. If no message combiner is provider, then no messages will be combined. Furthermore, it is not guaranteed the all messages in route to the vertex will be combined and thus, combiner-state should not be used. The result of the vertex program algorithm should be the same regardless of whether message combining is executed or not.- Specified by:
getMessageCombinerin interfaceVertexProgram<TraverserSet<Object>>- Returns:
- A optional denoting whether or not their is a message combine associated with the vertex program.
-
clone
public TraversalVertexProgram clone()
Description copied from interface:VertexProgramWhen multiple workers on a single machine need VertexProgram instances, it is possible to use clone. This will provide a speedier way of generating instances, over theVertexProgram.storeState(org.apache.commons.configuration2.Configuration)andVertexProgram.loadState(org.apache.tinkerpop.gremlin.structure.Graph, org.apache.commons.configuration2.Configuration)model. The default implementation simply returns the object as it assumes that the VertexProgram instance is a stateless singleton.- Specified by:
clonein interfaceVertexProgram<TraverserSet<Object>>- Overrides:
clonein classObject- Returns:
- A clone of the VertexProgram object
-
getPreferredResultGraph
public GraphComputer.ResultGraph getPreferredResultGraph()
- Specified by:
getPreferredResultGraphin interfaceVertexProgram<TraverserSet<Object>>
-
getPreferredPersist
public GraphComputer.Persist getPreferredPersist()
- Specified by:
getPreferredPersistin interfaceVertexProgram<TraverserSet<Object>>
-
getFeatures
public VertexProgram.Features getFeatures()
- Specified by:
getFeaturesin interfaceVertexProgram<TraverserSet<Object>>
-
build
public static TraversalVertexProgram.Builder build()
-
-