-
Notifications
You must be signed in to change notification settings - Fork 826
fix(datafusion): coerce numeric literals to and from Float16 #8847
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.
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
base: main
Are you sure you want to change the base?
Changes from all commits
418926f
923c587
0dffbd9
205b25c
a636294
6e0ed01
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Large diffs are not rendered by default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding Float16 to the filtering path makes the signed-zero comparison defect newly reachable: this head returns the
-0.0row forvalue < 0.0, andvalue = 0.0returns only+0.0. That is a silent wrong-row result, not just missing coverage. #5868 records the required equality semantics, while its proposed fix #6236 is still open and is not in this PR's live base.Please either rebase after a verified signed-zero fix lands or include equivalent Float16 comparison/index-boundary handling here, then extend the special-values test to Float16 with indexed and unindexed execution.
Reproducer run against 0dffbd9
Using the same
Float16Array[-0, +0, 2048, 2050]planner/physical-expression program:Row 0 held
-0.0; row 1 held+0.0.