Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/1929#issuecomment-53312925
@gkossakowski, thanks for the detailed reply. From my point of view, what
we want when new JARs are added is for *earlier* JARs to take precedence. This
is what makes the most sense. If you already instantiated an object from the
previous version of the class and stored it in a variable, it's not possible
for it to suddenly change class. So instead the effect should be the same as
tacking on another JAR at the end of your classpath -- only classes that are
not found in earlier JARs come from there. Would these semantics be possible to
implement for 2.11?
---
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]
