Bug fix in AWS glue operator related to num_of_dpus #19787 #21353
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.
This pull request is to fix an inconsistency and bug found during testing in #21348. This is an additional fix to the issue solved in #19787.
This pull request is in accordance with #21348 (comment)
In the
AWSGlueJobOperator
(file path:airflow/providers/amazon/aws/operators/glue.py
), I have changed the default value ofnum_of_dpus
from6
toNone
.Without this fix, it becomes inconsistent with the logic changed in the airflow/providers/amazon/aws/hooks/glue.py. In the
AWSGlueJobOperator
script, if the user does not want to specify thenum_of_dpus
, then also the__init__
function is default initializing it to6
(which gives the error below). Currently, to get around it, the user has to specifynum_of_dpus=None
to run without error. This fix solves this issue.