Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14580
@dongjoon-hyun The root cause is not in the optimizer rule
`EliminateOuterJoin`. Your fix will reduce the chances we can eliminate the
outer-join. This is not a right fix. The existing way we handle `using joins`
might also break the other Optimizer rules.
@nsyca Thank you for your inputs. DB2 does not have such a join type (using
+ outer), based on my understanding, 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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
