Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify handling of V2 'ReadRowsResponse' error cases #1915

Merged
merged 2 commits into from
Jun 27, 2016
Merged

Clarify handling of V2 'ReadRowsResponse' error cases #1915

merged 2 commits into from
Jun 27, 2016

Conversation

tseaver
Copy link
Contributor

@tseaver tseaver commented Jun 27, 2016

Distinguish response-level errors from invalid chunks.

JSON testcases ending in an incomplete row should not raise errors.

For "invalid" JSON testcases, verify that completed, non-error rows match expected results.

Assert that the state is 'ROW_IN_PROGRESS', and check that the completed
rows match the expected results.
@tseaver tseaver added the api: bigtable Issues related to the Bigtable API. label Jun 27, 2016
@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Jun 27, 2016
Verify that completed, non-error rows match expected results after an
invalid chunk testcase.
@tseaver tseaver merged commit fcc3751 into googleapis:bigtable-v2 Jun 27, 2016
@tseaver tseaver deleted the bigtable-v2-readrowsresponse-error-cases branch June 27, 2016 16:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: bigtable Issues related to the Bigtable API. cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants