Github user liyezhang556520 commented on the pull request:
https://github.com/apache/spark/pull/12083#issuecomment-206096350
@vanzin , @zsxwing , I have changed the buffer limit to 256K. I do agree
that it's better we handle this issue by manually copying data to directBuffer,
so no duplicate copy will be made. But that will introduce code complexity
somehow. How about we merge this PR first, and in further, I can create a new
JIRA and submit a new PR to use directByteBufferPool to avoid duplicate memory
copy? Because once we use directBuffer, the code is supposed to be take care of
and should be well reviewed.
---
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]
