Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15915
You could also cap it at 16MB here. Or 128MB or whatever. That is unrelated
to introducing a new config.
It seems funny that setting to allow Int.MaxValue but map anything else to
something orders of magnitude smaller. Why not just cap at Int.MaxValue like in
the original proposal? that's also less behavior change.
---
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]
