[HBASE-21536] Fix completebulkload usage instructions

• Type: Task
• Status: Resolved
• Priority: Trivial
• Resolution: Fixed
• Fix Version/s: 3.0.0-alpha-1, 2.2.0, 2.3.0, 2.1.6
• Component/s: documentation, mapreduce
• Release Note: Added completebulkload short name for BulkLoadHFilesTool to bin/hbase.
• Assignee: Artem Ervits
• Reporter: Artem Ervits
• Created: 30/Nov/18 20:13
• Updated: 06/Jun/19 21:18
• Resolved: 06/Jun/19 17:56

Description

Usage information upon invoking LoadIncrementalHFiles is misleading and error-prone.

usage: completebulkload /path/to/hfileoutputformat-output tablename -loadTable
-Dcreate.table=no - can be used to avoid creation of table by this tool
Note: if you set this to 'no', then the target table must already exist in HBase
-loadTable implies your baseDirectory to store file has a depth of 3 ,you must have an existing table
-Dignore.unmatched.families=yes - can be used to ignore unmatched column families

in case of invoking the class via hbase command, completebulkload argument is unnecessary and only required via hadoop jar invocation. This is also an attempt to clarify where <-loadTable> and <-Dargs> arguments go on the command line.

Furthermore, since LoadIncrementalHFiles was recently moved out of hbase-server.jar to hbase-mapreduce, updating ref guide to demonstrate as such.

Issue Links

• relates to: HBASE-22396 Backport HBASE-21536 to branch-1