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

HPE Data Fabric vs Spark SQL comparison

 

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

HPE Data Fabric
Ranking in Hadoop
4th
Average Rating
8.0
Reviews Sentiment
6.1
Number of Reviews
12
Ranking in other categories
No ranking in other categories
Spark SQL
Ranking in Hadoop
5th
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 May 2026, in the Hadoop category, the mindshare of HPE Data Fabric is 10.5%, down from 15.2% compared to the previous year. The mindshare of Spark SQL is 5.3%, down from 10.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Hadoop Mindshare Distribution
ProductMindshare (%)
HPE Data Fabric10.5%
Spark SQL5.3%
Other84.2%
Hadoop
 

Featured Reviews

Hamid M. Hamid - PeerSpot reviewer
Data architect at Banking Sector
A stable and scalable tool that serves as a great database
The initial setup of HPE Ezmeral Data Fabric is easy. I am not sure how long it took to deploy HPE Ezmeral Data Fabric, but I haven't heard about any disadvantages when it comes to the time taken for the deployment. I remember that one of our company's clients who had purchased the product never mentioned the product's setup phase being complex. One of the drawbacks with HPE Ezmeral Data Fabric stems from the fact that the product's upgrade was not straightforward, and it was a complex process since one of the teams in my company who deals with the tool found the upgrade part to be tough. The solution is deployed on an on-premises model. My company has two dedicated staff members to look after the deployment and maintenance phases of HPE Ezmeral Data Fabric.
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

"I highly recommend MapR."
"MapR is a great distribution, although I have limited experience with other distributors."
"I like the administration part."
"Initial setup is rather straightforward thanks to detailed documentation covering all the bases."
"This product enabled us opening up endless possibilities in data analytics, IOE/IOT, and predictive analysis."
"HPE Ezmeral Data Fabric can be accessed from any namespace globally as you would access it from a machine using an NFS."
"The model creation was very interesting, especially with the libraries provided by the platform."
"It is a stable solution...It is a scalable solution."
"We use it to gather all the transaction data."
"The scalability of the solution is good."
"Spark SQL gives us a handful of methods to design queries based on its own syntax and also incorporates the regular SQL syntax within tasks."
"This solution is a much more scalable and adventurous solution."
"The performance is one of the most important features, and it has an API to process the data in a functional manner."
"Data validation and ease of use are the most valuable features."
"The stability was fine. It behaved as expected."
"The solution is easy to understand if you have basic knowledge of SQL commands."
 

Cons

"Installations and setups are still a bit cryptic and can be improved."
"The product is not user-friendly."
"It'd like to see file system auditing, data encryption, and certification of other vendors' tools."
"The interface part, what I'm calling the integration part, could be improved."
"The UI for administration still has a lot of manual work to set up the cluster and get it running."
"I'd say we've had issues with pricing."
"It would be nice to have new developments in the Apache space (Spark, Storm, etc.)."
"The biggest drawback is that it has vendor locking."
"In the next release, maybe the visualization of some command-line features could be added."
"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."
"Being a new user, I am not able to find out how to partition it correctly."
"This solution could be improved by adding monitoring and integration for the EMR."
"SparkUI could have more advanced versions of the performance and the queries and all."
"I've experienced some incompatibilities when using the Delta Lake format."
"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."
"Spark SQL consumes so many resources that we migrated our streaming job from Spark to Apache Flink."
 

Pricing and Cost Advice

"The tool's price is cheap and based on a usage basis. The solution's licensing costs are yearly and there are no extra costs."
"There is a need for my company to pay for the licensing costs of the solution."
"HPE is flexible with you if you are an existing customer. They offer different models that might be beneficial for your organization. It all depends on how you negotiate."
"The solution is open-sourced and free."
"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 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."
"There is no license or subscription for this solution."
"We use the open-source version, so we do not have direct support from Apache."
report
Use our free recommendation engine to learn which Hadoop solutions are best for your needs.
893,221 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Construction Company
11%
Comms Service Provider
9%
Healthcare Company
9%
Financial Services Firm
20%
University
12%
Retailer
11%
Healthcare Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business4
Large Enterprise7
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise6
Large Enterprise4
 

Questions from the Community

Ask a question
Earn 20 points
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...
 

Also Known As

MapR, MapR Data Platform
No data available
 

Overview

 

Sample Customers

Valence Health, Goodgame Studios, Pico, Terbium Labs, sovrn, Harte Hanks, Quantium, Razorsight, Novartis, Experian, Dentsu ix, Pontis Transitions, DataSong, Return Path, RAPP, HP
UC Berkeley AMPLab, Amazon, Alibaba Taobao, Kenshoo, Hitachi Solutions
Find out what your peers are saying about HPE Data Fabric vs. Spark SQL and other solutions. Updated: April 2026.
893,221 professionals have used our research since 2012.