milvus-io/milvus

[Feature]: Support Truncate collection

Open

#26,280 opened on Aug 11, 2023

View on GitHub
 (8 comments) (0 reactions) (2 assignees)Go (4,000 forks)batch import
good first issuekind/feature

Repository metrics

Stars
 (44,298 stars)
PR merge metrics
 (Avg merge 7d 8h) (280 merged PRs in 30d)

Description

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe.

Truncate a collection cleans all data in a collection. This can help user to clean up data as soon as possible.

To truncate a collection

  1. Disalble writing of a collection
  2. release the collection
  3. change collection id to a new value
  4. cleanup all the meta of the old collection
  5. wait for async garbage colleciton of the actual. data

Describe the solution you'd like.

No response

Describe an alternate solution.

No response

Anything else? (Additional Context)

No response

Contributor guide

Research direction
Start by understanding the collection lifecycle in Milvus, focusing on the write and release mechanisms. Look at the codebase in the 'internal' directory for collection management. The issue outlines steps: disable writing, release collection, change collection ID, cleanup metadata, and await async garbage collection. There are two assignees, so check their linked work or comments. Review the garbage collection process for async data cleanup. The maintainers may have additional context in the comments (8 comments) about design decisions.
Tech stack
go
Domain
database
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Go programmingMilvus architecture overviewDistributed systems basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30