A parks department proposes putting live festival ticket checkout—inventory locks, payments, and immediate confirmations—on Hive tables in HDFS. What is the sound judgment?
Select an answer to reveal the explanation.
Short Explanation
Hive is a research library for big history books, not the cash register selling today's tickets. Live checkout needs an OLTP system with fast transactional semantics. Keep Hive for analytics after the sales land in the lake.
Full Explanation
Hive is designed for analytical SQL-like access to large Hadoop datasets, typically with higher latency and batch-oriented execution. Point-of-sale style checkout requires transactional OLTP guarantees Hive does not provide as a primary store. Rejecting the proposal protects civic payments; the issue is workload mismatch, not an inability of MapReduce to count keys in analytics jobs.