milvus-io
/
milvus
mirror of https://github.com/milvus-io/milvus.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[skip ci] Fix grammar and punctuation (#8879) 

Signed-off-by: sida shen <sida@sidas-MacBook-Pro.local>

Co-authored-by: sida shen <sida@sidas-MacBook-Pro.local>
pull/8891/head
SS 2021-09-29 19:24:22 +08:00 committed by GitHub
parent 27b4f0d5e3
commit d66cb16b94
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/design_docs/index_design.md
View File

@ -30,9 +30,9 @@ In Milvus, index building is performed asynchronously. When IndexCoordinate rece
RootCoordinate, it will first check whether the same index has been created according to the parameters. If the same
index has been created, it will return the IndexBuildID of the existing task. Otherwise, assign a globally unique
IndexBuildID to the task, then records the task in the MetaTable, and writes the MetaTable to the ETCD, and then
returns it to RootCoordinate. At this point RootCoordinate already knows that it has successfully sent the task to
returns it to RootCoordinate. At this point, RootCoordinate already knows that it has successfully sent the task to
IndexCoordinate. In fact, the index construction has not been completed yet. IndexCoordinate will have a background
process to find all the index tasks that need to be allocated periodically, and then allocate it to IndexNode for
process to find all the index tasks that need to be allocated periodically, and then allocate them to IndexNode for
actual execution.
When IndexCoordinate receives a request to delete an index from RootCoordinate, IndexCoordinate traverses the MetaTable,
@ -42,7 +42,7 @@ When the index task is marked as deleted, and the index status is complete, the
deleted from the MetaTable.
When IndexCoordinate receives a query index status request from other components, first check whether the corresponding
index task is marked for deletion in the MetaTable. If marked for deletion, the return index does not exist, otherwise
index task is marked for deletion in the MetaTable. If marked for deletion, the return index does not exist, otherwise,
it returns the index information
## 8.3 Feature Design