Add a Python API to load model input examples#5212
Conversation
Signed-off-by: Matthieu Maitre <mmaitre@microsoft.com>
Signed-off-by: Matthieu Maitre <mmaitre@microsoft.com>
|
Thanks for filing the PR @maitre-matt - I'll add this to my review queue. It's a great idea! |
ankit-db
left a comment
There was a problem hiding this comment.
Just a few brief comments
ankit-db
left a comment
There was a problem hiding this comment.
Thank you so much for the contribution! This one's going to be super useful for people 😄
|
@maitre-matt I think I may have messed up the signoff by accepting a suggestion which creates a commit. Will fix it tmm and merge! |
Thanks for the quick turnaround on that PR! Much appreciated. We are building ML tools and MLflow's standardization is making things a lot simpler. |
| from mlflow.models.utils import ( | ||
| _read_example, | ||
| ) |
There was a problem hiding this comment.
Not a big issue, but we can remove the comma.
| from mlflow.models.utils import ( | |
| _read_example, | |
| ) | |
| from mlflow.models.utils import _read_example |
…on > 3.3.1 (#5206) The parameter evals_result is removed in the master of lightgbm: lightgbm-org/LightGBM#4882. The parameter early_stopping_rounds is removed in the master of lightgbm: lightgbm-org/LightGBM#4908. We should also remove this param in our test. This PR also fixed the sagemaker test failure. Signed-off-by: Liang Zhang <liang.zhang@databricks.com>
Signed-off-by: Matthieu Maitre <mmaitre@microsoft.com>
What changes are proposed in this pull request?
This change adds a new Python API
Model.load_input_example(), which wraps the internal-only method_read_example(). It allows tools which consume MLflow models to correctly load model input examples.Associated Feature Request: #5211
How is this patch tested?
Added unit tests.
Does this PR change the documentation?
ci/circleci: build_doccheck. If it's successful, proceed to thenext step, otherwise fix it.
Detailson the right to open the job page of CircleCI.Artifactstab.docs/build/html/index.html.Release Notes
Is this a user-facing change?
Add a Python API to load model input examples
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