Github user ooq commented on the issue:
https://github.com/apache/spark/pull/14176
@davies I guess there is still benefit to make it public? If the user knows
that their workload would always run faster with single-level, e.g., many
distinct keys. I thought about `spark.sql.codegen.aggregate.map.fast.enable` or
`spark.sql.codegen.aggregate.map.codegen.enable`, but none of them captures the
fact that the biggest distinction is the two level design.
---
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
