Feature Differences - Sqoop 1 and Sqoop 2
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.
|
Data transfer from Hive or HBase to RDBMS | Not supported. Workaround: Follow this two-step approach.
|
Not supported. Follow the same workaround as for Sqoop 1. |
<< Viewing the Sqoop 2 Documentation | Whirr Installation >> | |