You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (Commented) (JIRA)" <ji...@apache.org> on 2012/01/10 01:47:39 UTC
[jira] [Commented] (HBASE-4151) completebulkload checks zoo.cfg
even though ZK ensemble is specified in hbase-site.xml
[ https://issues.apache.org/jira/browse/HBASE-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182964#comment-13182964 ]
stack commented on HBASE-4151:
------------------------------
@Mubarak So you are just doc'ing the fact that you can pass a -conf arg because completebulkload implements Tool? Since Tool can do more than just -conf, perhaps you should say this? Put '[genericOptions]' instead of '-conf FILENAME' in your patch and add line that points to genericOptions doc: http://hadoop.apache.org/common/docs/current/api/org/apache/hadoop/util/GenericOptionsParser.html#GenericOptions? (I took a look at other Tool implementations and doesn't seem to be a standard way of doing ths... that I can see)
> completebulkload checks zoo.cfg even though ZK ensemble is specified in hbase-site.xml
> --------------------------------------------------------------------------------------
>
> Key: HBASE-4151
> URL: https://issues.apache.org/jira/browse/HBASE-4151
> Project: HBase
> Issue Type: Bug
> Components: mapreduce
> Affects Versions: 0.94.0
> Environment: HBase-0.90.1
> Reporter: Seyed
> Priority: Minor
> Labels: hbase
> Attachments: HBASE-4151.trunk.v1.patch
>
>
> I have generated HFiles using importtsv and tried to bulk load them using completebulkload, even though i have specified the ZK quorum ensemble and client port in hbase-site.xml, completebulkload looks for ZK ensemble and client port in zoo.cfg, even after i have specified parameters in zoo.cfg, i was getting NullPointerException at line 167 in ZKConfig.java
> {code}
> if (conf.get(HConstants.CLUSTER_DISTRIBUTED).equals(HConstants.CLUSTER_IS_DISTRIBUTED)
> && value.startsWith("localhost")) {
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira