Skip to content

fix: BigQuery test command failure for fields with FLOAT or BOOLEAN types #1003

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.

Sign up for GitHub

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

Merged
jochenchrist merged 1 commit into from
Jan 9, 2026
Merged

fix: BigQuery test command failure for fields with FLOAT or BOOLEAN types #1003

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- Restrict DuckDB dependency to < 1.4.0 (#972)
- Fixed schema evolution support for optional fields in CSV and Parquet formats. Optional fields marked with `required: false` are no longer incorrectly treated as required during validation, enabling proper schema evolution where optional fields can be added to contracts without breaking validation of historical data files (#977)
- Fixed decimals in pydantic model export. Fields marked with `type: decimal` will be mapped to `decimal.Decimal` instead of `float`.
- Fix BigQuery test failure for fields with FLOAT or BOOLEAN types by mapping them to equivalent types (BOOL and FLOAT64)

## [0.11.2] - 2025-12-15

Expand Down
4 changes: 2 additions & 2 deletions datacontract/export/bigquery_exporter.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,8 +113,8 @@ def map_type_to_bigquery(prop: SchemaProperty) -> str:
# If physicalType is already a BigQuery type, return it directly
if prop.physicalType:
bq_types = {
"STRING", "BYTES", "INT64", "INTEGER", "FLOAT64", "FLOAT", "NUMERIC",
"BIGNUMERIC", "BOOL", "BOOLEAN", "TIMESTAMP", "DATE", "TIME", "DATETIME",
"STRING", "BYTES", "INT64", "INTEGER", "FLOAT64", "NUMERIC",
"BIGNUMERIC", "BOOL", "TIMESTAMP", "DATE", "TIME", "DATETIME",
"GEOGRAPHY", "JSON", "RECORD", "STRUCT", "ARRAY"
}
if prop.physicalType.upper() in bq_types or prop.physicalType.upper().startswith(("STRUCT<", "ARRAY<", "RANGE<")):
Expand Down
Loading