Overall Satisfaction with Apache Drill
Apache Drill was being used initially to evaluate running queries on data stored in multiple data stores (hDFS, postgres, cassandra). We were testing it out, over the use of PrestoDB. But saw that Drill also supported HBASE and other engines. it was from that aspect, used Drill to query data across the multiple datasources, as more ec2 instances were created, since some of the data was also stored in s3.
- 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
- deployment. Not as easy
- configuration isn't as straight forward, especially with the documentation
- Garbage collection could be improved upon
- 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).
- prestodb, impala and apache phoenix
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
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