[
https://issues.apache.org/jira/browse/SPARK-34037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17260270#comment-17260270
]
Kent Yao commented on SPARK-34037:
----------------------------------
Oh, I mean that when users query for 4 attributes, for example, we may return 5
(or maybe more) instead, with one attribute named `aggOrder`.
This attribute is added by spark's analyzer for push *sortorder * into
aggeration for internal logic only and it should not affect the final output
> aggOrder should not be output as a auxiliary internal attribute
> ---------------------------------------------------------------
>
> Key: SPARK-34037
> URL: https://issues.apache.org/jira/browse/SPARK-34037
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 3.1.0
> Reporter: Kent Yao
> Priority: Blocker
>
> TakeOrderedAndProject
> [ca_state,cd_gender,cd_marital_status,{color:red}aggOrder{color},cd_dep_employed_count,cd_dep_college_count,cnt1,min(cd_dep_count),max(cd_dep_count),avg(cd_dep_count),cnt2,min(cd_dep_employed_count),max(cd_dep_employed_count),avg(cd_dep_employed_count),cnt3,min(cd_dep_college_count),max(cd_dep_college_count),avg(cd_dep_college_count)]
> The TPCDS plan results for q35 q85 are messed up with this attribute
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
