Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/14580
Hi, @nsyca .
Thank you for comment. But, that's not a correct reason not to use `full
outer` in combination with `using`. They can be used together. The root cause
of your example problem is the `EliminateOuterJoin` do optimize too much. This
PR aims to reduce the scope of this optimizer. After this PR, your example will
be handled like the following. (This is the result of this PR.)
```
scala> sql("select coalesce(A.A,B.A), A.A, B.A from A full join B on
A.A=B.A where coalesce(A.A,B.A) is not null").show
+--------------+----+----+
|coalesce(A, A)| A| A|
+--------------+----+----+
| 1| 1|null|
| 3|null| 3|
| 2| 2| 2|
+--------------+----+----+
```
How do you think about this PR?
---
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]
