fix(spanner): correct handling of PartialResultSet.resume_token #8521
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problems:
google::spanner::v1::PartialResultSet
may not containa
resume_token
when it also does not complete a new row,so
last_resume_token_
should not be updated in that case.PartialResultSetResume::Read()
uses its factory andlast_resume_token_
to create a newPartialResultSetReader
,it should inform the
PartialResultSetSource
so that anypartly-constructed row can be discarded before processing
the resumed stream (which will resend that row).
That is, a "resume token" is really a row iterator, and a level
above row fragmentation and value chunking. So fix all of that.
Then expand the
ConnectionImplTest.ReadSuccess
test case toexercise the new code paths.
This change is