fix(cubesql): Support explicit UTC as timezone in pushdown SQL generation #8971
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.
Check List
Issue Reference this PR resolves
#8967
Description of Changes Made (if issue reference is not provided)
cubesql can introduce
ScalarValue::TimestampNanosecond(..., Some("UTC"))
during constant folding, andgenerate_sql_for_expr
trips on unsupported timezones.This PR just allows
None
as well asSome("UTC")
as timezones. Because DataFusion will always generateUTC
, it should be fine for now.See https://github.com/cube-js/arrow-datafusion/blob/dcf3e4aa26fd112043ef26fa4a78db5dbd443c86/datafusion/physical-expr/src/datetime_expressions.rs#L357-L367