You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@crunch.apache.org by "Josh Wills (JIRA)" <ji...@apache.org> on 2013/08/02 08:39:48 UTC

[jira] [Commented] (CRUNCH-245) hbase.zookeeper.quorum is overriden by hbase-default.xml

    [ https://issues.apache.org/jira/browse/CRUNCH-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727409#comment-13727409 ] 

Josh Wills commented on CRUNCH-245:
-----------------------------------

It was probably me copying-and-pasting it from somewhere: I think it's okay to remove it.
                
> hbase.zookeeper.quorum is overriden by hbase-default.xml
> --------------------------------------------------------
>
>                 Key: CRUNCH-245
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-245
>             Project: Crunch
>          Issue Type: Bug
>          Components: IO
>            Reporter: Chao Shi
>            Assignee: Chao Shi
>
> I'm using crunch-hbase on a small cluster with 4 nodes. The job complains cannot talk to ZK at *localhost*. In fact, I specify hbase.zookeeper.quorum programmatically, but it seems it is not passed to the job (as observed in JT's webpage).
> After some investigation, I found the cause is the following code. I have no idea why addHBaseResources is called here. Anybody knows? After comment it out, the job can read data from HBase.
>   @Override
>   public void configureSource(Job job, int inputId) throws IOException {
>     Configuration conf = job.getConfiguration();
>     HBaseConfiguration.addHbaseResources(conf);
>     TableMapReduceUtil.addDependencyJars(job);
>     if (inputId == -1) {
>       job.setMapperClass(CrunchMapper.class);
>       job.setInputFormatClass(inputBundle.getFormatClass());
>       inputBundle.configure(job.getConfiguration());
>     } else {
>       Path dummy = new Path("/hbase/" + table);
>       CrunchInputs.addInputPath(job, dummy, inputBundle, inputId);
>     }
>   }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira