Hive query optimization in Hadoop - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main goal of Hive query optimization?

The main goal is to make Hive queries run faster and use fewer resources by improving how data is processed and accessed.

beginner

Explain what partitioning means in Hive.

Partitioning divides a large table into smaller parts based on a column, like splitting sales data by year. This helps Hive read only the needed parts, speeding up queries.

intermediate

What is bucketing in Hive and how does it help optimization?

Bucketing splits data into a fixed number of files (buckets) based on a hash of a column. It helps by making joins and sampling faster because data is organized predictably.

intermediate

How does predicate pushdown improve Hive query performance?

Predicate pushdown means filtering data early, close to where it is stored, so less data moves around. This reduces the amount of data Hive processes and speeds up queries.

beginner

Why is using ORC or Parquet file formats recommended for Hive optimization?

ORC and Parquet store data in a columnar way, which means Hive reads only the columns needed. They also support compression and indexing, making queries faster and saving storage.

What does partitioning in Hive help with?

A Reading only relevant parts of data

B Compressing data files

C Encrypting data for security

D Changing data types automatically

Partitioning splits data so Hive reads only the needed parts, improving query speed.

Which file format is best for columnar storage in Hive?

A CSV

B JSON

C TXT

D ORC

ORC is a columnar format that helps Hive read only needed columns, speeding up queries.

What is bucketing used for in Hive?

A Splitting data into fixed files for faster joins

B Encrypting data buckets

C Backing up data automatically

D Changing data schema

Bucketing organizes data into fixed files to optimize joins and sampling.

Predicate pushdown helps Hive by:

A Changing data format

B Increasing data size

C Filtering data early to reduce processing

D Sorting data alphabetically

Filtering data close to storage reduces the amount Hive processes, speeding queries.

Which of these is NOT a Hive optimization technique?

A Partitioning

B Adding random delays

C Bucketing

D Using ORC format

Adding random delays does not optimize Hive queries.

Describe three ways Hive query optimization can improve query speed and resource use.

Think about how data is organized and filtered.

Explain how using ORC or Parquet file formats helps Hive process data more efficiently.

Focus on how data is stored and accessed.

Practice

1. What is the main purpose of Hive query optimization?

easy

A. To increase the size of data stored in Hive

B. To make data queries faster and reduce resource usage

C. To make Hive queries more complex

D. To disable partitioning in Hive tables

Solution

1. Step 1: Understand Hive query optimization goal

   Hive query optimization aims to improve query speed and reduce resource consumption.

2. Step 2: Evaluate options based on this goal

   Only To make data queries faster and reduce resource usage matches the goal of faster queries and less resource use.

3. Final Answer:

   To make data queries faster and reduce resource usage -> Option B

4. Quick Check:

   Optimization = Faster queries [OK]

Hint: Optimization means faster queries and less cost [OK]

Common Mistakes:

• Thinking optimization increases data size
• Confusing optimization with query complexity
• Ignoring resource usage benefits

2. Which of the following is the correct syntax to enable cost-based optimization (CBO) in Hive?

easy

A. ACTIVATE hive.cbo = 1;

B. ENABLE hive.cbo = true;

C. SET hive.cbo.enable=true;

D. SET hive.cob.enable = yes;

Solution

1. Step 1: Recall correct Hive syntax for setting properties

   Hive uses 'SET property=value;' to configure settings.

2. Step 2: Identify correct property name and value

   The correct property is 'hive.cbo.enable' and value is 'true'. SET hive.cbo.enable=true; matches this exactly.

3. Final Answer:

   SET hive.cbo.enable=true; -> Option C

4. Quick Check:

   SET + hive.cbo.enable=true [OK]

Hint: Use SET with exact property name and true/false [OK]

Common Mistakes:

• Misspelling property name
• Using ENABLE or ACTIVATE instead of SET
• Using yes/no instead of true/false

3. Given the Hive query:
SELECT * FROM sales WHERE year = 2023 AND region = 'US';
Assuming the table is partitioned by year and bucketed by region, what is the main optimization benefit?

medium

A. Hive reads only data for year 2023 and region 'US' buckets

B. Hive scans the entire table ignoring partitions and buckets

C. Hive reads only the region 'US' partition

D. Hive reads only the year 2023 bucket

Solution

1. Step 1: Understand partitioning and bucketing roles

   Partitioning by year means data is divided by year folders; bucketing by region means data is split into files by region.

2. Step 2: Analyze query filter impact

   Filtering on year=2023 uses partition pruning; filtering on region='US' uses bucket pruning.

3. Final Answer:

   Hive reads only data for year 2023 and region 'US' buckets -> Option A

4. Quick Check:

   Partition + bucket pruning = less data read [OK]

Hint: Partition filters reduce folders; bucket filters reduce files [OK]

Common Mistakes:

• Confusing partition with bucket filtering
• Assuming full table scan despite filters
• Mixing partition and bucket roles

4. Identify the error in this Hive query optimization setting:
SET hive.cbo.enable = 'true';

medium

A. SET command cannot be used for this property

B. Property name is incorrect

C. Missing semicolon at end

D. Value should not be in quotes

Solution

1. Step 1: Check correct syntax for SET command

   Hive SET commands use format: SET property=value; without quotes around boolean values.

2. Step 2: Identify issue with quotes around 'true'

   Putting 'true' in quotes makes it a string, which Hive does not accept for boolean properties.

3. Final Answer:

   Value should not be in quotes -> Option D

4. Quick Check:

   Boolean values no quotes [OK]

Hint: Boolean values in SET must be unquoted true/false [OK]

Common Mistakes:

• Adding quotes around boolean values
• Confusing property name spelling
• Omitting semicolon (optional but recommended)

5. You have a large Hive table with sales data partitioned by year and month. You want to optimize a query filtering on year=2023 only. Which approach will improve query performance the most?

hard

A. Add bucketing on month and enable cost-based optimization

B. Drop the month partition and keep only year

C. Disable partition pruning to scan all data

D. Use SELECT * without WHERE clause

Solution

1. Step 1: Understand current partitioning and query filter

   The table is partitioned by year and month, but query filters only on year=2023.

2. Step 2: Evaluate optimization options

   Adding bucketing on month helps organize data within partitions. Enabling cost-based optimization lets Hive choose best plan.

3. Step 3: Assess other options

   Dropping month partition reduces granularity; disabling pruning or removing WHERE clause worsens performance.

4. Final Answer:

   Add bucketing on month and enable cost-based optimization -> Option A

5. Quick Check:

   Partition + bucketing + CBO = best performance [OK]

Hint: Combine partitioning, bucketing, and CBO for best speed [OK]

Common Mistakes:

• Removing useful partitions
• Disabling pruning increases data scanned
• Ignoring cost-based optimization benefits