admin/milvus
1
0
Fork 0
mirror of https://gitee.com/milvus-io/milvus.git synced 2026-01-07 19:31:51 +08:00
Code Issues Packages Projects Releases Wiki Activity

[skip ci] improve milvus_drop_collection_en.md (#11624)

Browse Source 
Signed-off-by: Gitea <zizhao.chen@zilliz.com>
This commit is contained in:
nameczz 2021-11-11 13:21:09 +08:00 committed by GitHub
parent 5227db3fb4
commit 89c17c265b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/design_docs/milvus_drop_collection_en.md
View File

@ -1,6 +1,6 @@
# Drop Collection
`Milvus 2.0` uses `Collection` to represent a set of data, like `Table` in traditional database. Users can create or drop `Collection`.
`Milvus 2.0` uses `Collection` to represent a set of data, like `Table` in traditional database. Users can create or drop `Collection`.
This article introduces the execution path of `Drop Collection`. At the end of this article, you should know which components are involved in `Drop Collection`.
The execution flow of `Drop Collection` is shown in the following figure:
@ -19,9 +19,12 @@ service MilvusService {
}
message DropCollectionRequest {
common.MsgBase base = 1; // must
// Not useful for now
common.MsgBase base = 1;
// Not useful for now
string db_name = 2;
string collection_name = 3; // must
// Required, the collection name in milvus
string collection_name = 3;
}
```