HPE Data Fabric (formerly MapR, acquired by HPE in 2019) is a software-defined datastore and file system that simplifies data management and analytics by unifying data across core, edge, and multicloud sources into a single platform.
N/A
Presto
Score 2.6 out of 10
N/A
Presto is an open source SQL query engine designed to run queries on data stored in Hadoop or in traditional databases.
Teradata supported development of Presto followed the acquisition of Hadapt and Revelytix.
If you need Hadoop and just need raw speed for I/O and have a Hadoop savvy group of engineers who don't need/like web UIs, then MapR is a great fit for you. If you are new to Hadoop or have DevOps folks that are not Hadoop gurus, choosing MapR as your Hadoop vendor will have a steeper learning curve as you will need to do more training and build more admin consoles for them.
Simple stories & templates work nicely - like for our Insider program. Stories that include a lot of images may be challenging to create & have look appealing.
Linking, embedding links and adding images is easy enough.
Once you have become familiar with the interface, Presto becomes very quick & easy to use (but, you have to practice & repeat to know what you are doing - it is not as intuitive as one would hope).
Organizing & design is fairly simple with click & drag parameters.
I think MapR's main problem is name recognition. Hortonworks and Cloudera both are big names in the industry, but their deployment mechanisms are a little more difficult to use, especially when trying to fully automate it's deployment.
Documentation could always be better. But really, if that's your main weakness, it's everybody's weakness.
Presto was not designed for large fact fact joins. This is by design as presto does not leverage disk and used memory for processing which in turn makes it fast.. However, this is a tradeoff..in an ideal world, people would like to use one system for all their use cases, and presto should get exhaustive by solving this problem.
Resource allocation is not similar to YARN and presto has a priority queue based query resource allocation..so a query that takes long takes longer...this might be alleviated by giving some more control back to the user to define priority/override.
UDF Support is not available in presto. You will have to write your own functions..while this is good for performance, it comes at a huge overhead of building exclusively for presto and not being interoperable with other systems like Hive, SparkSQL etc.
Hortonworks and Cloudera are both sort of hacky. We have to do a lot of extra steps to automate those two. MapR has far fewer issues and doesn't force you into a once size fits all deployment scenario. There are multiple ways to deploy and some are more amenable to automation, MapR just has that in spades
I think Presto is one of the best solutions out there today at the cutting edge for interactive query analysis. One of the challenges is presto is a niche tool for the interactive query use case and doesn't have the knobs and whistles as much as Spark. In the foreseeable future if they are able to make presto work without the need for Hive, solving all the gaps it could be game changing and can be a direct threat to spark
