Hive 2.0 will not be 100% backwards compatible with 1.x. The following
JIRA link shows JIRAs already committed to 2.0 that break compatibility:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20fixVersion%20%3D%202.0.0%20AND%20%22Hadoop%20Flags%22%20%3D%20%22Incompatible%20change%22
HIVE-12429 is not yet committed but may also make the list.
In summary, the biggest changes are that Hadoop 1.x is no longer
supported, MapReduce as an engine is deprecated (though still supported
for now), and HIVE-12429 proposes to switch the standard authorization
model to SQL Standard Auth instead of the current default.
The goal from the beginning was for 2.0 to be allowed to break
compatibility where necessary while branch-1 and subsequent 1.x releases
would maintain backwards compatibility with the 1.x line.
Alan.
John Omernik <mailto:j...@omernik.com>
November 30, 2015 at 9:25
Agreed, any plans for Hive 1.3? Will Hive 2.0 be a breaking release
for those running 1.x?
Wangwenli <mailto:wangwe...@huawei.com>
November 15, 2015 at 17:07
Good News, *Any release plan for hive 1.3* ???
------------------------------------------------------------------------
Wangwenli
Gopal Vijayaraghavan <mailto:gop...@apache.org>
November 13, 2015 at 22:21
(+user@)
+1.
Cheers,
Gopal
On 11/13/15, 5:54 PM, "Lefty Leverenz"<leftylever...@gmail.com> wrote:
The Hive bylaws require this to be submitted on the user@hive mailing list
(even though users don't get to vote). See Release Plan in Actions
<https://cwiki.apache.org/confluence/display/Hive/Bylaws#Bylaws-Actions>.
-- Lefty
...
On Fri, Nov 13, 2015 at 1:38 PM, Sergey Shelukhin<
ser...@hortonworks.com>
wrote:
Hi.
With no strong objections on DISCUSS thread, some issues raised and
addressed, and a reminder from Carl about the bylaws for the release
process, I propose we release the first version of Hive 2 (2.0), and
nominate myself as release manager.
The goal is to have the first release of Hive with aggressive set of
new
features, some of which are ready to use and some are at experimental
stage and will be developed in future Hive 2 releases, in line with
the
Hive-1-Hive-2 split discussion.
If the vote passes, the timeline to create a branch should be around
the
end of next week (to minimize merging in the wake of the release),
and
the
timeline to release would be around the end of November, depending on
the
issues found during the RC cutting process, as usual.
Please vote:
+1 proceed with the release plan
+-0 don¹t care
-1 don¹t proceed with the release plan, for such and such reasons
The vote will run for 3 days.
Lefty Leverenz <mailto:leftylever...@gmail.com>
November 13, 2015 at 17:54
The Hive bylaws require this to be submitted on the user@hive mailing list
(even though users don't get to vote). See Release Plan in Actions
<https://cwiki.apache.org/confluence/display/Hive/Bylaws#Bylaws-Actions>.
-- Lefty
Thejas Nair <mailto:thejas.n...@gmail.com>
November 13, 2015 at 16:33
+1
On Fri, Nov 13, 2015 at 2:26 PM, Vaibhav Gumashta
