PostgresToGoogleCloudStorageOperator - BigQuery schema type for time zone naive fields #22536
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.
Fixes #11547
The idea here is to use
DATETIME
,DATE
. andTIME
fields in bigquery when the postgres columns is defined timezone naive.(timestamp
,date
,time
<=> totimestamp without timezone
,date without timezone
andtime without timezone
)I had to modify the
convert_type
function as BigQuery cannot import data forDATETIME
,DATE
. andTIME
fields from a timestamp.I also added some tests for that function. (Similar to what we have in
airflow/providers/google/cloud/transfers/mysql_to_gcs.py
)