Apache Pig vs Oracle Data Warehouse

• 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.

Read full review

• Able to handle very large data sizes efficiently from a performance, high availability and manageability perspective. This is accomplished through the Oracle Partitioning functionality. Partitioning allows large segments (tables, IOT index-organized tables, indexes) to be broken into smaller segments at the physical layer but treated as a whole at the logical layer.
• Provides support for dual-format architecture through Oracle In-Memory functionality. Without any change to application code one can obtain in-memory performance. This functionality enables us to have the tables represented in both the row format and the column format using in-memory format. This is a huge boost for BI/analytic queries since the Oracle optimizer is able to intelligently choose the appropriate format.
• Provision to materialize a subset of table data or table joins. This is through materialized views and the optimizer will rewrite the query against the base tables to make use of this materialized view. This provides a huge performance boost and is critical in VLDBs as in a data warehouse. The query rewrite is fully transparent to users.
• Provides multiple compression capabilities. This is very useful not only for deducing the storage foot print but as well as increase performance at different layers of the infrastructure including query performance. The compression functionality can be applied against both structured and unstructured data.
• With the advent of Engineered Systems (Exadata, Database Machine, SuperCluster) there are specific features and functionalities that can further boost the Oracle data warehouse. These are related to consolidation, Smart Scan, Storage Indexes, EHCC (Exadata hybrid columnar compression) and much more.
• RAC - Real Application Clusters (with 2 or more nodes) provides functionality for high availability, performance and scaling as the work load increases. The parallelism is provided both within a node and as well as across nodes. If for any reason a node goes down the data warehouse is still available through other nodes and the running queries are transparently failed over to the surviving nodes.

Read full review

• 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.

Read full review

• Customer support isn't the best out there. We usually have to wait about an hour to get some form of assistance.
• Pricing is a bit higher than many of its competitors such as AWS Redshift.
• Tweaking features requires dedicated staff. Software is fairly advanced. Would be difficult to use for newcomers.

Read full review

• 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.

Read full review

• Very cost effective for large databases.
• Very fast results on simple queries.
• Analytical functionalities are of wide range, which makes it very cost effective.
• For smaller businesses, it might be a great asset.
• Some features are supposed to be bought separately, so one needs to consider this before licensing with Oracle DW.

Read full review