-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR] log_table
support for csv (and not only json)
#11829
Comments
This feature makes sense ! :) |
The function in its current form seems to do much more than one would expect and has some inconsistencies:
|
I ran into another issue with |
@marcosjt7 thanks for pointing this out. I think the whole focus of |
@mlflow/mlflow-team Please assign a maintainer and start triaging this issue. |
Willingness to contribute
Yes. I can contribute this feature independently.
Proposal Summary
The experimental
log_table
feature is great! However, it supports onlyjson
. I think supporting alsocsv
would be a benefit for the user and easy to implement.Motivation
Log data as csv (instead of only json)
mlflow.log_text(df.to_csv(), artifact_file="example.csv")
would to the job. However, it is not intuitive as there is a log_table functionDetails
artifact_file
string: If csv=csv, else json (likewise its done in log_dict for json/yaml)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 integrationsThe text was updated successfully, but these errors were encountered: