In the Hive application of FusionInsight HD, there are scenarios where the data storage file has a high compression efficiency, and most queries only involve a part of the file field. This scenario…

Question

Options

• ATrue
• BFalse

• A
  74% (23)
• B
  26% (8)

Explanation

ORC (Optimized Row Columnar) File format is purpose-built for exactly this scenario: it stores data in a columnar layout, enabling high compression ratios because values of the same data type are stored together, and it supports column pruning, meaning queries that reference only a subset of fields skip unneeded columns entirely without reading them from disk. This combination of efficient compression and selective field access makes ORC the optimal choice in FusionInsight HD (Huawei's Hadoop distribution) when data files are large and queries are column-selective. Option B is incorrect because claiming ORC is unsuitable contradicts its core design goals - row-based formats like TextFile or SequenceFile would actually be the poor fit here, as they must read entire rows even when only a few fields are needed. Memory tip: Think of ORC as "Only Read Columns" - its columnar storage means you compress better (similar types cluster together) and query faster (skip irrelevant columns), making it the go-to format whenever you see "high compression + partial field queries" in a Hive scenario question.

No community discussion yet for this question.