Databases Reference
In-Depth Information
false
. The second option is to force Sqoop to generate a different schema by mapping
all
DATE
columns into
String
as OraOop expects.
7.11. Choosing the Proper Connector for Oracle
Problem
You are not sure when to use OraOop, the built-in Oracle connector, or the Generic
JDBC Connector.
Solution
For the best performance, use the OraOop connector. If OraOop does not work for your
use case, the next best alternative is the built-in connector. If those two connectors do
not work in your environment, your last resort is the Generic JDBC Connector.
The Generic JDBC Connector is slower than even the built-in Oracle
Connector.
Discussion
There are three connectors available for use when you need to transfer data to or from
the Oracle database: the Generic JDBC Connector, the built-in Oracle connector, and
OraOop. The Generic JDBC Connector and the built-in Oracle connector are bundled
within Sqoop, and you can use them out of the box. OraOop is not distributed with
Sqoop, and you would need to manually download and install it.
The JDBC driver is a dependency for all three connectors. You will always need to install
the JDBC driver. Sqoop will automatically try to use the most optimal connector avail‐
able, so OraOop will be used automatically when it's installed. If you need to condi‐
tionally disable OraOop on a per-job basis, you can set the property
oraoop.dis
abled
to
true
. For example, use the following command to disable OraOop after it's
been installed:
sqoop import
\
-Doraoop.disabled
=
true
\
--connect jdbc:oracle:thin:@oracle.example.com:1521/ORACLE
\
--username SQOOP
\
--password sqoop
\
--table cities
If you would prefer to explicitly choose which connector will be used rather than the
implicit selection, you can do that using the following set of parameters.
