Skip to main content

Hive on Tez: Why It Was Faster and Why Manual CDH Integration Is Now Legacy

By Anonymous
Struggling with delivery, architecture alignment, or platform stability?

I help teams fix systemic engineering issues: processes, architecture, and clarity.
→ See how I work with teams.


Apache Tez was introduced as a faster, DAG-based execution engine for Hive and other Hadoop workloads, delivering 30–50% speedups over classic MapReduce in many ETL pipelines. This article explains what Tez brought to Hive, how it fit into CDH-era deployments, and why the old practice of hand-compiling Tez against CDH 5.x is now a legacy pattern rather than a recommended approach.

Apache Tez was designed as a low-latency, DAG-based execution engine for Hadoop. It replaced many of the heavyweight MapReduce patterns used by early Hive deployments with more efficient execution graphs, reusing containers and avoiding unnecessary materialization steps.

In practical terms, switching Hive from MapReduce to Tez often yielded 30–50% faster ETL and reporting jobs on the same hardware, especially for complex multi-stage queries.

What Tez Brought to Hive

  • DAG execution: instead of chaining MapReduce jobs, Tez represents the query plan as a directed acyclic graph of tasks.
  • Container reuse: tasks are scheduled more efficiently on YARN, reducing startup overhead.
  • Better pipelining: intermediate data can be handled with less disk I/O compared to classic MapReduce.
  • Improved latency: especially visible in Hive ETL workloads with joins, aggregations and multi-step pipelines.

As distributions matured, Tez became a supported execution engine in certain vendor stacks (e.g. in HDP-era Hive deployments), and users could enable it with a simple configuration change instead of custom builds.

Why Manual Tez + CDH 5.4 Integration Is Now Legacy

When this article was originally written, Cloudera’s CDH 5.4 did not officially support Tez. Getting Tez to run with CDH required a series of manual steps:

  • Installing specific versions of Maven, JDK and Protobuf on CentOS 6.x
  • Cloning the Tez source code and building a matching release (e.g. Tez 0.7) against the CDH Hadoop version
  • Modifying pom.xml to use hadoop-2.6.0-cdh5.4.x and Cloudera repositories
  • Packaging Tez, uploading it to HDFS (e.g. /apps/tez) and configuring tez-site.xml
  • Extending the HADOOP_CLASSPATH and setting TEZ_HOME and TEZ_CONF_DIR
  • Switching Hive to Tez via set hive.execution.engine=tez;

These steps were valuable at the time for experimentation, and our own tests showed significant performance improvements on CDH 5.4 clusters. However, this approach:

  • Is tightly coupled to an end-of-life distribution (CDH 5.x)
  • Depends on outdated toolchains and library versions
  • Is not supported by Cloudera and should not be used in modern environments

Modern Perspective: Tez vs. Other Engines

Today, most new data platforms and lakehouse environments use engines such as:

  • Spark SQL
  • Trino / Presto
  • Hive LLAP in legacy deployments

Tez still appears in some long-lived clusters and as an execution option for certain Hive stacks, but the pattern of compiling Tez against a vendor distribution by hand is now a legacy workaround. For any modern deployment:

  • Use vendor-supported engines and integration points.
  • Avoid building Tez manually against old Hadoop versions.
  • Plan migrations off EOL distributions such as CDH 5.x.

Historical Notes

Originally, the environment for our Tez-on-CDH experiments was:

  • CDH 5.4 on CentOS 6.7
  • Manually installed Maven 3.2.5 and Oracle JDK 8u40
  • Protobuf 2.5.0 built from source or precompiled RPMs
  • Tez 0.7.0 compiled with a custom Maven profile targeting CDH Hadoop

These details are kept here purely for historical context, to show what it took to run Tez on an unsupported distribution and why modern, supported integrations are preferable today.

For current Tez installation and configuration details, always refer to the official Apache Tez documentation and the guidance of your Hadoop distribution vendor.

Related guides:

If you need help with distributed systems, backend engineering, or data platforms, check my Services.

Labels:

Most read articles

Building a Model-Agnostic Multi-Agent System with OpenClaw

By
Over one week we rebuilt our AI stack around OpenClaw’s multi-agent architecture to avoid provider lock-in and stop wasting premium tokens. By aligning models to tasks, diversifying fallbacks across providers, enforcing minimal tool access, and switching to memory-first workflows with ephemeral sessions, we reduced token usage per task by about 70% and cut our monthly bill by 77% while improving operational resilience. How We Achieved 77% Cost Reduction and Provider Independence Over the past week, we rebuilt our AI infrastructure around OpenClaw’s multi-agent architecture. The result was a 77% cost reduction , provider independence , and a delegation system that routes work to the most cost-effective model for each job. Below is the technical journey of optimizing a 7-agent squad with OpenClaw. The Challenge: Model Provider Lock-In We started with a simple problem: our entire squad defaulted to a single model provider. This created three issues: Cost inefficiency beca...
Read more

BacNet => MQTT in Production: The Real Cost of Bridging BACnet to MQTT at Scale

By
bacnet2mqtt looks simple in a README and expensive in production. Once BACnet polling, reconnection behavior, stale state, and MQTT publishing collide, teams discover they are not deploying a lightweight adapter but operating infrastructure. This article breaks down where bacnet2mqtt works, where it becomes a bottleneck, and which production patterns reduce the operational damage before incidents, backlogs, and silent data loss turn a building integration into a long-running engineering problem. I inherited a building controls integration problem 18 months ago. Three office floors. 217 BACnet sensors covering temperature, occupancy, and HVAC actuators. The data was trapped inside the building automation network while the business wanted analytics, reporting, and compliance visibility in the data platform. The obvious answer looked easy enough: deploy bacnet2mqtt, bridge BACnet into MQTT, and push the stream into the lakehouse stack. The repository made it sound like a w...
Read more

Get Apache Flume 1.3.x running on Windows

By Anonymous
Since we found an increasing interest in the flume community to get Apache Flume running on Windows systems again, I spent some time to figure out how we can reach that. Finally, the good news - Apache Flume runs on Windows. You need some tweaks to get them running. Prerequisites Build system: maven 3x, git, jdk1.6.x, WinRAR (or similar program) Apache Flume agent: jdk1.6.x, WinRAR (or similar program), Ultraedit++ or similar texteditor Tweak the Windows build box 1. Download and install JDK 1.6x from Oracle 2. Set the environment variables    => Start - type " env " into the search box, select " E dit system environment variables ", click Environment Variables, Select " New " from the " Systems variables " box, type " JAVA_HOME " into " variable name " and the path to your JDK installation into "Variable value" (Example:  C:\Program Files (x86)\Java\jdk1.6.0_33 ) 3. Download maven from Apache 4. Set...
Read more