Processing High Volume Updates in Hive
summary
A production solution handles 1 TB/day with 15% updates by keeping a base file per bucket and storing edits as separate HDFS files, then using a custom record reader that merges sorted base and edit streams at read time to synthesize current rows. It requires sorting on the primary key, consistent bucketing, compaction scheduled off-peak, and a cut‑off timestamp for repeatable reads. Prototype scales in daily tests but needs compaction tooling and fixes for Hive I/O quirks before wider release.
AI-written summary · about
chapters (5)
- 0:00Start
- 5:27Hive Table Layout
- 9:47Stitching Buckets Together
- 11:00Limitations
- 12:02Additional Challenges from Hive
related talks
20mMin and Max Aggregations with Updates in Real Time
48mContinuous Optimization for distributed BigData analysis
31mBuilding large scale, transactional data lakes with Apache Hudi
43mChange data capture in production with Apache Flink
50mApache Hudi : The Data Lake Platform
42mApache Hive Replication V3
01h 03mThe Future of Apache Hive and Hadoop 2.0: Bigger, Faster, Stronger
23mHadoop & Cloud Storage: Object Store Integration in Production
