influxdata / influxdata/influxdb
deleting a large bucket from the UI takes a long time
Open
Nobody has claimed this yet.
kind/enhancement
team/ui
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
if you load a bucket with a good amount of data, deleting the bucket takes a long time.
- Does delete bucket api actually remove the data? Or just tombstone it and delete it later?
- The UI needs some sort of indicator that it is waiting for the delete to return
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are identified. Start by checking the delete bucket API behavior for large buckets, then trace the UI's bucket-deletion flow. Done means the deletion behavior is understood and the UI clearly indicates that it is waiting for the delete request to return.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, database, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100