diff --git a/pom.xml b/pom.xml
index 44c8753..c8d73b7 100644
--- a/pom.xml
+++ b/pom.xml
@@ -645,7 +645,6 @@
100truetrue
- ${basedir}/src/site/resources/css/freebsd_docbook.css${basedir}/src/docbkx/customization.xsl2yes
@@ -662,6 +661,7 @@
truetrue../images/
+ ../css/freebsd_docbook.css
@@ -672,6 +672,7 @@
pre-siteimages/
+ css/freebsd_docbook.css
diff --git a/src/docbkx/book.xml b/src/docbkx/book.xml
index 66c3f12..a4e0b0e 100644
--- a/src/docbkx/book.xml
+++ b/src/docbkx/book.xml
@@ -889,7 +889,7 @@ System.out.println("md5 digest as string length: " + sbDigest.length); // ret
Schema Design SmackdownThis section will describe common schema design questions that appear on the dist-list. These are
- general guidelines and not laws - each application must consider it's own needs.
+ general guidelines and not laws - each application must consider its own needs.
Rows vs. VersionsA common question is whether one should prefer rows or HBase's built-in-versioning. The context is typically where there are
@@ -1267,7 +1267,7 @@ if (!b) {
NoSQL?HBase is a type of "NoSQL" database. "NoSQL" is a general term meaning that the database isn't an RDBMS which
- supports SQL as it's primary access language, but there are many types of NoSQL databases: BerkeleyDB is an
+ supports SQL as its primary access language, but there are many types of NoSQL databases: BerkeleyDB is an
example of a local NoSQL database, whereas HBase is very much a distributed database. Technically speaking,
HBase is really more a "Data Store" than "Data Base" because it lacks many of the features you find in an RDBMS,
such as typed columns, secondary indexes, triggers, and advanced query languages, etc.
@@ -1283,7 +1283,7 @@ if (!b) {
Automatic sharding: HBase tables are distributed on the cluster via regions, and regions are
automatically split and re-distributed as your data grows.Automatic RegionServer failover
- Hadoop/HDFS Integration: HBase supports HDFS out of the box as it's distributed file system.
+ Hadoop/HDFS Integration: HBase supports HDFS out of the box as its distributed file system.MapReduce: HBase supports massively parallelized processing via MapReduce for using HBase as both
source and sink.Java Client API: HBase supports an easy to use Java API for programmatic access.
@@ -1685,7 +1685,7 @@ rs.close();
Startup BehaviorIf run in a multi-Master environment, all Masters compete to run the cluster. If the active
- Master loses it's lease in ZooKeeper (or the Master shuts down), then then the remaining Masters jostle to
+ Master loses its lease in ZooKeeper (or the Master shuts down), then then the remaining Masters jostle to
take over the Master role.
diff --git a/src/docbkx/configuration.xml b/src/docbkx/configuration.xml
index 35a7a32..f6b5788 100644
--- a/src/docbkx/configuration.xml
+++ b/src/docbkx/configuration.xml
@@ -79,7 +79,7 @@ to ensure well-formedness of your document after an edit session.
DNS
- HBase uses the local hostname to self-report it's IP address.
+ HBase uses the local hostname to self-report its IP address.
Both forward and reverse DNS resolving must work in versions of
HBase previous to 0.92.0
The hadoop-dns-checker tool can be used to verify
@@ -794,7 +794,7 @@ stopping hbase............... Shutdown can take a moment to
in conf/hbase-env.sh to false
...
- # Tell HBase whether it should manage it's own instance of Zookeeper or not.
+ # Tell HBase whether it should manage its own instance of Zookeeper or not.
export HBASE_MANAGES_ZK=false Next set ensemble locations
and client port, if non-standard, in
hbase-site.xml, or add a suitably
diff --git a/src/docbkx/ops_mgt.xml b/src/docbkx/ops_mgt.xml
index 0873658..bad1516 100644
--- a/src/docbkx/ops_mgt.xml
+++ b/src/docbkx/ops_mgt.xml
@@ -238,7 +238,7 @@ row10 c1 c2
in conjunction with output from .
There are two ways to invoke this utility, with explicit classname and via the driver:
-$ bin/hbase org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFile <hdfs://storefileoutput> <tablename>
+$ bin/hbase org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles <hdfs://storefileoutput> <tablename>
.. and via the Driver..
HADOOP_CLASSPATH=`${HBASE_HOME}/bin/hbase classpath` ${HADOOP_HOME}/bin/hadoop jar ${HBASE_HOME}/hbase-VERSION.jar completebulkload <hdfs://storefileoutput> <tablename>