Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/14719#discussion_r78126865
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -683,8 +710,14 @@ class Analyzer(
try {
expr transformUp {
case GetColumnByOrdinal(ordinal, _) => plan.output(ordinal)
- case u @ UnresolvedAttribute(nameParts) =>
- withPosition(u) { plan.resolve(nameParts, resolver).getOrElse(u)
}
+ case u @ UnresolvedAttribute(nameParts, targetPlanIdOpt) =>
+ withPosition(u) {
+ targetPlanIdOpt match {
+ case Some(targetPlanId) =>
+ resolveExpressionFromSpecificLogicalPlan(nameParts, plan,
targetPlanId)
--- End diff --
Thank you for taking a look.
If resolved attributes are not in output of a child-logical-plan even
though those are in output of a sub-tree, `CheckAnalysys` verifies and raise
`AnalysysException` as well as before applying this patch
---
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
