Description
ScanningResultIterator drops dummy results and retries Result#next() in a loop as part of the Phoenix server paging feature.
ScanningResultIterator does not check if the query has already timed out currently. This means that ScanningResultIterator let the server to work on the scan even though the Phoenix query is already timed out. ScanningResultIterator should check if the query of the scan has been timed out and if so should return an operation timeout exception as BaseResultIterators does.
Attachments
Issue Links
- causes
-
PHOENIX-7102 phoenix-connectors doesn't compile with core HEAD
-
- Resolved
-
- links to