Apache Drill vs. Cloudera Distribution Hadoop (CDH)

if you're doing joins from hBASE, hdfs, cassandra and redis, then this works. Using it as a be all end all does not suit it. This is not your straight forward magic software that works for all scenarios. One needs to determine the use case to see if Apache Drill fits the needs. 3/4 of the time, usually it does.

Incentivized

Cloudera Distribution Hadoop (CDH) does a lot of things really well - especially on the analytical front. That being said the product is quite expensive. There are seemingly numerous applications that do the same thing on the functional level that are much more cost effecient for enterprise teams. If I were recommending this to a colleague I would let them know the product will absolutely be able to get the job done for their use case, but there are more efficient options

Incentivized

• queries multiple data sources with ease.
• supports sql, so non technical users who know sql, can run query sets
• 3rd party tools, like tableau, zoom data and looker were able to connect with no issues

Incentivized

• Solid and robust set of integrations
• Easy to use and easy to deploy across the enterprise
• Reliability - never lost any info
• Simple and clean interface

Incentivized

• deployment. Not as easy
• configuration isn't as straight forward, especially with the documentation
• Garbage collection could be improved upon

Incentivized

• The price is quite high competitively speaking
• Hard to learn more robust functions and custom options without experience

Incentivized

if Presto comes up with more support (ie hbase, s3), then its strongly possible that we'll move from apache drill to prestoDB. However, Apache drill needs more configuration ease, especially when it comes to garbage collection tuning. If apache drill could support also sparkSQL and Flume, then it does change drill into being something more valuable than prestoDB

Incentivized

compared to presto, has more support than prestodb. Impala has limitations to what drill can support apache phoenix only supports for hbase. no support for cassandra. Apache drill was chosen, because of the multiple data stores that it supports htat the other 3 do not support. Presto does not support hbase as of yet. Impala does not support query to cassandra

Incentivized

In terms of functionality there's not much difference, both get the job done. Amazon was more cost-efficient for our team, but this could vary depending on the size of the business. One thing I did notice was that Cloudera seemed to management and spit out our deployments faster than AWS.

Incentivized

• Configuration has taken some serious time out.
• Garbage collection tuning. is a constant hassle. time and effort applied to it, vs dedicating resources elsewhere.
• w/ sql support, reduces the need of devs to generate the resultset for analysts, when they can run queries themselves (if they know sql).

Incentivized

• Saves time by automating typically manual processes (data management, lifecyle AI etc)
• Quick deployments and analytics allow for faster time-to-value

Incentivized