Hi Sean,
"Boy it's a long story"...yeah, you tell me! :) I don't seem to find
anything worth reporting so...let's keep these possible discrepancies
in mind and be back to them when they hit us.
Thanks a lot, Sean. Your patience with dealing with people here and on
JIRA has always made me wish for
Boy it's a long story, but I think the short answer is that it's only
worth manually fixing the mismatches that are clearly going to cause a
problem.
Dependency version mismatch is inevitable, and Maven will always
settle on one version of a particular group/artifact using a
nearest-wins rule (SBT
Hi Sean,
Thanks a lot for help understanding the different jars.
Do you think there's anything that should be reported as an
enhancement/issue/task in JIRA?
Pozdrawiam,
Jacek Laskowski
https://medium.com/@jaceklaskowski/
Mastering Apache Spark 2.0 http://bit.ly/mastering-apache-spark
Follow
No, these are different major versions of these components, each of
which gets used by something in the transitive dependency graph. They
are not redundant because they're not actually presenting roughly the
same component in the same namespace.
However the parquet-hadoop bit looks wrong, in that
Hi,
Just noticed in assembly/target/scala-2.11/jars that similar libraries
have different versions:
-rw-r--r-- 1 jacek staff 1230201 17 wrz 09:51 netty-3.8.0.Final.jar
-rw-r--r-- 1 jacek staff 2305335 17 wrz 09:51 netty-all-4.0.41.Final.jar
and
-rw-r--r-- 1 jacek staff218076 17 wr
