Analysts only need a straightforward group-by on already-cataloged Hive tables of recycling-tonnage facts. What is the better abstraction choice?
Select an answer to reveal the explanation.
Short Explanation
If Hive already speaks group-by over the recycling tables, don't carve the same answer in low-level MapReduce stone. Use the higher abstraction when it fits. Laptops' localStorage is not a warehouse.
Full Explanation
Choosing the right abstraction level is part of BDPC judgment: simple aggregations on cataloged tables are often best expressed in Hive (or similar) instead of hand-written MapReduce. Raw MR remains valuable for custom logic Hive cannot express cleanly. Client-side browser storage is not an analytics platform for citywide tonnage facts.