From 4a5b94478e6109843e0b92b6ba2a8dd39440ed16 Mon Sep 17 00:00:00 2001 From: Xiang Li Date: Mon, 24 Aug 2015 10:40:05 -0700 Subject: [PATCH] etcdserverpb: update comment for txn request --- etcdserver/etcdserverpb/rpc.proto | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/etcdserver/etcdserverpb/rpc.proto b/etcdserver/etcdserverpb/rpc.proto index 6550a03c1..8dc6301d6 100644 --- a/etcdserver/etcdserverpb/rpc.proto +++ b/etcdserver/etcdserverpb/rpc.proto @@ -127,11 +127,10 @@ message Compare { } } -// First all the compare requests are processed. -// If all the compare succeed, all the success -// requests will be processed. -// Or all the failure requests will be processed and -// all the errors in the comparison will be returned. +// If the comparisons succeed, then the success requests will be processed in order, +// and the response will contain their respective responses in order. +// If the comparisons fail, then the failure requests will be processed in order, +// and the response will contain their respective responses in order. // From google paxosdb paper: // Our implementation hinges around a powerful primitive which we call MultiOp. All other database