Github user bdrillard commented on the issue:
https://github.com/apache/spark/pull/16648
@kiszk Sure, I'm glad to help make this change easier to review. I'll first
make a PR that focuses on code splitting into nested classes. There should be a
test case with a number of columns that is high enough to induce at least one
instance of generating a nested class, but still low enough to not trigger
failure based on the amount of global mutable state. If that PR is reviewed and
is considered acceptable, we can open a second to address global mutable state.
---
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
