Github user ioana-delaney commented on the issue:
https://github.com/apache/spark/pull/13867
With the ongoing changes to the subquery design, queries with deep
correlation will return more meaningful errors. For example, the above
mentioned query will issue the following error message:
```Cannot resolve '`t1.c2`' given input columns: [c1, c2]; line 5 pos 45 ```
The change seems to be due to SPARK-18863 which now calls
```checkAnalysis``` for a subquery tree.
I've tested all the test cases introduced by the current PR, and they all
result in similar error messages.
Therefore, I will close this PR as resolved by SPARK-18863.
---
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
