feat(Bigtable): add attempts headers on retry and exception logging #7428
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.
This PR adds two visibility features to the Bigtable client in
v0.221.0
(which will apply togoogle/cloud-bigtable: 1.28.3
)1. The
bigtable-attempt
header for retry attemptsIf a retryable exception is thrown, and the Bigtable client retries the call, all additional attempts will contain the header/metadata
bigtable-attempt
, which will start with "1" for the first retry and increment from there2. The
logger
option forBigtableClient
By setting a PSR3-compatible logging client, the
BigtableClient
class will log retryable or non-retryable exceptions which occur during thereadRows
streamNote: In the case of an exception, the exception message (e.g.
$e->getMessage()
) will be logged usingLoggerInterface::error
.