Fix f16 to f32 coercion to meet Trino f32 minimum#64
Merged
jackye1995 merged 1 commit intoMar 10, 2026
Merged
Conversation
31bd519 to
542eebf
Compare
2c5e755 to
d44951b
Compare
d44951b to
76cabf6
Compare
jackye1995
approved these changes
Mar 10, 2026
jackye1995
left a comment
Collaborator
There was a problem hiding this comment.
Looks good to me, thanks for the fix!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes
Fixes issue where f16 columns were incorrectly being casted to f32. Since Trino does not support float values with width < 32bits, this widens f16 columns to f32 when doing reads to prevent this issue.
Stacktrace: