Most Recent Releases

Latest Release 0.11.3 (May 18, 2016)

Previous Releases

Release 0.11.2 (Apr 7, 2016)

Release 0.11.1 (Feb 3, 2016)

Release 0.11.0 (Oct 27, 2015)

Release 0.10.1 (Jun 29, 2015)

Release 0.10.0 (Mar 8, 2015)

Release 0.9.0 (Oct 21, 2014)

Release 0.2-incubating (Nov 20, 2013)

Nightly builds

For developers, Tajo maintains nightly builds and SNAPSHOT artifacts. More information is available on Tajo developer Wiki.

Getting the source code via Git

The development codebase can also be downloaded from the Apache git repository as follows:

git clone

A read-only git repository is also mirrored on Github.

Once you have downloaded Tajo, follow the getting started instructions, and take a look at the rest of the Tajo documentation.

How to Verify the integrity of the files

It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. Please read Verifying Apache HTTP Server Releases for more information on why you should verify our releases.

The PGP signatures can be verified using PGP or GPG. First download the KEYS as well as the asc signature file for the relevant distribution. Make sure you get these files from the main distribution directory , rather than from a mirror. Then verify the signatures using

% pgpk -a KEYS

% pgpv tajo-0.X.0.tar.gz.asc


% pgp -ka KEYS

% pgp tajo-0.X.0.tar.gz.asc


% gpg --import KEYS

% gpg --verify tajo-0.X.0.tar.gz.asc

How to verify SHA1/MD5 hash values

Alternatively, you can verify the MD5 signature on the files. A unix program called md5 or md5sum is included in many unix distributions. It is also available as part of GNU Textutils. An MD5 signature consists of 32 hex characters, and a SHA1 signature consists of 40 hex characters. You can verify the signatures as follows:

md5sum -c tajo-0.x.0.tar.gz.md5


sha1sum -c tajo-0.x.0.tar.gz.sha1