fix: Allows clients to expect that query performance results have been logged before they receive a response #6334
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.
Defer response messaging to
onSuccess
for allExportBuilders
that useQueryPerformanceRecorder
. This allows clients to expect that query performance results have been logged before they receive a response.Change summary:
SessionState.ExportBuilder
uses that set aQueryPerformanceRecorder
to useonSuccess
for response delivery if possibleDoExchange
subscriptions and async input table operationsonSuccess
, but completion now happens after performance results are reportedGrpcUtil
usage