feat: surface retry
param to Table.read_row
api
#982
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.
what ? ( ̄^ ̄ゞ
this pr surfaces a
retry
param forTable.read_row
. this param defaults toDEFAULT_RETRY_READ_ROWS
just as it does forTable.read_rows
. it then passes forward into theTable.read_rows
callwhy ? („• ᴗ •„)
in the case where a caller may want to override the default
retry
param for theTable.read_row
api, they currently must switch to usingTable.read_rows
and add their own code for pulling the first item out of the iterator and guarding against multi-row responses (which are functionalities thatTable.read_row
already provides)in an ideal world, the
Table.read_row
helper method can accept and pass along the retry param so that clients don't need to write their own duplicate implementations wrappingTable.read_rows
~related issue ౨ৎ⋆˚。⋆
implements #941