You are on page 1of 9

If you prefer to run the unit tests, remove skipTests from the command a

bove.
If you use Eclipse IDE, you can import the projects using Import/Maven/Ex
isting Maven Projects. Eclipse does not automatically generate Java sources or in
clude the generated sources into the projects. Please build using maven as descr
ibed above and then use Project Properties to include target/generatedsources/jav
a as a source directory into the Java Build Path for these projects: tez-api, tez-m
apreduce, tez-runtime-internals and tez-runtime-library. This needs to be done j
ust once after importing the project.
Copy the relevant tez tarball into HDFS, and configure tez-site.xml
A tez tarball containing tez and hadoop libraries will be found at tez-d
ist/target/tez-x.y.z-SNAPSHOT.tar.gz
Assuming that the tez jars are put in /apps/ on HDFS, the command would
be
hadoop dfs -mkdir /apps/tez-x.y.z-SNAPSHOT
hadoop dfs -copyFromLocal tez-dist/target/tez-x.y.z-SNAPSHOT-archive.tar.gz
/apps/tez-x.y.z-SNAPSHOT/
tez-site.xml configuration.
Set tez.lib.uris to point to the tar.gz uploaded to HDFS. Assuming t
he steps mentioned so far were followed, set tez.lib.uris to ${fs.defaultFS}/app
s/tez-x.y.z-SNAPSHOT/tez-x.y.z-SNAPSHOT.tar.gz
Ensure tez.use.cluster.hadoop-libs is not set in tez-site.xml, or if
it is set, the value should be false
Please note that the tarball version should match the version of the cli
ent jars used when submitting Tez jobs to the cluster. Please refer to the Versi
on Compatibility Guide for more details on version compatibility and detecting m
ismatches.
Optional: If running existing MapReduce jobs on Tez. Modify mapred-site.xml
to change mapreduce.framework.name property from its default value of yarn to yarn-te
z
Configure the client node to include the tez-libraries in the hadoop classpa
th
Extract the tez minimal tarball created in step 2 to a local directory (
assuming TEZ_JARS is where the files will be decompressed for the next steps)
tar -xvzf tez-dist/target/tez-x.y.z-minimal.tar.gz -C $TEZ_JARS
set TEZ_CONF_DIR to the location of tez-site.xml
Add $TEZ_CONF_DIR, ${TEZ_JARS}/* and ${TEZ_JARS}/lib/* to the applicatio
n classpath. For example, doing it via the standard Hadoop tool chain would use
the following command to set up the application classpath:
export HADOOP_CLASSPATH=${TEZ_CONF_DIR}:${TEZ_JARS}/*:${TEZ_JARS}/lib/*
Please note the * which is an important requirement when setting up classp
aths for directories containing jar files.
There is a basic example of using an MRR job in the tez-examples.jar. Refer
to OrderedWordCount.java in the source code. To run this example:
$HADOOP_PREFIX/bin/hadoop jar tez-examples.jar orderedwordcount <input> <out
put>
This will use the TEZ DAG ApplicationMaster to run the ordered word count jo
b. This job is similar to the word count example except that it also orders all
words based on the frequency of occurrence.

Tez DAGs could be run separately as different applications or serially withi


n a single TEZ session. There is a different variation of orderedwordcount in te
z-tests that supports the use of Sessions and handling multiple input-output pai
rs. You can use it to run multiple DAGs serially on different inputs/outputs.
$HADOOP_PREFIX/bin/hadoop jar tez-tests.jar testorderedwordcount <input1> <o
utput1> <input2> <output2> <input3> <output3> ...
The above will run multiple DAGs for each input-output pair.
To use TEZ sessions, set -DUSE_TEZ_SESSION=true
$HADOOP_PREFIX/bin/hadoop jar tez-tests.jar testorderedwordcount -DUSE_TEZ_S
ESSION=true <input1> <output1> <input2> <output2>
Submit a MR job as you normally would using something like:
$HADOOP_PREFIX/bin/hadoop jar hadoop-mapreduce-client-jobclient-3.0.0-SNAPSH
OT-tests.jar sleep -mt 1 -rt 1 -m 1 -r 1
This will use the TEZ DAG ApplicationMaster to run the MR job. This can be v
erified by looking at the AMs logs from the YARN ResourceManager UI. This needs m
apred-site.xml to have mapreduce.framework.name set to yarn-tez
Various ways to configure tez.lib.uris
The tez.lib.uris configuration property supports a comma-separated list of value
s. The types of values supported are: - Path to simple file - Path to a director
y - Path to a compressed archive ( tarball, zip, etc).
For simple files and directories, Tez will add all these files and first-level e
ntries in the directories (recursive traversal of dirs is not supported) into th
e working directory of the Tez runtime and they will automatically be included i
nto the classpath. For archives i.e. files whose names end with generally known
compressed archive suffixes such as tgz, tar.gz, zip, etc. will be uncompressed into t
he container working directory too. However, given that the archive structure is
not known to the Tez framework, the user is expected to configure tez.lib.uris.
classpath to ensure that the nested directory structure of an archive is added t
o the classpath. This classpath values should be relative i.e. the entries shoul
d start with ./.
Hadoop Installation dependent Install/Deploy Instructions
The above install instructions use Tez with pre-packaged Hadoop libraries includ
ed in the package and is the recommended method for installation. A full tarball
with all dependencies is a better approach to ensure that existing jobs continu
e to run during a clusters rolling upgrade.
Although the tez.lib.uris configuration options enable a wide variety of usage p
atterns, there are 2 main alternative modes that are supported by the framework:
Mode A: Using a tez tarball on HDFS along with Hadoop libraries available on
the cluster.
Mode B: Using a tez tarball along with the Hadoop tarball.
Both these modes will require a tez build without Hadoop dependencies and that i
s available at tez-dist/target/tez-x.y.z-minimal.tar.gz.
For Mode A: Tez tarball with using existing cluster Hadoop libraries by leveragi
ng yarn.application.classpath

This mode is not recommended for clusters that use rolling upgrades. Additionall
y, it is the users responsibility to ensure that the tez version being used is co
mpatible with the version of Hadoop running on the cluster. Step 3 above changes
as follows. Also subsequent steps should use tez-dist/target/tez-x.y.z-minimal.
tar.gz instead of tez-dist/target/tez-x.y.z.tar.gz
A tez build without Hadoop dependencies will be available at tez-dist/target
/tez-x.y.z-minimal.tar.gz Assuming that the tez jars are put in /apps/ on HDFS,
the command would be
"hadoop fs -mkdir /apps/tez-x.y.z"
"hadoop fs -copyFromLocal tez-dist/target/tez-x.y.z-minimal.tar.gz /apps/tez
-x.y.z"
tez-site.xml configuration
Set tez.lib.uris to point to the paths in HDFS containing the tez jars.
Assuming the steps mentioned so far were followed, set tez.lib.uris to ${fs.defa
ultFS}/apps/tez-x.y.z/tez-x.y.z-minimal.tar.gz
Set tez.use.cluster.hadoop-libs to true
For Mode B: Tez tarball with Hadoop tarball
This mode will support rolling upgrades. It is the users responsibility to ensure
that the versions of Tez and Hadoop being used are compatible. To do this confi
guration, we need to change Step 3 of the default instructions in the following
ways.
Assuming that the tez archives/jars are put in /apps/ on HDFS, the command t
o put this minimal Tez archive into HDFS would be:
"hadoop fs -mkdir /apps/tez-x.y.z" "hadoop fs -copyFromLocal tez-dist/target/tez
-x.y.z-minimal.tar.gz /apps/tez-x.y.z"
Alternatively, you can put the minimal directory directly into HDFS and refe
rence the jars, instead of using an archive. The command to put the minimal dire
ctory into HDFS would be:
"hadoop fs -copyFromLocal tez-dist/target/tez-x.y.z-minimal/* /apps/tez-x.y.z"
After building hadoop, the hadoop tarball will be available at hadoop/hadoop
-dist/target/hadoop-x.y.z-SNAPSHOT.tar.gz
Assuming that the hadoop jars are put in /apps/ on HDFS, the command to put
this Hadoop archive into HDFS would be:
"hadoop fs -mkdir /apps/hadoop-x.y.z" "hadoop fs -copyFromLocal hadoop-dist/targ
et/hadoop-x.y.z-SNAPSHOT.tar.gz /apps/hadoop-x.y.z"
tez-site.xml configuration
Set tez.lib.uris to point to the the archives and jars that are needed f
or Tez/Hadoop.
Example: When using both Tez and Hadoop archives, set tez.lib.uris to ${
fs.defaultFS}/apps/tez-x.y.z/tez-x.y.z-minimal.tar.gz#tez,${fs.defaultFS}/apps/h
adoop-x.y.z/hadoop-x.y.z-SNAPSHOT.tar.gz#hadoop-mapreduce
Example: When using Tez jars with a Hadoop archive, set tez.lib.uris to:
${fs.defaultFS}/apps/tez-x.y.z,${fs.defaultFS}/apps/tez-x.y.z/lib,${fs.defaultF
S}/apps/hadoop-x.y.z/hadoop-x.y.z-SNAPSHOT.tar.gz#hadoop-mapreduce
In tez.lib.uris, the text immediately following the # symbol is the fragme
nt that refers to the symlink that will be created for the archive. If no fragme
nt is given, the symlink will be set to the name of the archive. Fragments shoul
d not be given to directories or jars.

If any archives are specified in tez.lib.uris, then tez.lib.uris.classpa


th must be set to define the classpath for these archives as the archive structu
re is not known.
Example: Classpath when using both Tez and Hadoop archives, set tez.lib.
uris.classpath to:
./tez/*:./tez/lib/*:./hadoop-mapreduce/hadoop-x.y.z-SNAPSHOT/share/hadoop/co
mmon/*:./hadoop-mapreduce/hadoop-x.y.z-SNAPSHOT/share/hadoop/common/lib/*:./hado
op-mapreduce/hadoop-x.y.z-SNAPSHOT/share/hadoop/hdfs/*:./hadoop-mapreduce/hadoop
-x.y.z-SNAPSHOT/share/hadoop/hdfs/lib/*:./hadoop-mapreduce/hadoop-x.y.z-SNAPSHOT
/share/hadoop/yarn/*:./hadoop-mapreduce/hadoop-x.y.z-SNAPSHOT/share/hadoop/yarn/
lib/*:./hadoop-mapreduce/hadoop-x.y.z-SNAPSHOT/share/hadoop/mapreduce/*:./hadoop
-mapreduce/hadoop-x.y.z-SNAPSHOT/share/hadoop/mapreduce/lib/*
Example: Classpath when using Tez jars with a Hadoop archive, set tez.li
b.uris.classpath to:
./hadoop-mapreduce/hadoop-x.y.z-SNAPSHOT/share/hadoop/common/*:./hadoop-mapr
educe/hadoop-x.y.z-SNAPSHOT/share/hadoop/common/lib/*:./hadoop-mapreduce/hadoopx.y.z-SNAPSHOT/share/hadoop/hdfs/*:./hadoop-mapreduce/hadoop-x.y.z-SNAPSHOT/shar
e/hadoop/hdfs/lib/*:./hadoop-mapreduce/hadoop-x.y.z-SNAPSHOT/share/hadoop/yarn/*
:./hadoop-mapreduce/hadoop-x.y.z-SNAPSHOT/share/hadoop/yarn/lib/*:./hadoop-mapre
duce/hadoop-x.y.z-SNAPSHOT/share/hadoop/mapreduce/*:./hadoop-mapreduce/hadoop-x.
y.z-SNAPSHOT/share/hadoop/mapreduce/lib/*
Install instructions for older versions of Tez (pre 0.5.0)
Copyright 2016 Apache Software Foundation. All Rights Reserved.
Apache Tez, Apache, the Apache feather logo, and the Apache Tez project logos ar
e trademarks of The Apache Software Foundation. All other marks mentioned may be
trademarks or registered trademarks of their respective owners.
Privacy Policy

Getting Started
Documentation
Community
Download Apache Tez Releases
Contribute
ASF
Apache Tez
Apache Software Foundation
Apache Tez / Install and Deployment Instructions
Last Published: 2016-09-01
Getting Started
Overview
Talks and Meetup Recordings
Project License
Documentation
Install Guide
Local Mode
Tez UI
User Guides
Community
Mailing Lists
Issue Tracking

Project Team
Project By-Laws
User Meetup Group
Tez Wiki
Download Apache Tez Releases
0.4.1-incubating
0.5.4
0.6.2
0.7.1
0.8.4
All Releases
Contribute
JIRA
Git (Read/Write)
Git (Read-only)
How to Contribute
ASF
License
Donate
Thanks
Security
Follow ApacheTez
Built by Maven
Install/Deploy Instructions for Tez
Replace x.y.z with the tez release number that you are using. E.g. 0.5.0. For Te
z versions 0.8.3 and higher, Tez needs Apache Hadoop to be of version 2.6.0 or h
igher.
Deploy Apache Hadoop using version of 2.6.0 or higher.
You need to change the value of the hadoop.version property in the top-l
evel pom.xml to match the version of the hadoop branch being used.
$ hadoop version
Build tez using mvn clean package -DskipTests=true -Dmaven.javadoc.skip=true
This assumes that you have already installed JDK6 or later and Maven 3 o
r later.
Tez also requires Protocol Buffers 2.5.0, including the protoc-compiler.
This can be downloaded from https://github.com/google/protobuf/tags/
.
On Mac OS X with the homebrew package manager brew install protobuf2
50
For rpm-based linux systems, the yum repos may not have the 2.5.0 ve
rsion. rpm.pbone.net has the protobuf-2.5.0 and protobuf-compiler-2.5.0 packages
.
If you prefer to run the unit tests, remove skipTests from the command a
bove.
If you use Eclipse IDE, you can import the projects using Import/Maven/Ex
isting Maven Projects. Eclipse does not automatically generate Java sources or in
clude the generated sources into the projects. Please build using maven as descr
ibed above and then use Project Properties to include target/generatedsources/jav
a as a source directory into the Java Build Path for these projects: tez-api, tez-m
apreduce, tez-runtime-internals and tez-runtime-library. This needs to be done j
ust once after importing the project.
Copy the relevant tez tarball into HDFS, and configure tez-site.xml
A tez tarball containing tez and hadoop libraries will be found at tez-d

ist/target/tez-x.y.z-SNAPSHOT.tar.gz
Assuming that the tez jars are put in /apps/ on HDFS, the command would
be
hadoop dfs -mkdir /apps/tez-x.y.z-SNAPSHOT
hadoop dfs -copyFromLocal tez-dist/target/tez-x.y.z-SNAPSHOT-archive.tar.gz
/apps/tez-x.y.z-SNAPSHOT/
tez-site.xml configuration.
Set tez.lib.uris to point to the tar.gz uploaded to HDFS. Assuming t
he steps mentioned so far were followed, set tez.lib.uris to ${fs.defaultFS}/app
s/tez-x.y.z-SNAPSHOT/tez-x.y.z-SNAPSHOT.tar.gz
Ensure tez.use.cluster.hadoop-libs is not set in tez-site.xml, or if
it is set, the value should be false
Please note that the tarball version should match the version of the cli
ent jars used when submitting Tez jobs to the cluster. Please refer to the Versi
on Compatibility Guide for more details on version compatibility and detecting m
ismatches.
Optional: If running existing MapReduce jobs on Tez. Modify mapred-site.xml
to change mapreduce.framework.name property from its default value of yarn to yarn-te
z
Configure the client node to include the tez-libraries in the hadoop classpa
th
Extract the tez minimal tarball created in step 2 to a local directory (
assuming TEZ_JARS is where the files will be decompressed for the next steps)
tar -xvzf tez-dist/target/tez-x.y.z-minimal.tar.gz -C $TEZ_JARS
set TEZ_CONF_DIR to the location of tez-site.xml
Add $TEZ_CONF_DIR, ${TEZ_JARS}/* and ${TEZ_JARS}/lib/* to the applicatio
n classpath. For example, doing it via the standard Hadoop tool chain would use
the following command to set up the application classpath:
export HADOOP_CLASSPATH=${TEZ_CONF_DIR}:${TEZ_JARS}/*:${TEZ_JARS}/lib/*
Please note the * which is an important requirement when setting up classp
aths for directories containing jar files.
There is a basic example of using an MRR job in the tez-examples.jar. Refer
to OrderedWordCount.java in the source code. To run this example:
$HADOOP_PREFIX/bin/hadoop jar tez-examples.jar orderedwordcount <input> <out
put>
This will use the TEZ DAG ApplicationMaster to run the ordered word count jo
b. This job is similar to the word count example except that it also orders all
words based on the frequency of occurrence.
Tez DAGs could be run separately as different applications or serially withi
n a single TEZ session. There is a different variation of orderedwordcount in te
z-tests that supports the use of Sessions and handling multiple input-output pai
rs. You can use it to run multiple DAGs serially on different inputs/outputs.
$HADOOP_PREFIX/bin/hadoop jar tez-tests.jar testorderedwordcount <input1> <o
utput1> <input2> <output2> <input3> <output3> ...
The above will run multiple DAGs for each input-output pair.
To use TEZ sessions, set -DUSE_TEZ_SESSION=true

$HADOOP_PREFIX/bin/hadoop jar tez-tests.jar testorderedwordcount -DUSE_TEZ_S


ESSION=true <input1> <output1> <input2> <output2>
Submit a MR job as you normally would using something like:
$HADOOP_PREFIX/bin/hadoop jar hadoop-mapreduce-client-jobclient-3.0.0-SNAPSH
OT-tests.jar sleep -mt 1 -rt 1 -m 1 -r 1
This will use the TEZ DAG ApplicationMaster to run the MR job. This can be v
erified by looking at the AMs logs from the YARN ResourceManager UI. This needs m
apred-site.xml to have mapreduce.framework.name set to yarn-tez
Various ways to configure tez.lib.uris
The tez.lib.uris configuration property supports a comma-separated list of value
s. The types of values supported are: - Path to simple file - Path to a director
y - Path to a compressed archive ( tarball, zip, etc).
For simple files and directories, Tez will add all these files and first-level e
ntries in the directories (recursive traversal of dirs is not supported) into th
e working directory of the Tez runtime and they will automatically be included i
nto the classpath. For archives i.e. files whose names end with generally known
compressed archive suffixes such as tgz, tar.gz, zip, etc. will be uncompressed into t
he container working directory too. However, given that the archive structure is
not known to the Tez framework, the user is expected to configure tez.lib.uris.
classpath to ensure that the nested directory structure of an archive is added t
o the classpath. This classpath values should be relative i.e. the entries shoul
d start with ./.
Hadoop Installation dependent Install/Deploy Instructions
The above install instructions use Tez with pre-packaged Hadoop libraries includ
ed in the package and is the recommended method for installation. A full tarball
with all dependencies is a better approach to ensure that existing jobs continu
e to run during a clusters rolling upgrade.
Although the tez.lib.uris configuration options enable a wide variety of usage p
atterns, there are 2 main alternative modes that are supported by the framework:
Mode A: Using a tez tarball on HDFS along with Hadoop libraries available on
the cluster.
Mode B: Using a tez tarball along with the Hadoop tarball.
Both these modes will require a tez build without Hadoop dependencies and that i
s available at tez-dist/target/tez-x.y.z-minimal.tar.gz.
For Mode A: Tez tarball with using existing cluster Hadoop libraries by leveragi
ng yarn.application.classpath
This mode is not recommended for clusters that use rolling upgrades. Additionall
y, it is the users responsibility to ensure that the tez version being used is co
mpatible with the version of Hadoop running on the cluster. Step 3 above changes
as follows. Also subsequent steps should use tez-dist/target/tez-x.y.z-minimal.
tar.gz instead of tez-dist/target/tez-x.y.z.tar.gz
A tez build without Hadoop dependencies will be available at tez-dist/target
/tez-x.y.z-minimal.tar.gz Assuming that the tez jars are put in /apps/ on HDFS,
the command would be
"hadoop fs -mkdir /apps/tez-x.y.z"
"hadoop fs -copyFromLocal tez-dist/target/tez-x.y.z-minimal.tar.gz /apps/tez

-x.y.z"
tez-site.xml configuration
Set tez.lib.uris to point to the paths in HDFS containing the tez jars.
Assuming the steps mentioned so far were followed, set tez.lib.uris to ${fs.defa
ultFS}/apps/tez-x.y.z/tez-x.y.z-minimal.tar.gz
Set tez.use.cluster.hadoop-libs to true
For Mode B: Tez tarball with Hadoop tarball
This mode will support rolling upgrades. It is the users responsibility to ensure
that the versions of Tez and Hadoop being used are compatible. To do this confi
guration, we need to change Step 3 of the default instructions in the following
ways.
Assuming that the tez archives/jars are put in /apps/ on HDFS, the command t
o put this minimal Tez archive into HDFS would be:
"hadoop fs -mkdir /apps/tez-x.y.z" "hadoop fs -copyFromLocal tez-dist/target/tez
-x.y.z-minimal.tar.gz /apps/tez-x.y.z"
Alternatively, you can put the minimal directory directly into HDFS and refe
rence the jars, instead of using an archive. The command to put the minimal dire
ctory into HDFS would be:
"hadoop fs -copyFromLocal tez-dist/target/tez-x.y.z-minimal/* /apps/tez-x.y.z"
After building hadoop, the hadoop tarball will be available at hadoop/hadoop
-dist/target/hadoop-x.y.z-SNAPSHOT.tar.gz
Assuming that the hadoop jars are put in /apps/ on HDFS, the command to put
this Hadoop archive into HDFS would be:
"hadoop fs -mkdir /apps/hadoop-x.y.z" "hadoop fs -copyFromLocal hadoop-dist/targ
et/hadoop-x.y.z-SNAPSHOT.tar.gz /apps/hadoop-x.y.z"
tez-site.xml configuration
Set tez.lib.uris to point to the the archives and jars that are needed f
or Tez/Hadoop.
Example: When using both Tez and Hadoop archives, set tez.lib.uris to ${
fs.defaultFS}/apps/tez-x.y.z/tez-x.y.z-minimal.tar.gz#tez,${fs.defaultFS}/apps/h
adoop-x.y.z/hadoop-x.y.z-SNAPSHOT.tar.gz#hadoop-mapreduce
Example: When using Tez jars with a Hadoop archive, set tez.lib.uris to:
${fs.defaultFS}/apps/tez-x.y.z,${fs.defaultFS}/apps/tez-x.y.z/lib,${fs.defaultF
S}/apps/hadoop-x.y.z/hadoop-x.y.z-SNAPSHOT.tar.gz#hadoop-mapreduce
In tez.lib.uris, the text immediately following the # symbol is the fragme
nt that refers to the symlink that will be created for the archive. If no fragme
nt is given, the symlink will be set to the name of the archive. Fragments shoul
d not be given to directories or jars.
If any archives are specified in tez.lib.uris, then tez.lib.uris.classpa
th must be set to define the classpath for these archives as the archive structu
re is not known.
Example: Classpath when using both Tez and Hadoop archives, set tez.lib.
uris.classpath to:
./tez/*:./tez/lib/*:./hadoop-mapreduce/hadoop-x.y.z-SNAPSHOT/share/hadoop/co
mmon/*:./hadoop-mapreduce/hadoop-x.y.z-SNAPSHOT/share/hadoop/common/lib/*:./hado
op-mapreduce/hadoop-x.y.z-SNAPSHOT/share/hadoop/hdfs/*:./hadoop-mapreduce/hadoop
-x.y.z-SNAPSHOT/share/hadoop/hdfs/lib/*:./hadoop-mapreduce/hadoop-x.y.z-SNAPSHOT
/share/hadoop/yarn/*:./hadoop-mapreduce/hadoop-x.y.z-SNAPSHOT/share/hadoop/yarn/
lib/*:./hadoop-mapreduce/hadoop-x.y.z-SNAPSHOT/share/hadoop/mapreduce/*:./hadoop

-mapreduce/hadoop-x.y.z-SNAPSHOT/share/hadoop/mapreduce/lib/*
Example: Classpath when using Tez jars with a Hadoop archive, set tez.li
b.uris.classpath to:
./hadoop-mapreduce/hadoop-x.y.z-SNAPSHOT/share/hadoop/common/*:./hadoop-mapr
educe/hadoop-x.y.z-SNAPSHOT/share/hadoop/common/lib/*:./hadoop-mapreduce/hadoopx.y.z-SNAPSHOT/share/hadoop/hdfs/*:./hadoop-mapreduce/hadoop-x.y.z-SNAPSHOT/shar
e/hadoop/hdfs/lib/*:./hadoop-mapreduce/hadoop-x.y.z-SNAPSHOT/share/hadoop/yarn/*
:./hadoop-mapreduce/hadoop-x.y.z-SNAPSHOT/share/hadoop/yarn/lib/*:./hadoop-mapre
duce/hadoop-x.y.z-SNAPSHOT/share/hadoop/mapreduce/*:./hadoop-mapreduce/hadoop-x.
y.z-SNAPSHOT/share/hadoop/mapreduce/lib/*
Install instructions for older versions of Tez (pre 0.5.0)
Copyright 2016 Apache Software Foundation. All Rights Reserved.
Apache Tez, Apache, the Apache feather logo, and the Apache Tez project logos ar
e trademarks of The Apache Software Foundation. All other marks mentioned may be
trademarks or registered trademarks of their respective owners.
Privacy Policy