Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10846#issuecomment-173291293
/cc @sryza, since I know we've talked about Hadoop `Configuration`-related
performance problems in the past. AFAIK this caching code dates back to the era
where cloning or creating `Configuration`s was so expensive as to be a
performance bottleneck. Provided that issue has been fixed / isn't relevant for
the Hadoop versions that we support in Spark 2.0.0+, could we safely omit this
caching? If this has to go into 1.6.1 or earlier, however, then we might want
to keep the caching and go with a flagging approach.
---
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]
