kudu-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From danburk...@apache.org
Subject [3/6] kudu git commit: Finish incomplete sentence in docs/design-docs/rpc-retry-and-failover.md
Date Mon, 28 Nov 2016 19:57:48 GMT
Finish incomplete sentence in docs/design-docs/rpc-retry-and-failover.md

This just finishes an incomplete sentence that was missed
during review.

Change-Id: I5a390d76d053dd34f20c058a1733ba949143d2b3
Reviewed-on: http://gerrit.cloudera.org:8080/5228
Tested-by: Kudu Jenkins
Reviewed-by: Todd Lipcon <todd@apache.org>
Reviewed-by: Alexey Serbin <aserbin@cloudera.com>


Project: http://git-wip-us.apache.org/repos/asf/kudu/repo
Commit: http://git-wip-us.apache.org/repos/asf/kudu/commit/0cb04557
Tree: http://git-wip-us.apache.org/repos/asf/kudu/tree/0cb04557
Diff: http://git-wip-us.apache.org/repos/asf/kudu/diff/0cb04557

Branch: refs/heads/master
Commit: 0cb045574c2537257b002eefb16f585ddda4fa10
Parents: c7b0372
Author: David Alves <dralves@apache.org>
Authored: Fri Nov 25 14:33:48 2016 -0800
Committer: David Ribeiro Alves <dralves@apache.org>
Committed: Mon Nov 28 19:18:45 2016 +0000

----------------------------------------------------------------------
 docs/design-docs/rpc-retry-and-failover.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/kudu/blob/0cb04557/docs/design-docs/rpc-retry-and-failover.md
----------------------------------------------------------------------
diff --git a/docs/design-docs/rpc-retry-and-failover.md b/docs/design-docs/rpc-retry-and-failover.md
index 70c026d..0375f72 100644
--- a/docs/design-docs/rpc-retry-and-failover.md
+++ b/docs/design-docs/rpc-retry-and-failover.md
@@ -183,8 +183,9 @@ from history.
 ## Declaring RPCs as Exactly Once
 
 To make sure the results of an RPC are tracked **transiently** on the server side (we'll
cover how
-to make sure ), all that is required is that the service definition enables the appropriate
option.
-For instance in the case of writes this is done the following way:
+we made sure that write results were tracked **persistently** in the following section),
all that
+is required is that the service definition enables the appropriate option. For instance in
the case
+of writes this is done the following way:
 
 ```
 service TabletServerService {


Mime
View raw message