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.

Sign up for GitHub

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

Jump to bottom

chr: Error mismatch between Velox and Presto. #12535

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

chr: Error mismatch between Velox and Presto. #12535

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

Comments

@peterenescu
Copy link
Contributor

peterenescu commented Mar 5, 2025 •
edited
Loading

Description

Function chr has different error output between Velox and Presto. Error causes fuzzer failures.

Reproduction

Velox:

presto:di> select chr(c0) from (values (6182359718462173641) ) t(c0);
Query 20250305_000203_00002_rd7dj failed: validCodePoint Not a valid Unicode code point: 6182359718462173641 Top-level Expression: presto.default.chr(field)

Presto:

presto> select chr(6182359718462173641);
Query 20250305_000149_00001_w2c2g failed: Not a valid Unicode code point: 6182359718462173641
@peterenescu peterenescu added bug Something isn't working fuzzer-found labels Mar 5, 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
Assignees
No one assigned
Labels
bug Something isn't working fuzzer-found
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@peterenescu