You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Thanks for raising the issue! The root cause is there is no physical operator for WHERE conditions on top of Join operator to perform the post-processing for now. We missed this semantic error in the testing because we used and assumed existing Nested Loop join is correct (which actually has the same issue) and didn't realized the difference in other RDBMS.
To fix the issue, a new operator should be included in physical plan in which WHERE conditions be translated into in-memory operation in Java code. To make it simple, we can start with support for very basic operation such as =, <, > etc.
Issue
The WHERE clause doesn't filter out the null value from right table after LEFT JOIN.
LEFT JOIN query
Sample Data
Actual Result
Expected Result
The text was updated successfully, but these errors were encountered: