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

[C++] Handle nulls consistently in set membership tests (Substrait <--> Acero) #37859

Open
ianmcook opened this issue Sep 25, 2023 · 0 comments

Comments

@ianmcook
Copy link
Member

Describe the bug, including details regarding any error messages, version, and platform.

There is a TODO here:

// TODO(GH-36420) Acero does not currently handle nulls correctly

Now that #36739 is merged, can we use the new INCONCLUSIVE null matching option to translate Substrait SingularOrList expressions to/from Acero is_in function options with consistent null handling behavior?

Can we also use this new option to ensure that Substrait's index_in function is translated to/from Acero's index_in function with the correct options set to give consistent behavior?

Some other related issues:

Component(s)

C++

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant