[FLINK-8687] Make MaterializedCollectStreamResult#retrievePage to hav… #5647
Conversation
This file contains hidden or 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
Contributor
|
Thank you @zhangminglei. Merging... |
asfgit
pushed a commit
that referenced
this pull request
Mar 12, 2018
…vePage to have resultLock This closes #5647.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
…e resultLock
What is the purpose of the change
Currently
MaterializedCollectStreamResult#retrievePagechecks page range and calls snapshot.subList() without holding resultLock. resultLock should be taken. If we do not lock, we might see the stale data.Brief change log
Add synchronized to protect it.