Github user nsyca commented on the issue:

    https://github.com/apache/spark/pull/16572
  
    Note the way the plans inside subqueries are not treated as part of the 
tree traversal is a common problem. Besides this problem, another was reported 
in SPARK-19093. Also the way Spark needs to implement a nested call to the 
Optimizer via the rule `OptimizedSubqueries` to work on those plans is another 
instance.
    
    One possible solution is to overwrite the tree traversal (`transformUp`, 
`transformDown`) of class `LogicalPlan` to include those subqueries' plans.


---
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]

Reply via email to