Add support to log customized tags to runs created by autolog #9114
Conversation
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
…9064 Signed-off-by: Li Jiang <[email protected]>
harupy
added
the
only-latest
Signed-off-by: Li Jiang <[email protected]>
|
Documentation preview for 6ed7c2e will be available here when this CircleCI job completes successfully. More info
|
github-actions
bot
added
area/tracking
…to fix test failures Signed-off-by: Li Jiang <[email protected]>
Signed-off-by: Li Jiang <[email protected]>
Signed-off-by: Li Jiang <[email protected]>
Signed-off-by: Li Jiang <[email protected]>
Signed-off-by: Li Jiang <[email protected]>
|
Hi @serena-ruan , could you help review the PR? Thanks. |
serena-ruan
reviewed
Jul 20, 2023
There was a problem hiding this comment.
@thinkall Overall looks great! Left a few comments :)
I think it could be more clear that we split tags test.
Signed-off-by: Li Jiang <[email protected]>
Signed-off-by: Li Jiang <[email protected]>
Thank you Serana, I've split all the tests for extra_tags. Warning messages and built-in tags checking have been included as well. |
Signed-off-by: Li Jiang <[email protected]>
serena-ruan
reviewed
Jul 20, 2023
Signed-off-by: Li Jiang <[email protected]>
|
LGTM! @harupy You wanna take a look? 😃 |
|
Thank you @serena-ruan, and hi, @harupy ! Just a gentle reminder to take a look :-) |
BenWilson2
pushed a commit
to BenWilson2/mlflow
that referenced
this pull request
Jul 31, 2023
…#9114) Signed-off-by: Li Jiang <[email protected]>
santiagxf
pushed a commit
to santiagxf/mlflow
that referenced
this pull request
Aug 7, 2023
…#9114) Signed-off-by: Li Jiang <[email protected]> Signed-off-by: santiagxf <[email protected]>
clarkh-ncino
pushed a commit
to ncino/mlflow
that referenced
this pull request
Aug 23, 2023
…#9114) Signed-off-by: Li Jiang <[email protected]> Signed-off-by: Clark Hollar <[email protected]>
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
Resolve #9064
What changes are proposed in this pull request?
Added a parameter
extra_tagsto allautologfunctions, and passed it tosafe_patchfunction inmlflow.utils.autologging_utils.safety.py.With this
extra_tags, users can log customized tags to runs created by autolog.How is this patch tested?
Does this PR change the documentation?
Release Notes
Is this a user-facing change?
Users can set the parameter
extra_tagsinmlflow.autolog(extra_tags={"test_tag": "autolog"})and all the other specific autolog functions such asmlflow.sklearn.autolog(extra_tags={"test_tag": "sklearn_autolog"})to log theextra_tagsinto runs created by autolog.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/gateway: AI Gateway service, Gateway client APIs, third-party Gateway integrationsarea/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