[Support inference params-2]Add params for PyFunc predict#8973
Merged
Conversation
Signed-off-by: Serena Ruan <[email protected]>
33 tasks
Signed-off-by: Serena Ruan <[email protected]>
Contributor
|
Documentation preview for 0096fee will be available here when this CircleCI job completes successfully. More info
|
serena-ruan
marked this pull request as draft
July 7, 2023 00:15
Signed-off-by: Serena Ruan <[email protected]>
Signed-off-by: Serena Ruan <[email protected]>
serena-ruan
marked this pull request as ready for review
July 7, 2023 10:34
serena-ruan
commented
Jul 7, 2023
Collaborator
Author
|
Seems like converting a draft PR to a normal PR doesn't trigger the workflows automatically. cc @harupy |
BenWilson2
reviewed
Jul 7, 2023
BenWilson2
reviewed
Jul 7, 2023
Signed-off-by: Serena Ruan <[email protected]>
Signed-off-by: Serena Ruan <[email protected]>
Signed-off-by: Serena Ruan <[email protected]>
BenWilson2
approved these changes
Jul 7, 2023
BenWilson2
left a comment
Contributor
There was a problem hiding this comment.
LGTM! Thanks @serena-ruan :)
serena-ruan
enabled auto-merge (squash)
July 7, 2023 15:07
serena-ruan
added a commit
to serena-ruan/mlflow
that referenced
this pull request
Jul 13, 2023
…lflow#8973)" This reverts commit 9ebab71. Signed-off-by: Serena Ruan <[email protected]>
serena-ruan
added a commit
that referenced
this pull request
Jul 13, 2023
* add predict params for pyfunc and python model Signed-off-by: Serena Ruan <[email protected]> * fix Signed-off-by: Serena Ruan <[email protected]> * add more tests and fix a small bug Signed-off-by: Serena Ruan <[email protected]> * address comments Signed-off-by: Serena Ruan <[email protected]> * add warnings for params missing case Signed-off-by: Serena Ruan <[email protected]> * reformat Signed-off-by: Serena Ruan <[email protected]> --------- Signed-off-by: Serena Ruan <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related Issues/PRs
Depends on: #8972
What changes are proposed in this pull request?
Support
paramsfield for PyFunc models and PythonModel.How is this patch tested?
Does this PR change the documentation?
Release Notes
Is this a user-facing change?
Support passing additional parameters as
paramsdictionary to modelpredictmethodWhat 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/recipes: Recipes, Recipe APIs, Recipe configs, Recipe Templatesarea/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