-
Notifications
You must be signed in to change notification settings - Fork 974
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: MongoDB to BigQuery breaking schema change from STRING to JSON #1834
Comments
I am unable to use the previous version of the job - only the latest version is available. I found a workaround where I will prepare the previous version of the template and host it on my end. Link to previous working image: https://console.cloud.google.com/gcr/images/dataflow-templates/global/2024-08-13-00_rc00/mongodb-to-bigquery 👉 Quick global rollback to restore soft-deleted version |
Changing data type of source_data column means all data pipelines appending data to an existing table on BigQuery by using this template should be modified. This is against backward compatibility |
Same issue here, is there any way this can be prioritized? |
CC @Polber is it necessary to fix the |
@Polber when will the merged fix be deployed for users of the template? |
Hi! Perhaps a new parameter could be added to the template, to be able to choose how to parse source_data. |
Nevermind, I see it was deployed to the GCS bucket ( |
Related Template(s)
mongodb_to_bigquery
Template Version
2024-08-20-00_rc00
What happened?
I have been using the template for a long time. I have a table in BigQuery where the
source_data
column is of type STRING (the table is appended with daily job execution). Pull Request #1796 introduces a change that alters the schema from STRING to JSON. The change in the Pull Request is not backwards compatible. I get the following error while running the job.Relevant log output
The text was updated successfully, but these errors were encountered: