Apache Sqoop vs. Cloudera Manager

Sqoop is great for sending data between a JDBC compliant database and a Hadoop environment. Sqoop is built for those who need a few simple CLI options to import a selection of database tables into Hadoop, do large dataset analysis that could not commonly be done with that database system due to resource constraints, then export the results back into that database (or another). Sqoop falls short when there needs to be some extra, customized processing between database extract, and Hadoop loading, in which case Apache Spark's JDBC utilities might be preferred

Incentivized

Cloudera Manager is well suited for environments and deployments where the administrator user base is not well versed in the Apache Hadoop ecosystem or the Linux command line interface.

Incentivized

• Provides generalized JDBC extensions to migrate data between most database systems
• Generates Java classes upon reading database records for use in other code utilizing Hadoop's client libraries
• Allows for both import and export features

Incentivized

• Cloudera Manager has an easy to use web GUI. You can start and stop cluster and services. It will start and stop services in a cluster in the right order. You can monitor the cluster, services, and physical host hardware as well.
• Cloudera Manager has an easy to use API that allows us to create scripts to automate deployment process.
• Cloudera Manager has an option to add additional services that you could manage via the web GUI.

Incentivized

• Sqoop2 development seems to have stalled. I have set it up outside of a Cloudera CDH installation, and I actually prefer it's "Sqoop Server" model better than just the CLI client version that is Sqoop1. This works especially well in a microservices environment, where there would be only one place to maintain the JDBC drivers to use for Sqoop.

Incentivized

• Support for third-party Python APIs within Cloudera Manager extension framework
• Providing more reporting/logging functionality as part of the open source distribution
• Support for the latest RHEL versions sooner in the release lifecycle

Incentivized

It meets all my customer's needs.

Incentivized

• Sqoop comes preinstalled on the major Hadoop vendor distributions as the recommended product to import data from relational databases. The ability to extend it with additional JDBC drivers makes it very flexible for the environment it is installed within.
• Spark also has a useful JDBC reader, and can manipulate data in more ways than Sqoop, and also upload to many other systems than just Hadoop.
• Kafka Connect JDBC is more for streaming database updates using tools such as Oracle GoldenGate or Debezium.
• Streamsets and Apache NiFi both provide a more "flow based programming" approach to graphically laying out connectors between various systems, including JDBC and Hadoop.

Incentivized

I have not used any competitors, such as Hortonworks, because Cloudera Manager just works and meets all my customer's needs. I only have deployed Hadoop using command line, which is not easy to use and manage.

Incentivized

• When combined with Cloudera's HUE, it can enable non-technical users to easily import relational data into Hadoop.
• Being able to manipulate large datasets in Hadoop, and them load them into a type of "materialized view" in an external database system has yielded great insights into the Hadoop datalake without continuously running large batch jobs.
• Sqoop isn't very user-friendly for those uncomfortable with a CLI.

Incentivized

• Cloudera Manager has allowed our organization to deploy Apache Hadoop to operations quicker and with less training versus using the command line exclusively.
• Increased employee efficiency.
• Increased product adoption.

Incentivized