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

fix: Left/right/outer joins should have nullable fields. #157

Merged
merged 1 commit into from
Jul 13, 2023

Conversation

carlyeks
Copy link
Contributor

During a left, right, or outer join, some set of fields from input become nullable because they are optionally matched in the output. For a left join, the right fields become nullable. For a right join, the left fields become nullable. For an outer join, both sets become nullable.

This test fails with assertions enabled in Calcite code because the left join should have nullable right types.

@CLAassistant
Copy link

CLAassistant commented Jul 13, 2023

CLA assistant check
All committers have signed the CLA.

@carlyeks carlyeks force-pushed the join-nullable-types branch 2 times, most recently from a2e8680 to 0f31cb3 Compare July 13, 2023 19:46
During a left, right, or outer join, some set of fields from input
become nullable because they are optionally matched in the output. For
a left join, the right fields become nullable. For a right join, the
left fields become nullable. For an outer join, both sets become
nullable.

This test fails with assertions enabled in Calcite code because the
left join should have nullable right types.
Copy link
Member

@vbarua vbarua left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fix!

@vbarua vbarua merged commit b987058 into substrait-io:main Jul 13, 2023
@carlyeks carlyeks deleted the join-nullable-types branch July 13, 2023 22:31
ajegou pushed a commit to ajegou/substrait-java that referenced this pull request Mar 29, 2024
During a left, right, or outer join, some set of fields from input
become nullable because they are optionally matched in the output. For
a left join, the right fields become nullable. For a right join, the
left fields become nullable. For an outer join, both sets become
nullable.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants