[WIP] feat: update mlflow UI #12334
Draft
[WIP] feat: update mlflow UI #12334
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yoonhyejin
commented
Jan 14, 2025
| <Typography.Title level={3}>Model Details</Typography.Title> | ||
| <InfoItemContainer justifyContent="left"> | ||
| {/* TODO: should use versionProperties? */} | ||
| <InfoItem title="Version"> |
There was a problem hiding this comment.
@RyanHolstien should we use the versionProperties.version for this as well? are we going to deprecate the properties.version?
yoonhyejin
commented
Jan 14, 2025
| """ | ||
| Represents lineage information for ML entities. | ||
| """ | ||
| type MLModelLineageInfo { |
There was a problem hiding this comment.
let me know if this is valid approach @shirshanka
There was a problem hiding this comment.
This looks right, just needs to have the backend mapping on the resolvers.
yoonhyejin
commented
Jan 14, 2025
| }; | ||
|
|
||
| const renderTrainingJobs = () => { | ||
| const lineageTrainingJobs = model?.properties?.mlModelLineageInfo?.trainingJobs || []; |
There was a problem hiding this comment.
let me know if this is a valid approach @shirshanka
would there be any difference between pulling properties > trainingjobs or pulling relationships > trained by?
yoonhyejin
commented
Jan 14, 2025
| </InfoItem> | ||
| <InfoItem title="Aliases"> | ||
| <InfoItemContent> | ||
| {/* use versionProperties for aliases */} |
There was a problem hiding this comment.
commenting this out until this get merged : #12166
…at/update-mlflow-ui
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist