git steps checkout download version apache hive Version Control. The Hive source code resides in the Apache Subversion (SVN) repository. (read-only) (read-only) (read-write) Github Mirror Instructions: Anonymous SVNCommitter SVN. Copyright © 2011-2014 The Apache Software Foundation Licensed under the Apache License, Version 2.0. Apache Hive, Hive, Apache, the Apache feather logo, and the Apache Hive project logo are trademarks of The Apache Software Foundation. Other names appearing on the site may be trademarks of their respective owners. Downloads. On the mirror, all recent releases are available, but are not guaranteed to be stable. For stable releases, look in the stable directory. 17 January 2021: release 2.3.8 available¶ This release works with Hadoop 2.x.y You can look at the complete JIRA change log for this release. 18 April 2020: release 2.3.7 available¶ This release works with Hadoop 2.x.y You can look at the complete JIRA change log for this release. 26 August 2019: release 3.1.2 available¶ This release works with Hadoop 3.x.y. You can look at the complete JIRA change log for this release. 23 August 2019: release 2.3.6 available¶ This release works with Hadoop 2.x.y. You can look at the complete JIRA change log for this release. 14 May 2019: release 2.3.5 available¶ This release works with Hadoop 2.x.y. You can look at the complete JIRA change log for this release. 7 November 2018: release 2.3.4 available¶ This release works with Hadoop 2.x.y. You can look at the complete JIRA change log for this release. 1 November 2018: release 3.1.1 available¶ This release works with Hadoop 3.x.y. You can look at the complete JIRA change log for this release. 30 July 2018: release 3.1.0 available¶ This release works with Hadoop 3.x.y. You can look at the complete JIRA change log for this release. 21 May 2018 : release 3.0.0 available¶ This release works with Hadoop 3.x.y. The on-disk layout of Acid tables has changed with this release. Any Acid table partition that had Update/Delete/Merge statement executed since the last Major compaction must execute Major compaction before upgrading to 3.0. No more Update/Delete/Merge may be executed against these tables since the start of Major compaction. Not following this may lead to data corruption. Tables/partitions that only contain results of Insert statements are fully compatible and don't need to be compacted. You can look at the complete JIRA change log for this release. 3 April 2018 : release 2.3.3 available¶ This release works with Hadoop 2.x.y You can look at the complete JIRA change log for this release. 18 November 2017 : release 2.3.2 available¶ This release works with Hadoop 2.x.y You can look at the complete JIRA change log for this release. 24 October 2017 : release 2.3.1 available¶ This release works with Hadoop 2.x.y You can look at the complete JIRA change log for this release. 25 July 2017 : release 2.2.0 available¶ This release works with Hadoop 2.x.y You can look at the complete JIRA change log for this release. 17 July 2017 : release 2.3.0 available¶ This release works with Hadoop 2.x.y You can look at the complete JIRA change log for this release. 07 April 2017 : release 1.2.2 available¶ This release works with Hadoop 1.x.y, 2.x.y You can look at the complete JIRA change log for this release. 8 December 2016 : release 2.1.1 available¶ This release works with Hadoop 2.x.y. Hive 1.x line will continue to be maintained with Hadoop 1.x.y support. You can look at the complete JIRA change log for this release. 20 June 2016 : release 2.1.0 available¶ This release works with Hadoop 2.x.y. Hive 1.x line will continue to be maintained with Hadoop 1.x.y support. You can look at the complete JIRA change log for this release. 25 May 2016 : release 2.0.1 available¶ This release works with Hadoop 2.x.y. Hive 1.x line will continue to be maintained with Hadoop 1.x.y support. You can look at the complete JIRA change log for this release. 15 February 2016 : release 2.0.0 available¶ This release works with Hadoop 2.x.y. Hive 1.x line will continue to be maintained with Hadoop 1.x.y support. You can look at the complete JIRA change log for this release. 28 Jan 2016 : hive-parent-auth-hook made available¶ This is a hook usable with hive to fix an authorization issue. Users of Hive 1.0.x,1.1.x and 1.2.x are encouraged to use this hook. More details can be found in the README inside the tar.gz file. 27 June 2015 : release 1.2.1 available¶ This release works with Hadoop 1.x.y, 2.x.y. 21 May 2015 : release 1.0.1, 1.1.1, and ldap-fix are available¶ These two releases works with Hadoop 1.x.y, 2.x.y. They are based on Hive 1.0.0 and 1.1.0 respectively, plus a fix for a LDAP vulnerability issue. Hive users for these two versions are encouraged to upgrade. Users of previous versions can download and use the ldap-fix. More details can be found in the README attached to the tar.gz file. You can look at the complete JIRA change log for release 1.0.1 and release 1.1.1. 18 May 2015 : release 1.2.0 available¶ This release works with Hadoop 1.x.y, 2.x.y. 8 March 2015: release 1.1.0 available¶ This release works with Hadoop 1.x.y, 2.x.y. 4 February 2015: release 1.0.0 available¶ This release works with Hadoop 1.x.y, 2.x.y. 12 November, 2014: release 0.14.0 available¶ This release works with Hadoop 1.x.y, 2.x.y. 6 June, 2014: release 0.13.1 available¶ This release works with Hadoop 0.20.x, 0.23.x.y, 1.x.y, 2.x.y. 21 April, 2014: release 0.13.0 available¶ This release works with Hadoop 0.20.x, 0.23.x.y, 1.x.y, 2.x.y. 15 October, 2013: release 0.12.0 available¶ This release works with Hadoop 0.20.x, 0.23.x.y, 1.x.y, 2.x.y. 15 May, 2013: release 0.11.0 available¶ This release works with Hadoop 0.20.x, 0.23.x.y, 1.x.y, 2.x.y. March, 2013: HCatalog merges into Hive¶ Old HCatalog releases may still be downloaded. 11 January, 2013: release 0.10.0 available¶ This release works with Hadoop 0.20.x, 0.23.x.y, 1.x.y, 2.x.y. Copyright © 2011-2014 The Apache Software Foundation Licensed under the Apache License, Version 2.0. Apache Hive, Hive, Apache, the Apache feather logo, and the Apache Hive project logo are trademarks of The Apache Software Foundation. Other names appearing on the site may be trademarks of their respective owners. HowToRelease. Skip this section if this is NOT the first release in a series (i.e., release X.Y.0). Notify developers on the #hive IRC channel and dev@hive mailing lists that you are about to branch a release. Create a branch for the release series: Increment the value of the version property in all pom.xml files. For example, if the current value is 0.7.0-SNAPSHOT , the new value should be 0.8.0-SNAPSHOT . Please note that the SNAPSHOT suffix is required in order to indicate that this is an unreleased development branch. This can be accomplished with a single command using Maven's Versions plugin as follows: Commit these changes to master with a comment "Preparing for X.Y+1.0 development". Updating Release Branch. These operations take place in the release branch. Check out the release branch with: Update the version property value in all pom.xml files. You should remove the SNAPSHOT suffix and set version equal to hive-X.Y.Z where Z is the point release number in this release series (0 for the first one, in which case this step is a no-op since you already did this above when creating the branch). Use Maven's Versions plugin to do this as follows: Commit these changes with a comment "Preparing for X.Y.Z development". If not already done, merge desired patches from trunk into the branch and commit these changes. Avoid usage of "git merge" to avoid too many merge commits. Either request the committer who committed that patch in master to commit to this branch, or commit it yourself, or try doing a git cherry-pick for trivial patches. Specifics of this step can be laid down by the release manager. Select all of the JIRAs for the current release that aren't FIXED and do bulk update to clear the 'Fixed Version' field. Likewise, use JIRA's Release Notes link to generate content for the RELEASE_NOTES.txt file. Be sure to select 'Text' format. (It's OK to do this with a direct commit rather than a patch.) Update the release notes in trunk with the release notes in branch. Tag the release candidate (R is the release candidate number, and also starts from 0): Building.