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

[SW-1481] Deprecate H2OMOJOModel, H2OMOJOPipelineModel and H2OMOJOSettings in the org.apache.spark package #1405

Closed
wants to merge 0 commits into from

Conversation

jakubhava
Copy link
Contributor

@jakubhava jakubhava commented Aug 1, 2019

This build on top of the scoring package. I would like to expose the scoring package with the new namespaces, old one being deprecated

Builds on top of #1403

@jakubhava jakubhava requested a review from mn-mikke August 1, 2019 12:52
Copy link
Collaborator

@mn-mikke mn-mikke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! I really like the direction of these changes.

Just a quick question... Is this change backward-compatible? In other words, what if a algorithm is trained and stored to a H2OMOJOModel in the old namespace and deserialized into one in ai.h2o.sparkling? Does it going to work with MOJOs produced by H2O-3?

model.setMojoData(mojoData)
model
}
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing a new line

@jakubhava
Copy link
Contributor Author

Thanks. I finally wanted to move forward with this -> I hope this trick should preserve the backward compatibility https://github.com/h2oai/sparkling-water/pull/1405/files#diff-ab18325d3077d27883c1467d7cb30c19R51

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

Successfully merging this pull request may close these issues.

None yet

2 participants