public interface ContinuousResultSet extends ResultSet
It uses asynchronous calls internally, but blocks on the results in order to provide a synchronous API to its clients. If the query is paged, only the first page will be fetched initially, and iteration will trigger background fetches of the next pages when necessary.
Note that this object can only be iterated once: rows are "consumed" as they are read,
subsequent calls to
iterator() will return the same iterator instance.
Implementations of this type are not thread-safe. They can only be iterated by the
thread that invoked
|Modifier and Type||Method and Description|
Cancels the continuous query.
The execution information for the last query performed for this iterable.
all, getAvailableWithoutFetching, getColumnDefinitions, getExecutionInfos, isFullyFetched, map, one, spliterator
There might still be rows available in the current page after the cancellation; the iteration will only stop when such rows are fully iterated upon.
Also, there might be more pages available in the driver's local page cache after the cancellation; these extra pages will be discarded.
Therefore, if you plan to resume the iteration later, the correct procedure is as follows:
@NonNull default ExecutionInfo getExecutionInfo()
This is a shortcut for:
getExecutionInfos().get(getExecutionInfos().size() - 1)
Note: because the driver does not support query traces for continuous queries,
ExecutionInfo.getTracingId() will always be
Copyright © 2017–2020. All rights reserved.