Repository navigation
Fixe cache level in Ingest objects - #2854
Merged
Merged
Conversation
pomadchin
force-pushed
the
fix/ingest-object
branch
from
December 18, 2018 14:37
294507c to
a837fa0
Compare
echeipesh
pushed a commit
that referenced
this pull request
Dec 28, 2018
Fixe cache level in Ingest objects
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Overview
Without this fix in some cases we can be get into the situation where this cache level (IN_MEMORY) would be assigned for the RDD, making impossible to set the desired cache level from the parameters, causing the following exception: