admin/milvus
1
0
Fork 0
mirror of https://gitee.com/milvus-io/milvus.git synced 2025-12-06 17:18:35 +08:00
Code Issues Packages Projects Releases Wiki Activity

[skip e2e] Fix grammar (#14659)

Browse Source 
Signed-off-by: Bennu <yunmei.li@zilliz.com>
This commit is contained in:
Bennu 2021-12-31 14:18:07 +08:00 committed by GitHub
parent bde6ee43c1
commit 460b49310d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/design_docs/milvus_timesync_en.md
View File

@ -42,7 +42,7 @@ It's easy to achieve this in a `single-node` database. But for a `Distributed Sy
Like [TiKV](https://github.com/tikv/tikv), Milvus 2.0 provides `TSO` service. All the events must alloc timestamp from `TSO`, not from local clock, so the first problem can be solved. Like [TiKV](https://github.com/tikv/tikv), Milvus 2.0 provides `TSO` service. All the events must alloc timestamp from `TSO`, not from local clock, so the first problem can be solved.
`TSO` is provided by the `RootCoord` component. Clients could alloc one or more timestamp in a single request; the `proto` is defined as following. `TSO` is provided by the `RootCoord` component. Clients could alloc one or more timestamp in a single request; the `proto` is defined as follows.
```proto ```proto
service RootCoord { service RootCoord {