No more typing reviews! Try our Samantha, our new voice AI agent.

Cloudera Distribution for Hadoop vs Spark SQL comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Cloudera Distribution for H...
Ranking in Hadoop
2nd
Average Rating
8.0
Reviews Sentiment
6.3
Number of Reviews
51
Ranking in other categories
NoSQL Databases (11th)
Spark SQL
Ranking in Hadoop
4th
Average Rating
7.8
Reviews Sentiment
7.6
Number of Reviews
15
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of November 2026, in the Hadoop category, the mindshare of Cloudera Distribution for Hadoop is 14.6%, down from 19.0% compared to the previous year. The mindshare of Spark SQL is 5.3%, down from 7.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Hadoop Mindshare Distribution
ProductMindshare (%)
Cloudera Distribution for Hadoop14.6%
Spark SQL5.3%
Other80.1%
Hadoop
 

Featured Reviews

Rok Dolinsek - PeerSpot reviewer
Manager, Bussines Development & Co Owner at Troia d.o.o.
Enables on-premise implementation with powerful data processing capabilities
This is the only solution that is possible to install on-premise. Cloudera provides a hybrid solution that combines compute on cloud or on-premises. It includes all machine learning algorithms in the Spark machine learning library. All functionalities needed for a big data platform and ETL are on the platform, eliminating the need for other tools. It is scalable, ready for vertical scaling, and very powerful, offering numerous functionalities and configurations for generative AI.
Kemal Duman - PeerSpot reviewer
Team Lead, Data Engineering at Nesine.com
Data pipelines have run faster and support flexible batch and streaming transformations
We do not have any performance problems, but we do have some resource problems. Spark SQL consumes so many resources that we migrated our streaming job from Spark to Apache Flink. Resource management in Spark SQL should be better. It consumes more resources, which is normal. The main reason we switched from Spark is memory and CPU consumption. The major reason is the resource problem because the number of streaming jobs has been increasing in our company. That is why we considered resource management as a priority. Because of the resource consumption, I would say the development of Spark SQL is better. For development purposes, it is a top product and not difficult to work with, but resources are the major problem. We changed to Flink regardless of development time. Development time is less in Spark compared with Flink.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The tool can be deployed using different container technologies, which makes it very scalable."
"The solution is reliable and stable, it fits our requirements."
"Implementing a Hadoop cluster has become relatively straight-forward using CDH."
"We were able to utilize data which was untapped previously."
"The data science aspect of the solution is valuable."
"It is helpful to gather and process data."
"The main advantage is the storage is less expensive."
"The search function is the most valuable aspect of the solution."
"Certain data sets that are very large are very difficult to process with Pandas and Python libraries. Spark SQL has helped us a lot with that."
"Overall the solution is excellent."
"We use it to gather all the transaction data."
"It is a stable solution."
"Data validation and ease of use are the most valuable features."
"The team members don't have to learn a new language and can implement complex tasks very easily using only SQL."
"One of Spark SQL's most beautiful features is running parallel queries to go through enormous data."
"The solution is easy to understand if you have basic knowledge of SQL commands."
 

Cons

"The initial setup of Cloudera is difficult."
"There are multiple bugs when we update."
"Cloudera's support is extremely bad and cannot be relied on."
"There are better solutions out there that have more features than this one."
"Cloudera 5 is currently very unstable. Between two Cloudera 5 clusters, we have an incident at least twice a week due to what are now outstanding bugs."
"It is quite complicated to configure and install. Integrating the platform into an information system is always a challenge, especially when starting with on-premise implementation."
"The areas of improvement depend on the scale of the project. For banking customers, security features and an essential budget for commercial licenses would be the top priority. Data regulation could be the most crucial for a project with extensive data or an extra use case."
"It has compatibility issues if installed in specialized hardware such as EMC Isilon or if node manager and data nodes are not co-located."
"Being a new user, I am not able to find out how to partition it correctly. I probably need more information or knowledge. In other database solutions, you can easily optimize all partitions. I haven't found a quicker way to do that in Spark SQL. It would be good if you don't need a partition here, and the system automatically partitions in the best way. They can also provide more educational resources for new users."
"The initial setup is a bit complex."
"The solution needs to include graphing capabilities. Including financial charts would help improve everything overall."
"There are many inconsistencies in syntax for the different querying tasks like selecting columns and joining between two tables so I'd like to see a more consistent syntax."
"There should be better integration with other solutions."
"In the next update, we'd like to see better performance for small points of data. It is possible but there are better tools that are faster and cheaper."
"It would be useful if Spark SQL integrated with some data visualization tools."
"Being a new user, I am not able to find out how to partition it correctly."
 

Pricing and Cost Advice

"I haven't bought a license for this solution. I'm only using the Apache license version."
"The price is very high. The solution is expensive."
"I believe we pay for a three-year license."
"The tool is expensive...For the SMB market or customers whose environments are not that complex and do not have multiple systems running, Cloudera might not be a good option."
"Cloudera requires a license to use."
"Cloudera Distribution for Hadoop is expensive, with support costs involved."
"The product’s price depends from project to project."
"It is an expensive product."
"We use the open-source version, so we do not have direct support from Apache."
"There is no license or subscription for this solution."
"The on-premise solution is quite expensive in terms of hardware, setting up the cluster, memory, hardware and resources. It depends on the use case, but in our case with a shared cluster which is quite large, it is quite expensive."
"The solution is open-sourced and free."
"The solution is bundled with Palantir Foundry at no extra charge."
"We don't have to pay for licenses with this solution because we are working in a small market, and we rely on open-source because the budgets of projects are very small."
report
Use our free recommendation engine to learn which Hadoop solutions are best for your needs.
922,528 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Outsourcing Company
11%
Construction Company
9%
Manufacturing Company
9%
Financial Services Firm
15%
Comms Service Provider
11%
Manufacturing Company
11%
University
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business16
Midsize Enterprise9
Large Enterprise32
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise6
Large Enterprise4
 

Questions from the Community

What is your experience regarding pricing and costs for Cloudera Distribution for Hadoop?
The price for Cloudera is average, yet it is very good compared to other solutions. It can be deployed on-premises, unlike competitors' cloud-only solutions.
What needs improvement with Cloudera Distribution for Hadoop?
If they could support modifying the data more easily than the current implementation, it would be beneficial.
What is your primary use case for Cloudera Distribution for Hadoop?
We use Cloudera Distribution for Hadoop for many use cases including analytics, storing huge data sets, and various data processing tasks.
What needs improvement with Spark SQL?
We do not have any performance problems, but we do have some resource problems. Spark SQL consumes so many resources that we migrated our streaming job from Spark to Apache Flink. Resource manageme...
What is your primary use case for Spark SQL?
Spark SQL has been in our stack for less than one year, though some of our colleagues are using it. It is a useful product for transformation jobs. We generally use Spark SQL for batch processing. ...
What advice do you have for others considering Spark SQL?
Regarding the Catalyst query optimizer, I think we are using it. We were using it in the past, but I am not certain if we use it now. We used it a long time ago. I rate my experience with Spark SQL...
 

Overview

 

Sample Customers

37signals, Adconion,adgooroo, Aggregate Knowledge, AMD, Apollo Group, Blackberry, Box, BT, CSC
UC Berkeley AMPLab, Amazon, Alibaba Taobao, Kenshoo, Hitachi Solutions
Find out what your peers are saying about Cloudera Distribution for Hadoop vs. Spark SQL and other solutions. Updated: November 2026.
922,528 professionals have used our research since 2012.