...
Building from sources
Checkout sources and switch to sqoop2 branch:
No Format |
---|
$ git clone https://git-wip-us.apache.org/repos/asf/sqoop.git sqoop2
$ cd sqoop2
$ git checkout sqoop2
|
Then , change to Sqoop2 source directory and build themyou can build sqoop using mvn:
No Format |
---|
$ mvn package |
Optionally you can build Sqoop with skipping tests:
...
To install generated binaries on remote server simply copy directory sqoopdirectory sqoop-2.0.0-
SNAPSHOT to SNAPSHOT
to your remote server:
Code Block |
---|
scp -r dist/target/sqoop-2.0.0-SNAPSHOT remote-server.company.org:/remote/path/ |
...
Sqoop server is depending on hadoop binaries, but they are not part of the distribution and thus you need to register install them within into Sqoop server manually. We currently supports only version 2.0, but other version will be added later. To install hadoop libraries execute command addtowar.
sh with sh
with argument -hadoop $version $location
. Following example is for Cloudera distribution version 4(CDH4):
Code Block |
---|
./bin/addtowar.sh -hadoop 2.0 /usr/lib/hadoop/client/ |
...
You can install any arbitrary jars (connectors, JDBC drivers) using -jars
argument that takes list of jars separated by ":". Here is example for installing MySQL jdbc driver into Sqoop server:
...
The logs of the Sqoop2 server and the Derby repository are located as sqoop.log
and derbyrepo.log
(by default unless changed by the above configuration), respectively, under the
(LOGS)
directory in the Sqoop2 distribution directory.