[
https://issues.apache.org/jira/browse/SQOOP-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538057#comment-14538057
]
John Blakeney commented on SQOOP-857:
-------------------------------------
I believe this behavior has changed since this ticket was opened, and that an
HBase ZooKeeper quorum can now be specified on the command line. I just
successfully ran a Sqoop job as follows, and the data was written to the
specified HBase cluster. Without {{-Dhbase.zookeeper.quorum}}, the job
attempted to use localhost:2181 and failed.
{{sqoop import -Dhbase.zookeeper.quorum=ZK_HOSTNAME --hbase-create-table ...}}
I'm using Sqoop 1.4.5 as part of CDH 5.3.1.
> -D switches on Sqoop's commandline by using HBase Import are ignored
> --------------------------------------------------------------------
>
> Key: SQOOP-857
> URL: https://issues.apache.org/jira/browse/SQOOP-857
> Project: Sqoop
> Issue Type: Improvement
> Components: hbase-integration
> Affects Versions: 1.4.2
> Reporter: Alexander Alten-Lorenz
>
> Any chance "-D hbase.zookeeper.quorum" is only used for the submitted
> Hadoop SQOOP job, but not for any SQOOP client activities?
> When passing -D hbase.zookeeper.quorum=zkhost1:2181 on sqoop's import, there
> is no error message, according to the log output SQOOP continues to use the
> conf file based or default settings:
> 13/01/31 00:41:31 INFO zookeeper.ZooKeeper: Initiating client connection,
> connectString=localhost:2181 sessionTimeout=180000 watcher=hconnection
> Sqoop reads the configuration via
> {code}// Add HBase configuration files to this conf object.
> HBaseConfiguration.addHbaseResources(conf);{code}
> and overwrite any -D property with the properties found in hbase-site.xml
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
