Skip to content
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

from_ieee754_32: Error mismatch between Presto and Velox #12532

Closed
peterenescu opened this issue Mar 4, 2025 · 1 comment
Closed

from_ieee754_32: Error mismatch between Presto and Velox #12532

peterenescu opened this issue Mar 4, 2025 · 1 comment
Labels
bug Something isn't working fuzzer-found

Comments

@peterenescu
Copy link
Contributor

peterenescu commented Mar 4, 2025

Description

Function from_ieee754_32 produces different error output between Presto and Velox. Error mismatch causes fuzzer failures and has to be added to skip list for.

Reproduction

Presto:

presto:di> select from_ieee754_32(VARBINARY '\4BD[m&c_t3ws[uOn=A<el$]mb_Jc(30nZ6@jbL9&H');
Query 20250304_231231_00057_rd7dj failed: Input floating-point value must be exactly 4 bytes long

Velox:

presto:di> select from_ieee754_32(c0) from (values (VARBINARY '\4BD[m&c_t3ws[uOn=A<el$]mb_Jc(30nZ6@jbL9&H')) t(c0);
Query 20250304_231259_00058_rd7dj failed: input.size() == kTypeLength (42 vs. 4) Input floating-point value must be exactly 4 bytes long Top-level Expression: presto.default.from_ieee754_32(field)
@peterenescu peterenescu added bug Something isn't working fuzzer-found labels Mar 4, 2025
@peterenescu
Copy link
Contributor Author

Actual issue caused by fuzzer default null handling: #12548

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working fuzzer-found
Projects
None yet
Development

No branches or pull requests

1 participant