You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hbase.apache.org by st...@apache.org on 2018/09/14 17:04:47 UTC
[hbase-operator-tools] branch master updated: Front the hbck1 naming
This is an automated email from the ASF dual-hosted git repository.
stack pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/hbase-operator-tools.git
The following commit(s) were added to refs/heads/master by this push:
new 0a27431 Front the hbck1 naming
0a27431 is described below
commit 0a27431303706546f9fb2cfc7b2e2c50e5a3061f
Author: Michael Stack <st...@apache.org>
AuthorDate: Fri Sep 14 10:04:22 2018 -0700
Front the hbck1 naming
---
hbase-hbck2/README.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/hbase-hbck2/README.md b/hbase-hbck2/README.md
index 3df0818..61b5f21 100644
--- a/hbase-hbck2/README.md
+++ b/hbase-hbck2/README.md
@@ -1,13 +1,13 @@
# HBCK2
HBCK2 is the successor to [hbck](https://hbase.apache.org/book.html#hbck.in.depth),
-the hbase-1.x fixup tool. Use it in place of the old _hbck_ tool against hbase-2.x
-installs.
+the hbase-1.x fixup tool (A.K.A _hbck1_). Use it in place of _hbck1_ making repairs
+against hbase-2.x installs.
-## hbck (HBCK1)
+## _hbck1_
The _hbck_ that ships with hbase-1.x (A.K.A _hbck1_) should not be run against an
hbase-2.x cluster. It may do damage. While _hbck1_ is still bundled inside hbase-2.x
-- to minimize surprise (it has a fat pointer to _HBCK2_ at the head of its help
-output) -- its write-facility has been removed. It can report on the state of an
+output) -- it's write-facility has been removed. It can report on the state of an
hbase-2.x cluster but its assessments may be inaccurate.