[GOBBLIN-1818] initilaize yarn clients in yarn app launcher so that a child class can override the yarn client creation logic #3679
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
Moved the logic of creating yarn clients out of the constructors, because child class variables are not initialized until super class is created and hence it cannot use it's own initialized variables in modifying logic in overriden methods.
This is in the continuation of [GOBBLIN-1815] Refactor yarn app launchers to support extending these classes #3671 work
Tests
trivial changes
Commits