This is the documentation for CDH 5.1.x. Documentation for other versions is available at Cloudera Documentation.

Feature Differences - Sqoop 1 and Sqoop 2

  Note:

Moving from Sqoop 1 to Sqoop 2: Sqoop 2 is essentially the future of the Apache Sqoop project. However, since Sqoop 2 currently lacks some of the features of Sqoop 1, Cloudera recommends you use Sqoop 2 only if it contains all the features required for your use case, otherwise, continue to use Sqoop 1.

Feature Sqoop 1 Sqoop 2
Connectors for all major RDBMS Supported.

Not supported.

Workaround: Use the generic JDBC Connector which has been tested on the following databases: Microsoft SQL Server, PostgreSQL, MySQL and Oracle.

This connector should work on any other JDBC compliant database. However, performance might not be comparable to that of specialized connectors in Sqoop.
Kerberos Security Integration Supported.

Not supported.
Encryption of Stored Passwords Not supported. No workaround. Supported using Derby's on-disk encryption.

Disclaimer: Although expected to work in the current version of Sqoop 2, this configuration has not been verified.

Data transfer from RDBMS to Hive or HBase Supported.

Not supported.

Workaround: Follow this two-step approach.
  1. Import data from RDBMS into HDFS
  2. Load data into Hive or HBase manually using appropriate tools and commands such as the LOAD DATA statement in Hive
Data transfer from Hive or HBase to RDBMS Not supported.
Workaround: Follow this two-step approach.
  1. Extract data from Hive or HBase into HDFS (either as a text or Avro file)
  2. Use Sqoop to export output of previous step to RDBMS

Not supported.

Follow the same workaround as for Sqoop 1.
Page generated September 3, 2015.