Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
M3
-
None
Description
At the moment, both Java and C++ clients set call_Seq_id, but the scanner backend ignores it. The PB says:
// The sequence ID of this call. The sequence ID should start at 0 // with the request for a new scanner, and after each successful request, // the client should increment it by 1. When retrying a request, the client // should _not_ increment this value. If the server detects that the client // missed a chunk of rows from the middle of a scan, it will respond with an // error.
The backend ought to verify that:
- The ID of a new scan is 0.
- Each subsequent scan request increments the ID by 1.