-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Render code to load model when pyfunc flavor is unavailable #5006
Conversation
...s/src/experiment-tracking/components/artifact-view-components/ShowArtifactLoggedModelView.js
Outdated
Show resolved
Hide resolved
loadModelCodeText(modelPath, flavor) { | ||
return ( | ||
`import mlflow\n` + | ||
`logged_model = '${modelPath}'\n\n` + | ||
`# Load model.\n` + | ||
`loaded_model = mlflow.${flavor}.load_model(logged_model)\n` | ||
); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@harupy This is perfect for everything except MLeap. MLeap models can't be reloaded in Python. Perhaps we can add a Java example for MLeap or show nothing for now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it. If so, I'd prefer to show nothing for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good!
See <a href={CustomPyfuncModelsDocUrl}>Creating custom Pyfunc models</a> for how to log | ||
this model as a PyFuncModel. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See <a href={CustomPyfuncModelsDocUrl}>Creating custom Pyfunc models</a> for how to log | |
this model as a PyFuncModel. | |
See <a href={CustomPyfuncModelsDocUrl}>creating custom Pyfunc models</a> to learn how | |
to customize this model and deploy it for batch or real-time scoring using the ``pyfunc`` model flavor. |
It would be nice to link to the pyfunc
docs too: https://www.mlflow.org/docs/latest/python_api/mlflow.pyfunc.html#module-mlflow.pyfunc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, I'll add the pyfunc link!
165cd0a
to
1c42092
Compare
Signed-off-by: harupy <hkawamura0130@gmail.com>
Signed-off-by: harupy <hkawamura0130@gmail.com>
…iew-components/ShowArtifactLoggedModelView.js Co-authored-by: dbczumar <39497902+dbczumar@users.noreply.github.com> Signed-off-by: harupy <hkawamura0130@gmail.com>
Signed-off-by: harupy <hkawamura0130@gmail.com>
Signed-off-by: harupy <hkawamura0130@gmail.com>
653ba6a
to
81e86f0
Compare
@dbczumar Let me add a few screenshots to show how it looks like now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks @harupy !
Thanks for the review! |
Signed-off-by: harupy hkawamura0130@gmail.com
What changes are proposed in this pull request?
Currently, the model artifact viewer renders code to load the logged model as a pyfunc model and make predictions even when the logged model doesn't contain the pyfunc flavor. This PR fixes the issue by rendering code to load the logged model using the original flavor module.
Before
no-pyfunc-model.mov
After
mlflow.sklearn
.How is this patch tested?
Unit tests
Release Notes
Is this a user-facing change?
(Details in 1-2 sentences. You can just refer to another PR with a description if this PR is part of a larger change.)
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/artifacts
: Artifact stores and artifact loggingarea/build
: Build and test infrastructure for MLflowarea/docs
: MLflow documentation pagesarea/examples
: Example codearea/model-registry
: Model Registry service, APIs, and the fluent client calls for Model Registryarea/models
: MLmodel format, model serialization/deserialization, flavorsarea/projects
: MLproject format, project running backendsarea/scoring
: MLflow Model server, model deployment tools, Spark UDFsarea/server-infra
: MLflow Tracking server backendarea/tracking
: Tracking Service, tracking client APIs, autologgingInterface
area/uiux
: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/docker
: Docker use across MLflow's components, such as MLflow Projects and MLflow Modelsarea/sqlalchemy
: Use of SQLAlchemy in the Tracking Service or Model Registryarea/windows
: Windows supportLanguage
language/r
: R APIs and clientslanguage/java
: Java APIs and clientslanguage/new
: Proposals for new client languagesIntegrations
integrations/azure
: Azure and Azure ML integrationsintegrations/sagemaker
: SageMaker integrationsintegrations/databricks
: Databricks integrationsHow should the PR be classified in the release notes? Choose one:
rn/breaking-change
- The PR will be mentioned in the "Breaking Changes" sectionrn/none
- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/feature
- A new user-facing feature worth mentioning in the release notesrn/bug-fix
- A user-facing bug fix worth mentioning in the release notesrn/documentation
- A user-facing documentation change worth mentioning in the release notes