Github user aokolnychyi commented on the issue:
    @gatorsmile I took a look at both PRs. 
    I quickly scanned  PR #14866 and did not find tests for existence joins. 
Also, `SQLConf.CROSS_JOINS_ENABLED = true` is checked only for `left_outer`. 
So, the proposed tests slightly improve the coverage. 
    PR #16762 checks everything from a different prospective than the proposed 
rules and has some unique scenarios compared to PR #14866. The main question 
that PR #16762 rises is about, for instance, inner joins with inequality 
conditions. As far as I understood, the ability to detect such cartesian 
products was the motivation to move the check away from the Optimizer. Is it 
still planned? Cannot this be also done by modifying the existing rule in the 
Optimizer? Currently, it only checks that there are conditions which reference 
to both sides. Instead, it can rely on equality predicates, right?

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to