TEZ-4091: UnorderedPartitionedKVWriter::readDataForDME should check i… #53
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
…f in-mem file is flushed or not
|
Thanks @sidseth . |
abstractdog
pushed a commit
to abstractdog/tez
that referenced
this pull request
Nov 7, 2019
…f in-mem file is flushed or not (apache#53)
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.
Changes:
It is possible that in-mem writer spilled over to disk. Need to use that path as finalOutPath and set its permission. Otherwise it would lead to NPE in
readDataForDMEas it may not havefinalOutPathRelevant permissions have to be setup in the file being written out by in-mem writer (i.e after spill)