You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hbase.apache.org by ch...@apache.org on 2017/12/19 15:37:33 UTC
hbase git commit: HBASE-18404 fixed typo in acid semantics
Repository: hbase
Updated Branches:
refs/heads/branch-2 1dca9142a -> 5cf0e62a5
HBASE-18404 fixed typo in acid semantics
Signed-off-by: Sean Busbey <bu...@apache.org>
Signed-off-by: Chia-Ping Tsai <ch...@gmail.com>
Project: http://git-wip-us.apache.org/repos/asf/hbase/repo
Commit: http://git-wip-us.apache.org/repos/asf/hbase/commit/5cf0e62a
Tree: http://git-wip-us.apache.org/repos/asf/hbase/tree/5cf0e62a
Diff: http://git-wip-us.apache.org/repos/asf/hbase/diff/5cf0e62a
Branch: refs/heads/branch-2
Commit: 5cf0e62a557f987e68d7d0768e11e650c49a844c
Parents: 1dca914
Author: coral <co...@cloudera.com>
Authored: Thu Jul 20 14:31:59 2017 -0500
Committer: Chia-Ping Tsai <ch...@gmail.com>
Committed: Tue Dec 19 23:37:21 2017 +0800
----------------------------------------------------------------------
src/main/site/xdoc/acid-semantics.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/hbase/blob/5cf0e62a/src/main/site/xdoc/acid-semantics.xml
----------------------------------------------------------------------
diff --git a/src/main/site/xdoc/acid-semantics.xml b/src/main/site/xdoc/acid-semantics.xml
index 2696df7..2d4eb6a 100644
--- a/src/main/site/xdoc/acid-semantics.xml
+++ b/src/main/site/xdoc/acid-semantics.xml
@@ -93,7 +93,7 @@ under the License.
<section name="Atomicity">
<ol>
- <li>All mutations are atomic within a row. Any put will either wholely succeed or wholely fail.[3]</li>
+ <li>All mutations are atomic within a row. Any put will either wholly succeed or wholly fail.[3]</li>
<ol>
<li>An operation that returns a "success" code has completely succeeded.</li>
<li>An operation that returns a "failure" code has completely failed.</li>
@@ -225,7 +225,7 @@ under the License.
log. This does not actually imply an fsync() to magnetic media, but rather just that the data has been
written to the OS cache on all replicas of the log. In the case of a full datacenter power loss, it is
possible that the edits are not truly durable.</p>
- <p>[3] Puts will either wholely succeed or wholely fail, provided that they are actually sent
+ <p>[3] Puts will either wholly succeed or wholly fail, provided that they are actually sent
to the RegionServer. If the writebuffer is used, Puts will not be sent until the writebuffer is filled
or it is explicitly flushed.</p>