fix: Use Spark session timezone in native execution when creating Arrow schema [WIP] #2734
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.
Which issue does this PR close?
Partial fix for #2649
Rationale for this change
In native code, we had a hard-coded
UTCwhen converting Spark schema to Arrow schema.In
to_arrow_datatype:This would lead to a runtime error when running a query against a DataFrame (not a Parquet file) that is not in
UTC:What changes are included in this PR?
Pass Spark timeZoneId into native code and use that instead of hard-coded
UTC.How are these changes tested?
WIP