Github user kiszk commented on the pull request:
https://github.com/apache/spark/pull/11301#issuecomment-191366608
I agree with @rxin that it includes the size of the bytecode. I can
alleviate an increase of bytecode size to create and call a utility routine
instead of generating all in the ```processNext()```.
@davis and @sarutak, the original motivation of this is that it is not easy
to identify the original method of a method that an exception throws. Its name
is always the same as ```processNext()```. Is there any good idea to identify
the original method name?
---
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]
