public class DriverRemoteTraversal<S,E> extends AbstractRemoteTraversal<S,E>
AbstractRemoteTraversal
implementation for the Gremlin Driver. This Traversal
implementation is
typically iterated from RemoteStep
where the nextTraverser()
method is called. While this class
provides implementations for both next()
and hasNext()
that unroll "bulked" results, those methods
are not called directly from with TinkerPop remoting.Traversal.Admin<S,E>, Traversal.Exceptions, Traversal.Symbols
Constructor and Description |
---|
DriverRemoteTraversal(ResultSet rs,
Client client,
boolean attach,
Optional<Configuration> conf) |
Modifier and Type | Method and Description |
---|---|
void |
close()
Releases server-side resources related to this traversal (i.e.
|
RemoteTraversalSideEffects |
getSideEffects()
Deprecated.
as of release 3.3.8, not directly replaced, see
Admin#getSideEffects() for more information,
but further note that this method is not being removed, but will not be functional for remote execution. Prefer
GraphTraversal.cap(String, String...) to get side-effects as part of traversal iteration. |
boolean |
hasNext() |
E |
next() |
Traverser.Admin<E> |
nextTraverser()
Note that internally
#nextTraverser() is called from within a loop (specifically in
AbstractStep.next() that breaks properly when a NoSuchElementException is thrown. |
addStep, applyStrategies, clone, getBytecode, getGraph, getParent, getSteps, getStrategies, getTraverserGenerator, getTraverserRequirements, isLocked, removeStep, setGraph, setParent, setSideEffects, setStrategies
equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
addStart, addStarts, addStep, equals, getEndStep, getStartStep, removeStep, reset
@Deprecated public RemoteTraversalSideEffects getSideEffects()
Admin#getSideEffects()
for more information,
but further note that this method is not being removed, but will not be functional for remote execution. Prefer
GraphTraversal.cap(String, String...)
to get side-effects as part of traversal iteration.DriverRemoteTraversal
that spawned this as the side-effect will not be ready. Generally
speaking, the common user would not get side-effects this way - they would use a call to cap()
.public boolean hasNext()
public E next()
public Traverser.Admin<E> nextTraverser()
AbstractRemoteTraversal
#nextTraverser()
is called from within a loop (specifically in
AbstractStep.next()
that breaks properly when a NoSuchElementException
is thrown. In
other words the "results" should be iterated to force that failure.nextTraverser
in interface Traversal.Admin<S,E>
nextTraverser
in class AbstractRemoteTraversal<S,E>
Copyright © 2013–2020 Apache Software Foundation. All rights reserved.