Comments (19)
+1 to this being important.
from pipelines.
@Ark-kun maybe we should have labels based filter, people can add labels like owner, project,..
from pipelines.
This requires the backend API to be there. @IronPan to chime in, is there an issue tracking that work?
from pipelines.
API would provided as part of this #112
from pipelines.
More context from @IronPan: That API orphans the deleted experiment's runs though, it doesn't delete them.
This is fine for now, but if we don't also offer a delete run API, the All runs view will be cluttered with all the orphaned runs.
@ajayalfred any thoughts here? What do you think of this as a starting point?
from pipelines.
Since runs are organized inside experiments, a user would expect deleting an experiment to delete the runs contained as well. I don't see a usecase where the user will expect this to behave otherwise and produce orphaned runs.
A delete run API is still needed for the case when a user wants to delete an individual run/set of runs inside an experiment.
Does that make sense?
from pipelines.
Yup, that's what I'd prefer to do too.
So I guess we'll block this on support for deleting an experiment's runs from the backend.
cc/ @IronPan.
from pipelines.
Ho folks - any progress on this one?
from pipelines.
I don't think we have anyone working on this, feel free to pick up the discussion if you feel like it.
There is however some work I'm doing now to support archiving runs, which should help declutter the workspace. Experiments are still create-only though.
from pipelines.
+1 on this, in multi-user settings experiments will pile up quickly
from pipelines.
+1 on this, in multi-user settings experiments will pile up quickly
The solution to this is probably a default filter that only shows your own experiments.
from pipelines.
maybe we should have labels based filter, people can add labels like owner, project,..
I like this approach.
from pipelines.
What if instead of deleting, we just had an option to archive, like with runs. There should also be an option to archive pipelines. That way no metadata is lost, but old experiments are out of the way
Sent with GitHawk
from pipelines.
Why not allow archiving / deleting for experiments with no unarchived runs? Would be interested in this feature.
from pipelines.
no metadata is lost, but old experiments are out of the wa
Would showing the experiments with recent runs first solve your issues? #249
from pipelines.
no metadata is lost, but old experiments are out of the wa
Would showing the experiments with recent runs first solve your issues? #249
Probably. I just want to hide the experiments that aren't relevant to me. The filter ideally should only show experiments you create by default too (in the situation where multiple scientists are sharing a cluster).
from pipelines.
Closing this as a duplicate of #1263
We plan to support archiving experiments in KFP 1.0
from pipelines.
/close
from pipelines.
@Bobgy: Closing this issue.
In response to this:
/close
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.
from pipelines.
Related Issues (20)
- [feature] Upgrade KServe component to support v2 features
- [bug] Unable to compile pipeline after upgrading to KFP 2.4 HOT 4
- [feature] Add image build vars to backend Makefiles HOT 1
- [backend] Tolerations are not added into Pod spec. HOT 1
- [backend] "cannot save parameter" for cached steps HOT 1
- [sdk] Wrong DSL component and pipeline return types
- [feature] Use `s3://` for MinIO usage
- [sdk] Relax `python_requires` in `setup.py`
- [feature] Show Pod Events in KFP v2 UI
- [sdk] trusted host is the same as index url
- [Tracker] Migrate prow tests to GitHub Action HOT 2
- Migrate periodic functional tests to GH Actions HOT 2
- Migrate presubmit tests to GH Actions HOT 2
- Migrate postsubmit tests to GH Actions HOT 8
- Replacement of components with "@graph_component" decorator in V2 HOT 1
- Ml Pipeline Artifact 503 RBAC:Access Denied HOT 4
- [frontend] incompatible error while building frontend image HOT 2
- [feature] Upgrade Node version (node 14 has reached EOL) HOT 2
- [frontend] Latency when listing runs HOT 7
- [test] `kubeflow-pipeline-e2e-test` and `kubeflow-pipeline-upgrade-test` broken and blocks presubmit
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pipelines.