[
https://issues.apache.org/jira/browse/ARROW-17656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644921#comment-17644921
]
Apache Arrow JIRA Bot commented on ARROW-17656:
-----------------------------------------------
This issue was last updated over 90 days ago, which may be an indication it is
no longer being actively worked. To better reflect the current state, the issue
is being unassigned per [project
policy|https://arrow.apache.org/docs/dev/developers/bug_reports.html#issue-assignment].
Please feel free to re-take assignment of the issue if it is being actively
worked, or if you plan to start that work soon.
> [C++] Change Acero Aggregate output order
> -----------------------------------------
>
> Key: ARROW-17656
> URL: https://issues.apache.org/jira/browse/ARROW-17656
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Reporter: Vibhatha Lakmal Abeykoon
> Assignee: Vibhatha Lakmal Abeykoon
> Priority: Major
> Labels: acero, query-engine, substrait
>
> At the moment Acero Aggregates output contains aggregate fields followed by
> key fields. In Substrait this is the other way around. Also, it is not
> necessary to keep this static and use a project node to fulfill the
> requirement. It is rather important to modify this order and update the
> corresponding test cases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
