Apache Drill vs. Apache Pig

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

Apache Pig is best suited for ETL-based data processes. It is good in performance in handling and analyzing a large amount of data. it gives faster results than any other similar tool. It is easy to implement and any user with some initial training or some prior SQL knowledge can work on it. Apache Pig is proud to have a large community base globally.

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

• Its performance, ease of use, and simplicity in learning and deployment.
• Using this tool, we can quickly analyze large amounts of data.
• It's adequate for map-reducing large datasets and fully abstracted MapReduce.

Incentivized

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

Incentivized

• UDFS Python errors are not interpretable. Developer struggles for a very very long time if he/she gets these errors.
• Being in early stage, it still has a small community for help in related matters.
• It needs a lot of improvements yet. Only recently they added datetime module for time series, which is a very basic requirement.

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

It is quick, fast and easy to implement Apache Pig which makes is quite popular to be used.

Incentivized

The documentation is adequate. I'm not sure how large of an external community there is for support.

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

Apache Pig might help to start things faster at first and it was one of the best tool years back but it lacks important features that are needed in the data engineering world right now. Pig also has a steeper learning curve since it uses a proprietary language compared to Spark which can be coded with Python, Java.

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

• Higher learning curve than other similar technologies so on-boarding new engineers or change ownership of Apache Pig code tends to be a bit of a headache
• Once the language is learned and understood it can be relatively straightforward to write simple Pig scripts so development can go relatively quickly with a skilled team
• As distributed technologies grow and improve, overall Apache Pig feels left in the dust and is more legacy code to support than something to actively develop with.

Incentivized