Repository: hbase Updated Branches: refs/heads/master 76ffc7503 -> 3702b0b44
HBASE-11655 ADDENDUM - typo fix Project: http://git-wip-us.apache.org/repos/asf/hbase/repo Commit: http://git-wip-us.apache.org/repos/asf/hbase/commit/3702b0b4 Tree: http://git-wip-us.apache.org/repos/asf/hbase/tree/3702b0b4 Diff: http://git-wip-us.apache.org/repos/asf/hbase/diff/3702b0b4 Branch: refs/heads/master Commit: 3702b0b445582264b2452d004d4f2c38978a4d02 Parents: 76ffc75 Author: Jonathan M Hsieh <[email protected]> Authored: Mon Aug 18 14:25:57 2014 -0700 Committer: Jonathan M Hsieh <[email protected]> Committed: Mon Aug 18 14:25:57 2014 -0700 ---------------------------------------------------------------------- src/main/docbkx/shell.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/hbase/blob/3702b0b4/src/main/docbkx/shell.xml ---------------------------------------------------------------------- diff --git a/src/main/docbkx/shell.xml b/src/main/docbkx/shell.xml index 7a850ac..a400d8d 100644 --- a/src/main/docbkx/shell.xml +++ b/src/main/docbkx/shell.xml @@ -134,7 +134,7 @@ return $status <para>Getting an exit code of 0 means that the command you scripted definitely succeeded. However, getting a non-zero exit code does not necessarily mean the command failed. The command could have succeeded, but the client lost connectivity, - or some other event obscured its succewss. This is because RPC commands are + or some other event obscured its success. This is because RPC commands are stateless. The only way to be sure of the status of an operation is to check. For instance, if your script creates a table, but returns a non-zero exit value, you should check whether the table was actually created before trying again to create
