Skip to content

[FR] Add MlflowException on the top level #6620

@dbczumar

Description

@dbczumar

Willingness to contribute

No. I cannot contribute this feature at this time.

Proposal Summary

Make mlflow.exceptions.MlflowException importable as mlflow.MlflowException.

Motivation

What is the use case for this feature?

Make it easier for users to catch MLflow errors.

Why is this use case valuable to support for MLflow users in general?

^

Why is this use case valuable to support for your project(s) or organization?

^

Why is it currently difficult to achieve this use case?

The mlflow.exceptions module is not documented, so it's difficult for users to find out how to import and catch MlflowException.

Details

No response

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/pipelines: Pipelines, Pipeline APIs, Pipeline configs, Pipeline Templates
  • area/projects: MLproject format, project running backends
  • area/scoring: MLflow Model server, model deployment tools, Spark UDFs
  • 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/trackingTracking service, tracking client APIs, autologgingenhancementNew feature or requestgood first issueGood for newcomershas-closing-prThis issue has a closing PRhelp wantedWe would like help from the community to add this support

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions