Fix for issue with reading schema fields for JSON files in GCSToBigQueryOperator #28284
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3aceda7 to
905ac35
Compare
IKholopov
reviewed
Dec 14, 2022
tests/system/providers/google/cloud/gcs/example_gcs_to_bigquery_async.py
Outdated
Show resolved
Hide resolved
905ac35 to
8bb170c
Compare
20b4b95 to
ff1ed14
Compare
ff1ed14 to
9ffa97f
Compare
potiuk
approved these changes
Dec 21, 2022
Contributor
|
Thanks for fixing it up, Vlada! |
Contributor
Author
|
Thank you for helping me to improve my code :) |
84 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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 fix includes changes for issue with incorrect reading schema_fields in case of using JSON files.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an 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 a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.