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 August 2026, in the Hadoop category, the mindshare of HPE Data Fabric is 9.8%, down from 14.8% compared to the previous year. The mindshare of Spark SQL is 5.1%, down from 10.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Hadoop Mindshare Distribution
ProductMindshare (%)
HPE Data Fabric9.8%
Spark SQL5.1%
Other85.1%
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

"Our customer purchased a paid support service and so far MapR has addressed our issues well."
"I like the administration part."
"The model creation was very interesting, especially with the libraries provided by the platform."
"The fact that the heavy computation is required on Big Data can be distributed across many nodes in a cluster, makes this solution a winner."
"It is a stable solution...It is a scalable solution."
"My customers find the product cheaper compared to other solutions. The previous solution that we used did not have unified analytics like the runtime or the analog."
"My first choice is MapR, as it is more adaptable to different contexts, and it could be customized in some way to fit the different needs, and this is my first choice and my first advice to people who ask me about this particular platform."
"Outside of human error, MapR is probably the most stable of the major releases."
"The scalability of the solution is good."
"One of Spark SQL's most beautiful features is running parallel queries to go through enormous data."
"It is a stable solution."
"The solution is easy to understand if you have basic knowledge of SQL commands."
"The team members don't have to learn a new language and can implement complex tasks very easily using only SQL."
"This solution is useful to leverage within a distributed ecosystem."
"We use it to gather all the transaction data."
"Data validation and ease of use are the most valuable features."
 

Cons

"The interface part, what I'm calling the integration part, could be improved."
"It would be nice to have new developments in the Apache space (Spark, Storm, etc.)."
"One weakness for MapR is the Kerberos support."
"The product is not user-friendly."
"Upgrading Ezmeral to a new version is a pain. They're trying to make the solution more container-friendly, so I think they're going in the right direction. The only problem we've had in the past was the upgrades. The process isn't smooth due to how the Red Hat operating system upgrades currently work."
"Installations and setups are still a bit cryptic and can be improved."
"The UI for administration still has a lot of manual work to set up the cluster and get it running."
"Having the ability to extend the services provided by the platform to an API architecture, a micro-services architecture, could be very helpful."
"It takes a bit of time to get used to using this solution versus Pandas as it has a steep learning curve."
"It would be useful if Spark SQL integrated with some data visualization tools."
"In terms of improvement, the only thing that could be enhanced is the stability aspect of Spark SQL."
"It would be beneficial for aggregate functions to include a code block or toolbox that explains its calculations or supported conditional statements."
"The solution needs to include graphing capabilities. Including financial charts would help improve everything overall."
"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."
"There should be better integration with other solutions."
 

Pricing and Cost Advice

"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 tool's price is cheap and based on a usage basis. The solution's licensing costs are yearly and there are no extra costs."
"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."
"The solution is bundled with Palantir Foundry at no extra charge."
"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."
"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.
908,800 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
18%
Financial Services Firm
17%
Healthcare Company
10%
Comms Service Provider
8%
Financial Services Firm
22%
University
11%
Comms Service Provider
7%
Healthcare Company
7%
 

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: August 2026.
908,800 professionals have used our research since 2012.