public interface RemoteConnection extends AutoCloseable
Traversal
and
returning results. Results refer to both the Iterator
of results from the submitted Traversal
as well as the side-effects produced by that Traversal
. Those results together are wrapped in a
Traversal
.Modifier and Type | Field and Description |
---|---|
static String |
GREMLIN_REMOTE |
static String |
GREMLIN_REMOTE_CONNECTION_CLASS |
Modifier and Type | Method and Description |
---|---|
static RemoteConnection |
from(Configuration conf)
Create a
RemoteConnection from a Configuration object. |
<E> RemoteTraversal<?,E> |
submit(Bytecode bytecode)
Deprecated.
As of release 3.2.4, replaced by
submitAsync(Bytecode) . |
<E> Iterator<Traverser.Admin<E>> |
submit(Traversal<?,E> traversal)
Deprecated.
As of release 3.2.2, replaced by
submitAsync(Bytecode) . |
default <E> CompletableFuture<RemoteTraversal<?,E>> |
submitAsync(Bytecode bytecode)
|
close
static final String GREMLIN_REMOTE
static final String GREMLIN_REMOTE_CONNECTION_CLASS
@Deprecated <E> Iterator<Traverser.Admin<E>> submit(Traversal<?,E> traversal) throws RemoteConnectionException
submitAsync(Bytecode)
.RemoteConnectionException
@Deprecated <E> RemoteTraversal<?,E> submit(Bytecode bytecode) throws RemoteConnectionException
submitAsync(Bytecode)
.Traversal
Bytecode
to a server and returns a RemoteTraversal
.
The RemoteTraversal
is an abstraction over two types of results that can be returned as part of the
response from the server: the results of the Traversal
itself and the side-effects that it produced.RemoteConnectionException
default <E> CompletableFuture<RemoteTraversal<?,E>> submitAsync(Bytecode bytecode) throws RemoteConnectionException
Traversal
Bytecode
to a server and returns a promise of a RemoteTraversal
.
The RemoteTraversal
is an abstraction over two types of results that can be returned as part of the
response from the server: the results of the Traversal
itself and the side-effects that it produced.
The default implementation calls the submit(Bytecode)
method for backward compatibility, but generally
speaking this method should be implemented directly as submit(Bytecode)
is not called directly by
any part of TinkerPop. Even if the RemoteConnection
itself is not capable of asynchronous behaviour, it
should simply implement this method in a blocking form.RemoteConnectionException
static RemoteConnection from(Configuration conf)
RemoteConnection
from a Configuration
object. The configuration must contain a
gremlin.remote.remoteConnectionClass
key which is the fully qualified class name of a
RemoteConnection
class.Copyright © 2013–2019 Apache Software Foundation. All rights reserved.