Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable running MOJO spark pipeline without H2O init #4935

Closed
exalate-issue-sync bot opened this issue May 22, 2023 · 3 comments
Closed

Enable running MOJO spark pipeline without H2O init #4935

exalate-issue-sync bot opened this issue May 22, 2023 · 3 comments
Assignees

Comments

@exalate-issue-sync
Copy link

Usecase: train a pipeline containing an h2o stage, store it to file. Then read it from a file in another script and use it for scoring without explicitly initialising H2O (like with similar calls: H2OConf(spark))

Without that an exception would be thrown:
java.lang.ClassNotFoundException: org.apache.spark.ml.h2o.models.H2OMOJOModel

@exalate-issue-sync
Copy link
Author

Jakub Hava commented: After analyzing this, loading the classes can't be handled automatically. Therefore we can document this behavior and say that user needs to initialize the PySparkling in this case using the Initializer.load_sparkling_jar call

CC: [~accountid:5a73cf5fdca0242a1ca84b4b]

@DinukaH2O
Copy link

JIRA Issue Migration Info

Jira Issue: SW-817
Assignee: Jakub Hava
Reporter: Stefan Pacinda
State: Resolved
Fix Version: 2.1.28
Attachments: N/A
Development PRs: Available

Linked PRs from JIRA

#696
#697

@hasithjp
Copy link
Member

JIRA Issue Migration Info Cont'd

Jira Issue Created Date: 2018-04-24T03:33:59.365-0700

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants