Open thatcort opened 3 weeks ago
@thatcort Thank you for reporting the issue! There is an ongoing effort for supporting Pyarrow 16: https://github.com/mlflow/mlflow/pull/11905.
@mlflow/mlflow-team Please assign a maintainer and start triaging this issue.
Willingness to contribute
No. I cannot contribute this feature at this time.
Proposal Summary
Please support pyarrow version 16. MLFlow is currently pinned to <16.
Motivation
I am trying to install the latest version of another library (nvidia cudf-cu12) that requires pyarrow v16, but mlflow's dependency on <16 is preventing this.
MLFlow should not limit what other libraries can be installed alongside.
I require both libraries to work together.
The conflicting dependency requirements prevent installing cudf-cu12.
Details
No response
What component(s) does this bug affect?
area/artifacts
: Artifact stores and artifact loggingarea/build
: Build and test infrastructure for MLflowarea/deployments
: MLflow Deployments client APIs, server, and third-party Deployments integrationsarea/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, autologgingWhat interface(s) does this bug affect?
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 supportWhat language(s) does this bug affect?
language/r
: R APIs and clientslanguage/java
: Java APIs and clientslanguage/new
: Proposals for new client languagesWhat integration(s) does this bug affect?
integrations/azure
: Azure and Azure ML integrationsintegrations/sagemaker
: SageMaker integrationsintegrations/databricks
: Databricks integrations