Skip to content
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

Closed
vishalkarve15 opened this issue Jan 22, 2024 · 2 comments
Closed

Schema mismatch error needs to be more verbose #1175

vishalkarve15 opened this issue Jan 22, 2024 · 2 comments
Assignees

Comments

@vishalkarve15
Copy link
Contributor

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.

@jster1357
Copy link

+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
* Issue #1175: Add details to schema mismatch message

* switch precision, scale to be consistent with conventions
@vishalkarve15
Copy link
Contributor Author

Fixed in version 0.41.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants