From 17887de1407f4a68eb4fb9c70ce8029f402d01d1 Mon Sep 17 00:00:00 2001 From: Xieql Date: Mon, 10 Jan 2022 13:26:24 +0800 Subject: [PATCH] [skip e2e] Improve annotation (#15071) Signed-off-by: Xieql --- docs/design_docs/milvus_create_index_en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/design_docs/milvus_create_index_en.md b/docs/design_docs/milvus_create_index_en.md index b293db102a..05ef0cf932 100644 --- a/docs/design_docs/milvus_create_index_en.md +++ b/docs/design_docs/milvus_create_index_en.md @@ -180,7 +180,7 @@ message CreateIndexRequest { 13. When receiving `CreateIndex` request, `IndexNode` would wrap this request into `IndexBuildTask`, and push this task into `IndexBuildQueue`, then send response to `IndexCoord`. -14. There is a background service, `indexBuildLoop`, in the `IndexNode`. `indexBuildLoop` would call `scheduleIndexBuildTask` to get a `IndexBuildTask` from `IndexBuildQueue`, and then start another `goroutine` to build index and update meta. +14. There is a background service, `indexBuildLoop`, in the `IndexNode`. `indexBuildLoop` would call `scheduleIndexBuildTask` to get an `IndexBuildTask` from `IndexBuildQueue`, and then start another `goroutine` to build index and update meta. _Note_: `IndexNode` will not notify the `QueryCoord` to load the index files, if a user wants to speed up search by these index files, he should call `ReleaseCollection` firstly, then call `LoadCollection` to load these index files.