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]Remove useless words (#12550) 

Signed-off-by: yanliang567 <yanliang.qiao@zilliz.com>
pull/12577/head
yanliang567 2021-12-01 22:24:11 +08:00 committed by GitHub
parent 3e46c2a523
commit a7af1042db
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/developer_guides/how-guarantee-ts-works.md
View File

@ -35,8 +35,7 @@ As shown in the figure below, when inserting data into the message queue, Milvus
records, but also insert timetick continuously. Taking "syncTs1" in the figure as an example, when downstream consumers
(such as QueryNodes) see syncTs1, it means that all the data which is earlier than syncTs1 has been consumed. In
other words, the inserted record with a timestamp smaller than syncTs1 will no longer appear in the message queue.
Of course, if there is, there must be a bug in the system. If you find it, we are pleased to solve it as soon as
possible.
![ts-watermask](./figs/guarantee-ts-ts-mask.png)