Github user dilipbiswal commented on the issue:
https://github.com/apache/spark/pull/13483
@viirya You know, as I said above, both ways are not perfect. My inputs are
just based on my previous design experiences. All the design decisions I made
are based on usage scenarios.
This PR is to refine the behavior of `spark.sql.retainGroupColumns`. I
think that might be why @yhuai opened this JIRA.
The problem you mentioned above is another issue. I think we should not
deduplicating the columns, if users really want to do something absurd. : )
---
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]
