ExecutionInfo
for all Graph
queries.@Deprecated public interface GraphExecutionInfo
Modifier and Type | Method and Description |
---|---|
Node |
getCoordinator()
Deprecated.
The node that was used as a coordinator to successfully complete the query.
|
List<Map.Entry<Node,Throwable>> |
getErrors()
Deprecated.
The errors encountered on previous coordinators, if any.
|
Map<String,ByteBuffer> |
getIncomingPayload()
Deprecated.
The custom payload sent back by the server with the response, if any (otherwise the map will be
empty).
|
int |
getSpeculativeExecutionCount()
Deprecated.
The number of speculative executions that were started for this query.
|
GraphStatement<?> |
getStatement()
Deprecated.
The statement that was executed.
|
int |
getSuccessfulExecutionIndex()
Deprecated.
The index of the execution that completed this query.
|
List<String> |
getWarnings()
Deprecated.
The server-side warnings for this query, if any (otherwise the list will be empty).
|
GraphStatement<?> getStatement()
Node getCoordinator()
int getSpeculativeExecutionCount()
This does not include the initial, normal execution of the query. Therefore, if speculative executions are disabled, this will always be 0. If they are enabled and one speculative execution was triggered in addition to the initial execution, this will be 1, etc.
SpeculativeExecutionPolicy
int getSuccessfulExecutionIndex()
0 represents the initial, normal execution of the query, 1 the first speculative execution, etc.
SpeculativeExecutionPolicy
List<Map.Entry<Node,Throwable>> getErrors()
The list is in chronological order, based on the time that the driver processed the error responses. If speculative executions are enabled, they run concurrently so their errors will be interleaved. A node can appear multiple times (if the retry policy decided to retry on the same node).
List<String> getWarnings()
This feature is only available with DefaultProtocolVersion.V4
or above; with lower
versions, this list will always be empty.
Map<String,ByteBuffer> getIncomingPayload()
This method returns a read-only view of the original map, but its values remain inherently
mutable. If multiple clients will read these values, care should be taken not to corrupt the
data (in particular, preserve the indices by calling ByteBuffer.duplicate()
).
This feature is only available with DefaultProtocolVersion.V4
or above; with lower
versions, this map will always be empty.
Copyright © 2017–2024. All rights reserved.