Skip to main content

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

By Anonymous
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

Why Is Customer Obsession Disappearing?

By
Many companies trade real customer-obsession for automated, low-empathy support. Through examples from Coinbase, PayPal, GO Telecommunications and AT&T, this article shows how reliance on AI chatbots, outsourced call centers, and KPI-driven workflows erodes trust, NPS and customer retention. It argues that human-centric support—treating support as strategic investment instead of cost—is still a core growth engine in competitive markets. It's wild that even with all the cool tech we've got these days, like AI solving complex equations and doing business across time zones in a flash, so many companies are still struggling with the basics: taking care of their customers. The drama around Coinbase's customer support is a prime example of even tech giants messing up. And it's not just Coinbase — it's a big-picture issue for the whole industry. At some point, the idea of "customer obsession" got replaced with "customer automation," and no...
Read more

How to scale MySQL perfectly

By
When MySQL reaches its limits, scaling cannot rely on hardware alone. This article explains how strategic techniques such as caching, sharding and operational optimisation can drastically reduce load and improve application responsiveness. It outlines how in-memory systems like Redis or Memcached offload repeated reads, how horizontal sharding mechanisms distribute data for massive scale, and how tools such as Vitess, ProxySQL and HAProxy support routing, failover and cluster management. The summary also highlights essential practices including query tuning, indexing, replication and connection management. Together these approaches form a modern DevOps strategy that transforms MySQL from a single bottleneck into a resilient, scalable data layer able to grow with your application. When your MySQL database reaches its performance limits, vertical scaling through hardware upgrades provides a temporary solution. Long-term growth, though, requires a more comprehensive approach. This invo...
Read more

What the Heck is Superposition and Entanglement?

By
This post is about superposition and interference in simple, intuitive terms. It describes how quantum states combine, how probability amplitudes add, and why interference patterns appear in systems such as electrons, photons and waves. The goal is to give a clear, non mathematical understanding of how quantum behavior emerges from the rules of wave functions and measurement. If you’ve ever heard the words superposition or entanglement thrown around in conversations about quantum physics, you may have nodded politely while your brain quietly filed them away in the "too confusing to deal with" folder.  These aren't just theoretical quirks; they're the foundation of mind-bending tech like Google's latest quantum chip, the Willow with its 105 qubits. Superposition challenges our understanding of reality, suggesting that particles don't have definite states until observed. This principle is crucial in quantum technologies, enabling phenomena like quantum comp...
Read more