Make WorkProcessor#blocking always execute futureSupplier #15711
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A common patter across operators is calling WorkProcessor#blocking to report memory usage: .blocking(() -> memoryContext.setBytes(localAggregatedMemoryContext.getBytes())); However, before this change lambda wasn't called when upstream processor yielded or was blocked. This change makes lambda to be always called which makes reporting of operator memory usage more accurate.
arhimondr
approved these changes
Jan 13, 2023
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A common patter across operators is calling WorkProcessor#blocking to report memory usage:
.blocking(() -> memoryContext.setBytes(localAggregatedMemoryContext.getBytes()));
However, before this change lambda wasn't called when upstream processor yielded or was blocked.
This change makes lambda to be always called which makes reporting of operator memory usage more accurate.
Fixes #15679
Release notes
( ) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
(x) Release notes are required, with the following suggested text: