How Does Impala Compare To Hive And Pig?

1.	How Does Impala Compare To Hive And Pig?
Answer» Impala is different from Hive and Pig because it uses its own daemons that are SPREAD across the cluster for queries. Because Impala does not rely on MAPREDUCE, it AVOIDS the startup overhead of MapReduce jobs, allowing Impala to RETURN results in real time. Impala is different from Hive and Pig because it uses its own daemons that are spread across the cluster for queries. Because Impala does not rely on MapReduce, it avoids the startup overhead of MapReduce jobs, allowing Impala to return results in real time.

Answer»

Impala is different from Hive and Pig because it uses its own daemons that are SPREAD across the cluster for queries. Because Impala does not rely on MAPREDUCE, it AVOIDS the startup overhead of MapReduce jobs, allowing Impala to RETURN results in real time.

Impala is different from Hive and Pig because it uses its own daemons that are spread across the cluster for queries. Because Impala does not rely on MapReduce, it avoids the startup overhead of MapReduce jobs, allowing Impala to return results in real time.

Discussion

No Comment Found

Related InterviewSolutions

What Kinds Of Impala Queries Or Data Are Best Suited For Hbase?
Can I Do Insert ... Select * Into A Partitioned Table?
How Do I Load A Big Csv File Into A Partitioned Table?
Is There A Dual Table?
Why Is Space Not Freed Up When I Issue Drop Table?
Why Do I Have To Use Refresh And Invalidate Metadata, What Do They Do?
Can Impala Do User-defined Functions (udfs)?
Is There An Update Statement?
When Does Impala Hold On To Or Return Memory?
What Are The Most Memory-intensive Operations?