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.

Sign up for GitHub

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

Jump to bottom

h2o.upload_mojo should also work for POJO #7104

Closed
exalate-issue-sync bot opened this issue May 11, 2023 · 2 comments
Closed

h2o.upload_mojo should also work for POJO #7104

exalate-issue-sync bot opened this issue May 11, 2023 · 2 comments
Labels
fixVersion/3.38.0.1

Comments

@exalate-issue-sync
Copy link

h2o.import_mojo can be used to import a POJO (java class), however, using h2o.upload_mojo fails because we expect we will be able to derive the class name from the file name (Vec). In case of upload_mojo we have a randomized Vec name.
@h2o-ops-ro
Copy link
Collaborator

JIRA Issue Details

Jira Issue: PUBDEV-8561
Assignee: Michal Kurka
Reporter: Michal Kurka
State: Resolved
Fix Version: 3.38.0.1
Attachments: N/A
Development PRs: Available

@h2o-ops-ro
Copy link
Collaborator

Linked PRs from JIRA

#6054
https://github.com/h2oai/h2oai-serving/pull/1079

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
fixVersion/3.38.0.1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@h2o-ops-ro