From 4cddfbba3099e58fa46ee1f18e8a00a102364d3e Mon Sep 17 00:00:00 2001 From: yanliang567 <82361606+yanliang567@users.noreply.github.com> Date: Mon, 1 Nov 2021 18:21:57 +0800 Subject: [PATCH] [skip ci]Update drop collection md (#11006) Signed-off-by: yanliang567 --- docs/design_docs/milvus_drop_collection_en.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/design_docs/milvus_drop_collection_en.md b/docs/design_docs/milvus_drop_collection_en.md index b12137249c..377dbe5b0f 100644 --- a/docs/design_docs/milvus_drop_collection_en.md +++ b/docs/design_docs/milvus_drop_collection_en.md @@ -1,6 +1,7 @@ # Drop Collection -`Milvus 2.0` uses `Collection` to represent a set of data, like `Table` in traditional database. Users can create or drop `Collection`. Altering the `Schema` of `Collection` is not supported yet. 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`. +`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: