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

ScalarFunctionExpr does not preserve the nullable flag on serialization roundtrip #13829

Closed
ccciudatu opened this issue Dec 18, 2024 · 0 comments · Fixed by #13830
Closed

ScalarFunctionExpr does not preserve the nullable flag on serialization roundtrip #13829

ccciudatu opened this issue Dec 18, 2024 · 0 comments · Fixed by #13830
Labels
bug Something isn't working

Comments

@ccciudatu
Copy link
Contributor

Describe the bug

A physical plan that contains scalar functions will always set the nullable flag to true after deserialization.

To Reproduce

The coalesce function results in a non-nullable field. However, if the plan is serialized and deserialized, the same field will be nullable.
A test to showcase exactly this will be included in the upcoming PR.

Expected behavior

The plan schema should stay the same after a roundtrip.

Additional context

No response

@ccciudatu ccciudatu added the bug Something isn't working label Dec 18, 2024
@findepi findepi changed the title ScalarFunctionExpr does not preserve the nullable flag on roundtrip ScalarFunctionExpr does not preserve the nullable flag on serialization roundtrip Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant