Lightning-AI / Lightning-AI/pytorch-lightning

MLflow model format required for the Register Model

Open
#21,437 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature logger: mlflow
Dominant language
Python
Stars
31.4k
Forks
3.8k
Avg merge
6d 7h
Merged PRs (30d)
6

Description

### Description & Motivation

I have problems when i want to register a model while using `pytorch-lightning`. It does not offer the option to `mlflow.log_model`. I would really appreciate if we can add this feature to `MLflowLogger` so it can improve experiments tracking and model versioning.

### Pitch

I want to know if it is possible to add this feature in this repo. If possible, then I would like to add the feature based on your guidelines.

### Alternatives

Refactor MLFlowLogger to bring mlflow.log_model into the picture.

### Additional context

When using pure `mlflow.log_model`, it enables "Register Model" in the experiment run of mlflow UI.

Image

Since `MLFlowLogger` only support `log_artifact`, "Register Model" is never triggered.

cc @lantiga

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the MLFlowLogger entry point and trace its existing log_artifact support alongside the mlflow.log_model API. Clarify which model types and logger interface are in scope, then define completion as model logging that enables Register Model in the MLflow UI with appropriate coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, pytorch
Domain
machine-learning
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.