From 3b8773b9992ea5c7262ae9e3a0955890ace9b9d9 Mon Sep 17 00:00:00 2001 From: "min.tian" Date: Tue, 14 Dec 2021 16:23:46 +0800 Subject: [PATCH] [skip ci] Check the syntax of meta_snapshot docs (#13307) Signed-off-by: min.tian --- docs/design_docs/milvus_meta_snapshot_en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/design_docs/milvus_meta_snapshot_en.md b/docs/design_docs/milvus_meta_snapshot_en.md index 6345e7d5fe..6e8c6ce8d9 100644 --- a/docs/design_docs/milvus_meta_snapshot_en.md +++ b/docs/design_docs/milvus_meta_snapshot_en.md @@ -67,7 +67,7 @@ The output of above test program should look like this: --- PASS: TestMVCC (0.01s) ``` -In `etcd`, each write operation would add `1` to `Revision`. So if we specify the `Revision` value at query, we can get the historical value under that `Revision`. +In `etcd`, each writes operation would add `1` to `Revision`. So if we specify the `Revision` value at query, we can get the historical value under that `Revision`. `metaSnapShot` is based on this feature of `etcd`. We will write an extra `Timestamp` on each write operation. `etcd`'s `Txn` makes sure that the `Timestamp` would have the same `Revision` with user data.