Apache Drill vs. SAP Vora

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

I spent more than 1 year with SAP Vora, SAP Datahub and SAP Leonardo with ML, iOt. I believe this product has potential but it is not easy to adopt. SAP has to keep in mind how open-source big data technologies are able to deliver quick results. I know SAP is stabilizing and fighting hard against many open source technologies, but it still has a long way to go there.

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

• Modelling with SAP HANA and Hadoop
• Realtime Analysis using Vora and HANA as a Streaming engine
• Time series Analysis on large chunks of datasets
• Machine learning capabilities on Hadoop tables and spark contexts

Incentivized

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

Incentivized

• Vora 2.0 in on premise scenarios could be improved, as adoption of the cloud is not an easy sell.
• Kubernetes and Docker integration need to be more seamless and quick to understand. If this is simplified, it will be easy to adopt
• Data hub orchestration and integrations could be simplified so that quick adoption within SAP BW, ECC, S4 HANa scenarios is possible.

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

• 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

• Negative impact would be Poc and RFI will need more time to adopt and decision making gets delayed
• Positive impact would be it's a great leap from SAP to adopt a Big data technologies and AI within cloud stream. But selling is going to take time.

Incentivized