add dataproc_jars to templated fields in relevant dataproc operators #3305
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.
JIRA
Description
This is a very minor change, adding only one field (
dataproc_jars
) to the list of templated fields for the various DataProc operators that submit jobs requiring jar files. Note that this field is always calleddataproc_jars
in the operators, even though each operator's constructor has a different name for this field. So the change may look a slight bit confusing, because it might appear that the templated field should vary by operator, but this is not the case.Tests
DataProcHadoopOperator
) successfully for about a month.Commits
Documentation
Code Quality
git diff upstream/master -u -- "*.py" | flake8 --diff