Add an iterator of Traverser.Admin objects to the head/start of the traversal. Users should
typically not need to call this method. For dynamic inject of data, they should use InjectStep.
Add a single Traverser.Admin object to the head of the traversal. Users should typically not need
to call this method. For dynamic inject of data, they should use InjectStep.
Get the Step instances associated with this traversal.
The steps are ordered according to their linked list structure as defined by Step.getPreviousStep() and Step.getNextStep().
Remove a Step from the traversal. Those overriding this method should take care to reset state for
the step in the GValueManager. By default, this requirement is delegated to removeStep(int).
Type Parameters:
S2 - the new start type of the traversal (if the removed step was a start step)
E2 - the new end type of the traversal (if the removed step was an end step)
Apply the registered TraversalStrategies to the traversal.
Once the strategies are applied, the traversal is "locked" and can no longer have steps added to it.
The order of operations for strategy applications should be: globally id steps, apply each strategy in turn
to root traversal, then recursively to nested traversals.
Gets a generator that creates new TraverserSet instances for steps in the traversal. Providers may
override this default implementation to provider their own TraverserSet.
Get the TraversalSideEffects associated with the traversal. This method should not be called
externally for purposes of retrieving side-effects as traversal results. Traversal results should only be
returned by way of the execution of the traversal itself. Should a side-effect of a traversal be needed it
should only be obtained by using GraphTraversal.cap(String, String...) so that the side-effect can
be included as part of the traversal iteration. Relying on this method to get side-effects in these
situations may not result in consistent behavior across all types of executions and environments (e.g.
remoting).
Set the TraversalParentStep that is the parent of this traversal. Traversals can be nested
and this is the means by which the traversal tree is connected. If there is no parent, then it should be a
EmptyStep.
Parameters:
step - the traversal holder parent step or EmptyStep if it has no parent
Get the TraversalParentStep that is the parent of this traversal. Traversals can be nested
and this is the means by which the traversal tree is walked.
Returns:
the traversal holder parent step or EmptyStep if it has no parent.