-
Notifications
You must be signed in to change notification settings - Fork 195
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
Schema mismatch error needs to be more verbose #1175
Comments
+1 for this. Being able to see what the offending columns are would reduce overall developer friction when building pipelines. |
vishalkarve15
added a commit
to vishalkarve15/spark-bigquery-connector
that referenced
this issue
Aug 30, 2024
vishalkarve15
added a commit
to vishalkarve15/spark-bigquery-connector
that referenced
this issue
Aug 30, 2024
vishalkarve15
added a commit
to vishalkarve15/spark-bigquery-connector
that referenced
this issue
Aug 30, 2024
vishalkarve15
added a commit
to vishalkarve15/spark-bigquery-connector
that referenced
this issue
Aug 30, 2024
vishalkarve15
added a commit
that referenced
this issue
Sep 4, 2024
Fixed in version 0.41.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current error message when writing to a BigQuery table is very vague:
"Destination table's schema is not compatible with dataframe's schema"
The extent of the schema mismatch is unclear and there is no indication if only the mode check (required vs nullable) needs fixing.
spark-bigquery-connector/spark-bigquery-connector-common/src/main/java/com/google/cloud/spark/bigquery/write/context/BigQueryDirectDataSourceWriterContext.java
Line 151 in 76dc211
The text was updated successfully, but these errors were encountered: