fix: Make Java gRPC client use timeouts as expected #4237
Merged
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 does / why we need it:
In my previous PR I added deadlines to the gRPC stub used in Java
FeastClient
, however deadlines in gRPC don't behave like timeouts and in that PR are only set once when the client is constructed, causing requests after construction to fail with deadline exceeded even though the time they took was was within the deadline the used thought they had set up; here's an example of the issue:The
getOnlineFeatures(...)
call would exceed the deadline even if it took 1ms.The official gRPC examples show the correct usage for adding timeouts is to create a copy stub with a new deadline setup for every new request as shown here, which is what is included in this PR.
Which issue(s) this PR fixes:
N/A
Fixes
N/A