Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/11555#issuecomment-195122428
Got the offline inputs from @ioana-delaney.
> Using subqueries is not common, and it is only used if runtime doesn't
support a certain sequence of operations.
> Internally, when projecting columns with the same name coming from
different tables, we can use aliases to distinguish among them. That should be
the default behavior irrespective of any further optimizations that can be
applied to the generated SQL.
Basically, I think we can safely merge this PR. Fix the naming ambiguity
issues in a separate PR. Thanks!
---
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]
