[
https://issues.apache.org/jira/browse/HBASE-21536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16836526#comment-16836526
]
Artem Ervits commented on HBASE-21536:
--------------------------------------
I think so [~psomogyi] the output is the same whether you use
LoadIncrementalHFiles or BulkLoadHFilesTool.
{code:java}
[vagrant@hadoop ~]$ hbase org.apache.hadoop.hbase.tool.BulkLoadHFilesTool
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/opt/hadoop/hadoop-2.7.7/share/hadoop/common/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/opt/hbase/hbase-2.2.0/lib/client-facing-thirdparty/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
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{code}
However, the reference guide has no documentation on invoking this new tool. So
perhaps we can merge this Jira and I can add new one targeting 3.x and finish
the documentation there?
> Fix completebulkload usage instructions
> ---------------------------------------
>
> Key: HBASE-21536
> URL: https://issues.apache.org/jira/browse/HBASE-21536
> Project: HBase
> Issue Type: Task
> Components: documentation, mapreduce
> Reporter: Artem Ervits
> Assignee: Artem Ervits
> Priority: Trivial
> Attachments: HBASE-21536.v01.patch
>
>
> Usage information upon invoking LoadIncrementalHFiles is misleading and
> error-prone.
> {code:java}
> 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{code}
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
