Skip to content
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] Display the complete dataset profile in the data details view #12010

Open
1 of 22 tasks
gboeer opened this issue May 15, 2024 · 1 comment
Open
1 of 22 tasks

[FR] Display the complete dataset profile in the data details view #12010

gboeer opened this issue May 15, 2024 · 1 comment
Labels
area/uiux Front-end, user experience, plotting, JavaScript, JavaScript dev server enhancement New feature or request

Comments

@gboeer
Copy link

gboeer commented May 15, 2024

Willingness to contribute

Yes. I would be willing to contribute this feature with guidance from the MLflow community.

Proposal Summary

When logging a dataset, using mlflow.log_input() , the dataset information contained in the returned dataset profile is truncated in the web view.

image

While it is possible to look at the full profile when hovering over it, it is not possible to select/copy any text from it.
I think it would be nicer to display the full profile in a nicely formatted manner, e.g. using the json format as in the artifacts view.

Motivation

What is the use case for this feature?

Easily look at the full dataset specifications and be able to copy information from it.

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/deployments: MLflow Deployments client APIs, server, and third-party Deployments integrations
  • 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/recipes: Recipes, Recipe APIs, Recipe configs, Recipe 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
@gboeer gboeer added the enhancement New feature or request label May 15, 2024
@github-actions github-actions bot added the area/uiux Front-end, user experience, plotting, JavaScript, JavaScript dev server label May 15, 2024
@harupy harupy added the help wanted We would like help from the community to add this support label May 15, 2024
@gboeer gboeer changed the title [FR] Display the complete dataset profile in the date details view [FR] Display the complete dataset profile in the data details view May 15, 2024
@harupy harupy removed the help wanted We would like help from the community to add this support label May 16, 2024
Copy link

@mlflow/mlflow-team Please assign a maintainer and start triaging this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/uiux Front-end, user experience, plotting, JavaScript, JavaScript dev server enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants