Github user bryanjj commented on the pull request:
https://github.com/apache/spark/pull/6141#issuecomment-115977592
ok sounds good, I'll close it
---
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
GitHub user bryanjj reopened a pull request:
https://github.com/apache/spark/pull/6141
[SPARK-6380] Resolution of equi-join key in post-join projection
create a new method in LogicalPlan for resolving ambiguous references and
wrote an implentation for Project.
handles cases
Github user bryanjj closed the pull request at:
https://github.com/apache/spark/pull/6141
---
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
Github user bryanjj closed the pull request at:
https://github.com/apache/spark/pull/6141
---
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
Github user bryanjj commented on the pull request:
https://github.com/apache/spark/pull/6141#issuecomment-107102720
thanks for reviewing! the idea is to to make it easier to resolve
unnecessary ambiguous references, and SPARK-6380 is just one specific case.
---
If your project
GitHub user bryanjj opened a pull request:
https://github.com/apache/spark/pull/6141
[SPARK-6380] Resolution of equi-join key in post-join projection
create a new method in LogicalPlan for resolving ambiguous references and
wrote an implentation for Project.
handles cases like
