Github user davies commented on a diff in the pull request:

    https://github.com/apache/spark/pull/10678#discussion_r51356255
  
    --- Diff: 
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
 ---
    @@ -521,38 +522,99 @@ class Analyzer(
        */
       object ResolveSortReferences extends Rule[LogicalPlan] {
         def apply(plan: LogicalPlan): LogicalPlan = plan resolveOperators {
    -      case s @ Sort(ordering, global, p @ Project(projectList, child))
    -          if !s.resolved && p.resolved =>
    -        val (newOrdering, missing) = resolveAndFindMissing(ordering, p, 
child)
    +      case s @ Sort(_, _, a: Aggregate) if a.resolved =>
    --- End diff --
    
    So this seems that the rule in `ResolveAggregateFunctions` does not really 
resolve the missing attributes, we could keep that rule unchanged in this PR.
    
    If it's not trivial to fix this, we could create another JIRA for that.


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

Reply via email to