Github user liancheng commented on the issue:
https://github.com/apache/spark/pull/15082
My understanding of the main concern of closing this PR is that:
1. Although this issue can be potentially dangerous, the current code work
fine without fixing this issue.
1. We still can't remove the safe projection in `SortAggregateExec` after
fixing this issue (as @cloud-fan explained above), thus data may be copied
twice and leads to performance regression.
---
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
