Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/19447
Thank you for your clarification. I understand that you originally
addressed `JVM limit of 0xFFFF` caused by a lot of small methods.
For 2, my idea is that it would be good to monitor the number of method
entries and to split the class if it is large (e.g. 16384). Does it work for
your case?
`if (currClassSize > 1600000 || (the number of method entries [= # of new
function names] > 16384))`
For 3, you already have a solution (hopefully without introducing new
config).
Finally, we could control # of entries for methods in problems 2 and 3
without new config. What do you think?
When we submit a PR, it is necessary to have test case. We hope that you
can create it. If it is hard to write a program to cause the issue, you can
directly call internal APIs (e.g. `CodeGeneratorSuite`).
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
