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

Bug: Extra null tuples can be emitted by optional match #4861

Open
royi-luo opened this issue Feb 6, 2025 · 0 comments
Open

Bug: Extra null tuples can be emitted by optional match #4861

royi-luo opened this issue Feb 6, 2025 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@royi-luo
Copy link
Collaborator

royi-luo commented Feb 6, 2025

Kùzu version

master

What operating system are you using?

No response

What happened?

See #4240 (comment)

Optional match should output a single null tuple for each probed key that doesn't have a match. However, the current behaviour currently outputs one null tuple for each empty probed vector, which can output more null tuples than are expected. We should fix our left join to align with the expected behaviour.

Are there known steps to reproduce?

No response

@royi-luo royi-luo added the bug Something isn't working label Feb 6, 2025
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

No branches or pull requests

2 participants