-
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
[feature] Allow the ability to sort Experiments by "last run creation" #10884
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
/remove-lifecycle stale |
/assign |
@ElayAharoni we have implemented this in our downstream here: opendatahub-io@bf77909 , we just haven't had the bandwidth to forward it upstream yet if you would like to take this one, would you be open to rebasing over this commit for kfp? |
…0884 Signed-off-by: Elay Aharoni (EXT-Nokia) <[email protected]>
…ments-by-last-run-creation-#10884' into Allow-the-ability-to-sort-Experiments-by-last-run-creation-kubeflow#10884
|
whoops, I commented on the wrong issue heh |
/reopen |
@HumairAK: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
… run creation. Fixes #10884 (#11163) * UPSTREAM: <carry>: add last_run_creation Signed-off-by: Humair Khan <[email protected]> * Allow-the-ability-to-sort-Experiments-by-last-run-creation-#10884 Signed-off-by: Elay Aharoni (EXT-Nokia) <[email protected]> * UPSTREAM: <carry>: chore(backend): Rename UpdateLastRun -> SetLastRunTimestamp follup up to bf77909. Rename UpdateLastRun -> SetLastRunTimestamp also tweak a related log message Signed-off-by: Greg Sheremeta <[email protected]> * UPSTREAM: <carry>: chore(backend): Rename UpdateLastRun -> SetLastRunTimestamp follup up to bf77909. Rename UpdateLastRun -> SetLastRunTimestamp also tweak a related log message Signed-off-by: Greg Sheremeta <[email protected]> --------- Signed-off-by: Humair Khan <[email protected]> Signed-off-by: Elay Aharoni (EXT-Nokia) <[email protected]> Signed-off-by: Greg Sheremeta <[email protected]> Co-authored-by: Humair Khan <[email protected]> Co-authored-by: Elay Aharoni (EXT-Nokia) <[email protected]> Co-authored-by: Greg Sheremeta <[email protected]>
… run creation. Fixes kubeflow#10884 (kubeflow#11163) * UPSTREAM: <carry>: add last_run_creation Signed-off-by: Humair Khan <[email protected]> * Allow-the-ability-to-sort-Experiments-by-last-run-creation-kubeflow#10884 Signed-off-by: Elay Aharoni (EXT-Nokia) <[email protected]> * UPSTREAM: <carry>: chore(backend): Rename UpdateLastRun -> SetLastRunTimestamp follup up to bf77909. Rename UpdateLastRun -> SetLastRunTimestamp also tweak a related log message Signed-off-by: Greg Sheremeta <[email protected]> * UPSTREAM: <carry>: chore(backend): Rename UpdateLastRun -> SetLastRunTimestamp follup up to bf77909. Rename UpdateLastRun -> SetLastRunTimestamp also tweak a related log message Signed-off-by: Greg Sheremeta <[email protected]> --------- Signed-off-by: Humair Khan <[email protected]> Signed-off-by: Elay Aharoni (EXT-Nokia) <[email protected]> Signed-off-by: Greg Sheremeta <[email protected]> Co-authored-by: Humair Khan <[email protected]> Co-authored-by: Elay Aharoni (EXT-Nokia) <[email protected]> Co-authored-by: Greg Sheremeta <[email protected]>
Feature Area
/area frontend
/area backend
What feature would you like to see?
When experiments list get's rather long, would be very useful to be able to sort the experiments by "last run creation date":
In the UI this would result in the user being able to click the "Last 5 runs" column header, and sort by this. Thus also getting rid of the "Cannot sort by this column" mouseover message.
Note that this field does not currently exist in the backend api, and would need to be added. This would result in a new column on the Experiments table for which we could sort this field by. This field would need to be updated everytime a run is created, this means when:
What is the use case or pain point?
It is hard to find experiments that have had a recent run because we cannot sort by this field.
Is there a workaround currently?
No
Love this idea? Give it a 👍.
The text was updated successfully, but these errors were encountered: