[BUG] Attribute lifecycle_stage of an experiment and its runs is not set to LifecycleStage.DELETED when the experiment is deleted in FileStore backend

[mariusschlegel]

Issues Policy acknowledgement

• I have read and agree to submit bug reports in accordance with the issues policy

Willingness to contribute

Yes. I can contribute a fix for this bug independently.

MLflow version

• Client: 2.2.2
• Tracking server: 2.2.2

System information

• OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Fedora Linux 37
• Python version: 3.10.10

Describe the problem

When using the FileStore backend and deleting/restoring an experiment, the lifecycle_stage attribute of the experiment and its runs is not persistently set/updated to LifecycleStage.DELETED/LifecycleStage.ACTIVE (see https://github.com/mlflow/mlflow/blob/master/mlflow/store/tracking/file_store.py#L418). This is contrary to the implementation of the SQLAlchemyStore backend (see https://github.com/mlflow/mlflow/blob/master/mlflow/store/tracking/sqlalchemy_store.py#L395).

Tracking information

REPLACE_ME

Code to reproduce issue

REPLACE_ME

Stack trace

REPLACE_ME

Other info / logs

REPLACE_ME

What component(s) does this bug affect?

• area/artifacts: Artifact stores and artifact logging
• area/build: Build and test infrastructure for MLflow
• area/docs: MLflow documentation pages
• area/examples: Example code
• area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
• area/models: MLmodel format, model serialization/deserialization, flavors
• area/projects: MLproject format, project running backends
• area/scoring: MLflow Model server, model deployment tools, Spark UDFs
• area/recipes: Recipes, Recipe APIs, Recipe configs, Recipe Templates
• area/server-infra: MLflow Tracking server backend
• area/tracking: Tracking Service, tracking client APIs, autologging

What interface(s) does this bug affect?

• area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
• area/docker: Docker use across MLflow's components, such as MLflow Projects and MLflow Models
• area/sqlalchemy: Use of SQLAlchemy in the Tracking Service or Model Registry
• area/windows: Windows support

What language(s) does this bug affect?

• language/r: R APIs and clients
• language/java: Java APIs and clients
• language/new: Proposals for new client languages

What integration(s) does this bug affect?

• integrations/azure: Azure and Azure ML integrations
• integrations/sagemaker: SageMaker integrations
• integrations/databricks: Databricks integrations

[WeichenXu123]

Thank you ! I reviewed your PR.

[mariusschlegel]

Thanks a lot for reviewing. I have revised the PR according to your comments.

[mlflow-automation]

@BenWilson2 @dbczumar @harupy @WeichenXu123 Please assign a maintainer and start triaging this issue.