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]Update create collection md file (#10938) 

Signed-off-by: yanliang567 <yanliang.qiao@zilliz.com>
pull/10942/head
yanliang567 2021-10-30 11:29:03 +08:00 committed by GitHub
parent 88b4b17b56
commit be4a9a48b3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/design_docs/milvus_create_collection_en.md
View File

@ -106,7 +106,7 @@ type CreateCollectionReqTask struct {
4. `CreateCollectionReqTask.Execute` would alloc `CollecitonID` and default `PartitionID`, and set `Virtual Channel` and `Physical Channel`, which are used by `MsgStream`, then write the `Collection`'s meta into `metaTable`
5. After `Collection`'s meta writing into `metaTable`, `Milvus` would consider this collection has been created successfully.
5. After `Collection`'s meta written into `metaTable`, `Milvus` would consider this collection has been created successfully.
6. `RootCoord` would alloc a timestamp from `TSO` before writing `Collection`'s meta into `metaTable`, and this timestamp is considered as the point when the collection was created
@ -133,6 +133,8 @@ message CreateCollectionRequest {
_Notes:_
1. In the `Proxy`, all `DDL` requests will be wrapped into `task`, and push the `task` into `DdTaskQueue`, the background service will read a new `task` from `DdTaskQueue` only when the previous one is finished. So all the `DDL` requests are executed serially on the `Proxy`
1. In `Proxy`, all `DDL` requests will be wrapped into `task`, and push the `task` into `DdTaskQueue`.
A background service will read a new `task` from `DdTaskQueue` only when the previous one is finished.
So all the `DDL` requests are executed serially on the `Proxy`
2. In the `RootCoord`, all `DDL` requests will be wrapped into `reqTask`, but there is no task queue, so the `DDL` requests will be executed in parallel on `RootCoord`.
2. In `RootCoord`, all `DDL` requests will be wrapped into `reqTask`, but there is no task queue, so the `DDL` requests will be executed in parallel on `RootCoord`.