Apache Drill vs. Kognitio

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

What you have are different strategies for data encoding, which makes the process quite flexible, it is perfectly done so that a joint and collaborative work can be carried out, this information analyzed in large quantities, is extremely vital for the company, by giving it the correct and timely reading

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

• Ultra fast query results.
• IN Memory Database.
• Easy integration to reporting services.

Incentivized

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

Incentivized

• Problems Could Be Encountered is particularly pronounced in more complex analyses.
• Categorical variables are often not precise enough

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

We selected Kognitio because of the legacy systems that are still running. Also, we have legacy systems in place that are fit for Kognitio. End-user has good feedback on our side when we started implementing this solution. Current servers are compatible with Kognitio in place.

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

• The implementation of the formats to integrate the users we have and the program is also good.
• I also improve the control of aspects related to the work environment

Incentivized