Bitwise offers Hydrograph, a data integration tool with provides ETL functionality on Hadoop and Spark.
N/A
Presto
Score 10.0 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.
N/A
Pricing
Hydrograph
Presto
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Hydrograph
Presto
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Hydrograph
Presto
Features
Hydrograph
Presto
Data Source Connection
Comparison of Data Source Connection features of Product A and Product B
Hydrograph
6.0
1 Ratings
31% below category average
Presto
-
Ratings
Connect to traditional data sources
5.01 Ratings
00 Ratings
Connecto to Big Data and NoSQL
7.01 Ratings
00 Ratings
Data Transformations
Comparison of Data Transformations features of Product A and Product B
Hydrograph
6.5
1 Ratings
21% below category average
Presto
-
Ratings
Simple transformations
5.01 Ratings
00 Ratings
Complex transformations
8.01 Ratings
00 Ratings
Data Modeling
Comparison of Data Modeling features of Product A and Product B
Hydrograph
5.4
1 Ratings
36% below category average
Presto
-
Ratings
Data model creation
7.01 Ratings
00 Ratings
Business rules and workflow
4.01 Ratings
00 Ratings
Collaboration
5.01 Ratings
00 Ratings
Testing and debugging
6.01 Ratings
00 Ratings
Data Governance
Comparison of Data Governance features of Product A and Product B
Presto is for interactive simple queries, where Hive is for reliable processing. If you have a fact-dim join, presto is great..however for fact-fact joins presto is not the solution.. Presto is a great replacement for proprietary technology like Vertica
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.
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.
Presto is good for a templated design appeal. You cannot be too creative via this interface - but, the layout and options make the finalized visual product appealing to customers. The other design products I use are for different purposes and not really comparable to Presto.