You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Ilya Kasnacheev (Jira)" <ji...@apache.org> on 2019/09/20 09:32:00 UTC
[jira] [Created] (IGNITE-12204) In binary distribution, essential
dependencies for ignite-spark missing
Ilya Kasnacheev created IGNITE-12204:
----------------------------------------
Summary: In binary distribution, essential dependencies for ignite-spark missing
Key: IGNITE-12204
URL: https://issues.apache.org/jira/browse/IGNITE-12204
Project: Ignite
Issue Type: Improvement
Components: spark
Affects Versions: 2.7.6
Reporter: Ilya Kasnacheev
It seems that we only put direct dependencies of other JARs in our binary distribution, and not transient ones.
For example, libs/optional/ignite-spark lacks the essential commons-lang3 jar, which will lead to the following error immediately:
{code}
Exception in thread "main" java.lang.NoClassDefFoundError: org.apache.commons.lang3.SystemUtils
at org.apache.spark.util.Utils$.<init>(Utils.scala:1915)
at org.apache.spark.util.Utils$.<clinit>(Utils.scala)
at org.apache.spark.SparkConf.loadFromSystemProperties(SparkConf.scala:75)
{code}
It's almost impossible to fix without resorting to Maven source build.
I understand that adding Spark module to Ignite server is something not widely used, but if we ship this module at all, we should make sure that it is usable in some form.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)