mlflow/mlflow

[FR] Reordering of table columns on MLflow Experiment page.

Open

#7,870 opened on 2023年2月21日

GitHub で見る
 (2 comments) (2 reactions) (0 assignees)Python (17,127 stars) (3,904 forks)batch import
area/trackingarea/uiuxenhancementhelp wanted

説明

Willingness to contribute

No. I cannot contribute this feature at this time.

Proposal Summary

We propose to enable users to reorder the columns of the Runs table on the MLflow Experiment page.

  • Every column except "Run name" should be reorderable.
  • Reordering should be supported across different types, e.g. "param", "metric", "param" should be supported.
  • The column ordering should be persisted in the URL.

Motivation

What is the use case for this feature?

When selecting models, users often want to closely inspect values from a few related metrics / parameters. Letting users group them together will help make this easier, reducing eye strain.

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

MLflow users have long asked for this capability. This is the official feature request.

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

^

Why is it currently difficult to achieve this use case?

Columns of the Runs table are not currently reorderable.

Details

The ag-grid component that is used for the MLflow Runs table already supports reordering, it's just disabled right now. All we need to do is:

  1. re-enable ordering setting suppressMovable: false: https://github.com/mlflow/mlflow/blob/75e39dcff8aae5c1859d8c364f3eae8537c9076a/mlflow/server/js/src/experiment-tracking/components/experiment-page/utils/experimentPage.column-utils.ts#L476

  2. persist the column ordering in the MLflow URL when it's changed. reference utilities: https://github.com/mlflow/mlflow/blob/master/mlflow/server/js/src/experiment-tracking/components/experiment-page/utils/persistSearchFacets.ts.

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/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

コントリビューターガイド

技術スタック
javascripttypescriptreact
領域
frontend
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
2
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
fresh
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
JavaScriptReactag gridURL parameter handling
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
80
調査方針
Review the column utility file at https://github.com/mlflow/mlflow/blob/75e39dcff8aae5c1859d8c364f3eae8537c9076a/mlflow/server/js/src/experiment tracking/components/experiment page/utils/experimentPage.column utils.ts#L476 to locate the `suppressMovable` setting and change it to `false`. Then examine the URL persistence utility in `persistSearchFacets.ts` to understand how column state is serialized using `updateSearchFacets` and related functions. Add column ordering to the persisted facets, and ensure it is applied on load by reading from the URL. Test by dragging columns in the UI and verifying that the URL updates and the order persists across page refreshes.