[GOBBLIN-1906] Add null-check to JobConfigurationUtils.putStateIntoConfiguration
to avoid IllegalArgumentException
#3770
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.
Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA
Description
A customer reported seeing:
the appears to arise from concurrent modification to the
State
's underlyingProperties
(i.e. between the time thekeySet()
is first read and when each value is accessed from the sameProperties
).although the customer's impl seems to warrant synchronization, given that a null-value is certain to be rejected by
o.a.hadoop.conf.Configuration
, defensively filter those out ahead of time.Tests
no current unit tests for this small utility method
Commits