Github user marmbrus commented on the pull request:

    https://github.com/apache/spark/pull/10566#issuecomment-188920585
  
    > The first way is based on the constraints. If the parent join is full 
outer, the parent join will not have any IsNotNull constraint. In the current 
constraint propagation, its constraints is Set.empty[Expression]. Thus, 
$"c.int" === $"a.int" is not eligible for using the first way.
    
    Why isn't the constraint present?  We should fix that instead of inventing 
another unrelated way to reason about nullability.


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to