danieljbruce
danieljbruce
Look at the TestReadRows_Generic_Headers test to see latency of a single call.
Show that there is latency in the client without any changes to gax. This will provide a useful benchmark against the gax changes for measuring latency.
Another test for latency in Bigtable. Removes parameters that will set the retry properties and relies on retries set in a lower level.
Try this experiment and see what the conformance test results deliver.
This is a PR used to see where the system tests fail in kokoro so that we can pinpoint the line of code that is causing the problem.
**Source code changes** The current code calls `getResumptionRequestFn` twice when the result from the first call can be reused. For clients implementing retries, we only want one call to `getResumptionRequestFn`...
**Summary** This PR contains the changes required for allowing users to make Authorized Views requests on the Data plane. The changes have already been reviewed in the following PRs: https://github.com/googleapis/nodejs-bigtable/pull/1463...
**Summary:** We intend to make code changes to ensure that ReadRows retries doesn't re-request data the server has already sent back. In order to guarantee that the client doesn't re-request...
This PR adds a test that will consistently fail without the patch from https://github.com/googleapis/nodejs-bigtable/pull/1453/files in place. If there are data duplication issues in the future then having this test in...
**Summary:** This PR offers a long term fix ensuring that when retryable errors occur that the user will not experience data loss nor will duplicate data be delivered to them....