Move source_objects datatype check out of GCSToBigQueryOperator.__init__ #20347
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.
Closes: #20333
Currently there is a datatype check on
source_objectswithin theGCSToBigQueryOperator.__init__()method. This is a template field for the operator. If a user tries to pass in anXComvalue that will be rendered as a list (i.e.render_template_as_native_obj=Trueat the DAG level), the datatype check incorrectly assumes the value is a string and wraps the value in a list. When theXComvalue is then rendered duringexecute()the value becomes aList[List]instead of the desiredListtype.Moving this datatype check into the
execute()method of the operator will allow any template rendering to occur before the check is performed.^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.