Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4565#issuecomment-74235582
Rather than add a new flag, why not just disallow overwrite in these cases?
I'd like someone else to review the logic too before forbidding this. That
is, I would not want this to cause an error in a common case, just because a
jar changed, but where the caller does not care about updating the classloader.
---
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]
