Introduce a warning during the serialization of MOJO model

[exalate-issue-sync]

For details, refer to support ticket: https://support.h2o.ai/a/tickets/100534

[exalate-issue-sync]

Marek Novotny commented: Alternative solution is to throw exception if H2OMOJOModel is being serialized:

H2OMOJOModel is currently Java serializable and serves as a closure for Spark UDFs that are responsible for model scoring. However, H2OMOJOModel which has been serialized, moved to different Spark application and deserialized can't be used for scoring. Such a H2OMOJOModel will get disconnected from H2O-3 mojo artifacts that were located on Spark executors of the original cluster.

So the solution would be to create a class that will play role of a closure for Spark UDFs and make H2OMOJOModel unserializable.

[exalate-issue-sync]

Arun Aryasomayajula commented: Any updates on this Jira Marek?

[exalate-issue-sync]

Marek Novotny commented: [~accountid:5fa438f822f3990076aa232d] I’ve created the PR [https://github.com//pull/2742|https://github.com//pull/2742|smart-link] to cover that.

[DinukaH2O]

JIRA Issue Migration Info

Jira Issue: SW-2655
Assignee: Marek Novotny
Reporter: Neema Mashayekhi
State: Resolved
Fix Version: 3.36.0.4-1
Attachments: N/A
Development PRs: Available

Linked PRs from JIRA

#2742

[hasithjp]

JIRA Issue Migration Info Cont'd

Jira Issue Created Date: 2021-12-01T14:55:33.561-0800