fix: [df52] route timestamp timezone mismatches through spark_parquet_convert #3494
+12
−3
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.
Summary
Timestamp(us, None)by DataFusion were being routed through Spark'sCastexpression when the logical schema expectedTimestamp(us, Some("UTC")). Spark's Cast treatsNone-timezone as TimestampNTZ (local time) and applies a timezone conversion, shifting values by the session timezone offset (e.g., -5h45m for Asia/Kathmandu)Timestamp -> Timestampmismatches throughCometCastColumnExprwhich delegates tospark_parquet_convert, handling this as a metadata-only timezone relabelTest plan
CometJoinSuiteshould now passparquet_roundtrip_int_as_string,parquet_roundtrip_unsigned_int) continue to pass🤖 Generated with Claude Code