Support shift+select for Traces#20125
Conversation
🛠 DevTools 🛠
Install mlflow from this PRFor Databricks, use the following command: |
|
Documentation preview for 025f270 is available at: More info
|
Signed-off-by: B-Step62 <yuki.watanabe@databricks.com>
29878fb to
2ee24db
Compare
mlflow/server/js/src/shared/web-shared/genai-traces-table/GenAiTracesTableBody.tsx
Outdated
Show resolved
Hide resolved
| if (!enableRowSelection) { | ||
| lastSelectedRowIdRef.current = null; | ||
| return; | ||
| } |
There was a problem hiding this comment.
hmm when is this case necessary? if row selection is disabled the user should have no way of selecting a row in the first place right
There was a problem hiding this comment.
aside from this, looking at the code i'm not sure if enableRowSelection is ever false
| if (!rowSelection || Object.keys(rowSelection).length === 0) { | ||
| lastSelectedRowIdRef.current = null; | ||
| } |
There was a problem hiding this comment.
is it possible to handle this in the onclick handler instead when deselecting? we should avoid useEffects where possible to avoid unnecessary rerender cycles
There was a problem hiding this comment.
makes sense, yeah it removes unnecessary rerender
| }, | ||
| ); | ||
|
|
||
| const getRowSelectionChangeHandler = useCallback( |
There was a problem hiding this comment.
do we need this to be a getter? why not just rowSelectionChangeHandler and return the function directly?
There was a problem hiding this comment.
Hmm I quite not remember... this was sth I did when updated universe side a month ago😅 It seems removing it doesn't have an effect so we can simplify this.
| }) => { | ||
| const cells = row.getVisibleCells(); | ||
| const intl = useIntl(); | ||
| const rowSelectHandler = React.useMemo( |
There was a problem hiding this comment.
when https://github.com/mlflow/mlflow/pull/20125/files#r2706732804 is addressed this should be unnecessary, we can pass the prop directly to the select cell
daniellok-db
left a comment
There was a problem hiding this comment.
lgtm when comments addressed!
Signed-off-by: B-Step62 <yuki.watanabe@databricks.com>
Signed-off-by: B-Step62 <yuki.watanabe@databricks.com>
Signed-off-by: B-Step62 <yuki.watanabe@databricks.com>
What changes are proposed in this pull request?
Port PR #1486294 from universe to support Shift+select in the trace table. Manually porting to ship this in 3.9 (the PR has been there for a long forgotten so want to clean up:D)
How is this PR tested?
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
Support Shift+select in the Trace table.
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/tracking: Tracking Service, tracking client APIs, autologgingarea/models: MLmodel format, model serialization/deserialization, flavorsarea/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registryarea/scoring: MLflow Model server, model deployment tools, Spark UDFsarea/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflowsarea/gateway: MLflow AI Gateway client APIs, server, and third-party integrationsarea/prompts: MLflow prompt engineering features, prompt templates, and prompt managementarea/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionalityarea/projects: MLproject format, project running backendsarea/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/build: Build and test infrastructure for MLflowarea/docs: MLflow documentation pagesHow should the PR be classified in the release notes? Choose one:
rn/none- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/breaking-change- The PR will be mentioned in the "Breaking Changes" sectionrn/feature- A new user-facing feature worth mentioning in the release notesrn/bug-fix- A user-facing bug fix worth mentioning in the release notesrn/documentation- A user-facing documentation change worth mentioning in the release notesShould this PR be included in the next patch release?
Yesshould be selected for bug fixes, documentation updates, and other small changes.Noshould be selected for new features and larger changes. If you're unsure about the release classification of this PR, leave this unchecked to let the maintainers decide.What is a minor/patch release?
Bug fixes, doc updates and new features usually go into minor releases.
Bug fixes and doc updates usually go into patch releases.