-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
feat(backend): sort by run metrics - step 3. Part of #3591 #4251
Merged
Merged
Changes from 28 commits
Commits
Show all changes
38 commits
Select commit
Hold shift + click to select a range
5b67273
enable pagination when expanding experiment in both the home page and…
jingzhang36 d3f8d1d
Revert "enable pagination when expanding experiment in both the home …
jingzhang36 601c257
Merge remote-tracking branch 'upstream/master'
jingzhang36 a95ce51
Merge branch 'master' of github.com:jingzhang36/pipelines
jingzhang36 949e99b
Merge remote-tracking branch 'upstream/master'
jingzhang36 2ad60e7
Merge branch 'master' of github.com:jingzhang36/pipelines
jingzhang36 61128e3
Merge remote-tracking branch 'upstream/master'
jingzhang36 0f3003b
Merge remote-tracking branch 'upstream/master'
jingzhang36 88f9df9
Merge remote-tracking branch 'upstream/master'
jingzhang36 9d65153
Merge remote-tracking branch 'upstream/master' into master
jingzhang36 bf9d42c
Merge branch 'master' of github.com:jingzhang36/pipelines into master
jingzhang36 5e49d3f
Merge remote-tracking branch 'upstream/master' into master
jingzhang36 cbcd57f
Merge branch 'master' of github.com:jingzhang36/pipelines into master
jingzhang36 983c0e1
Merge remote-tracking branch 'upstream/master' into master
jingzhang36 fbf9d40
Merge remote-tracking branch 'upstream/master' into master
jingzhang36 2ec3b1c
Merge remote-tracking branch 'upstream/master' into master
jingzhang36 0dbe684
sorting by run metrics is different from sorting by name, uuid, creat…
jingzhang36 432e9e5
Merge remote-tracking branch 'upstream/master' into master
jingzhang36 eca6ce6
Merge remote-tracking branch 'origin/master' into sort_metrics_2
jingzhang36 90b0857
unit test: add sorting on metrics with both asc and desc order
jingzhang36 76048b7
GetFieldValue in all models
jingzhang36 f5859ae
fix unit test
jingzhang36 dd401bf
whether to test in list_test. It's hacky when check mode == 'run'
jingzhang36 a75254d
Merge remote-tracking branch 'upstream/master' into master
jingzhang36 8b5e1c8
Merge remote-tracking branch 'origin/master' into tmp4
jingzhang36 1b3dcc4
move model specific code to model; prevent model package depends on l…
jingzhang36 80f514e
some assumption on token's Model field
jingzhang36 98353f9
fix the regular field checking logic
jingzhang36 ee22b69
Merge remote-tracking branch 'upstream/master' into master
jingzhang36 998ccc7
add comment to help devs to use the new field
jingzhang36 afc06b9
add a validation check
jingzhang36 be4be61
Listable object can be too large to be in token. So replace it with only
jingzhang36 5457634
Merge remote-tracking branch 'upstream/master' into master
jingzhang36 576ee2f
Merge branch 'master' of github.com:jingzhang36/pipelines into master
jingzhang36 69be419
Merge remote-tracking branch 'origin/master' into tmp4
jingzhang36 3b697ba
Merge branch 'tmp4' of github.com:jingzhang36/pipelines into tmp4
jingzhang36 6c71128
Merge remote-tracking branch 'upstream/master' into tmp4
jingzhang36 6124c82
matches func update
jingzhang36 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Can you comment example values of these fields?
That helps understanding these fields.
My initial confusion when reading this: Is it an ML model or a data model?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually this is not about the ML terminology, but about a terminology used in backend implementation . We actually can get clues from the existing backend implementation. If we take a look at our code, there is a folder called backend/src/apiserver/model. In that folder, we have structs job, run, experiment, etc. In other words, the run, job, experiment, etc. are considered a type of "model". (I am not sure about the history here though). Moreover, all those models (aka, job, run, experiment, etc.) implement the "listable" interface. In other words, the set of jobs, (or runs, experiments) is listable.
So back to this struct token. Token is applied to a listable (aka a set of runs, jobs, experiments etc.). So, in the token, we can add this model field to indicate which model (aka, run, job, experiment) this token applies to.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So I add some explanation to this field, pointing to the folder. Hope that would help.