Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/3525#issuecomment-73388468
FWIW I think the logic behind the existing parameters is: 7% should be
enough for anyone. And if it isn't, they know it, and have a clear idea of just
how much they want the overhead to be. Or: if 7% is consistently not enough, it
should be higher, like 10%. I'd leave the existing param unless it's obviously
problematic.
But that's separate from the question here, of whether lots of these
strings could be specified in mega or gigabytes. Is that still something that
can move forward? the refactoring of all that seems helpful in any event.
---
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]
