Fix RSparkling in case the jars are being fetched from maven

Description

None

Activity

Show:
Jakub Hava
February 27, 2019, 2:28 PM
Edited

Actually this is a more complex issue in Spark -> https://issues.apache.org/jira/browse/SPARK-24287

I'm trying to see of we are able to resolve this for this particular case - RSparkling, however usage of maven artifact ai.h2o:sparkling-water-package_2.11 will remain broken until this is fixed

Jakub Hava
February 27, 2019, 4:11 PM

Found the core issue. The issue is that instead of jar, javadoc is downloaded.

It is caused transitively by sparkling-water-core_2.11 -> h2o-algos -> com.github.fommil.netlib-core where you actually see http://central.maven.org/maven2/com/github/fommil/netlib/core/1.1.2/core-1.1.2.pom the dependency on javadoc enforced via the classifier.

Trying to see if I can exclude this on the sparkling_water_package package level

Jakub Hava
February 28, 2019, 8:03 AM

This will be fixed on H2O side by

Jakub Hava
February 28, 2019, 8:04 AM

Will keep this jira open just as a wrapper on Sparkling Water side even though no code change is required in Sparkling Water

Assignee

Jakub Hava

Reporter

Jakub Hava

Labels

None

CustomerVisible

No

testcase 1

None

testcase 2

None

testcase 3

None

h2ostream link

None

Affected Spark version

None

AffectedContact

None

AffectedCustomers

None

AffectedPilots

None

AffectedOpenSource

None

Support Assessment

None

Customer Request Type

None

Support ticket URL

None

End date

None

Baseline start date

None

Baseline end date

None

Task progress

None

Task mode

None

ReleaseNotesHidden

None

Fix versions

Priority

Major
Configure