Hadoop 2 has been GA for a little over a year, there is still a fairly significant user base that uses hadoop-1 and would not be happy with this change. It should be removed at some point, but I'm not in favor of removing in next release which would be too soon.
Perhaps we can declare it deprecated in some future release (perhaps 1.3), then another release to formally remove it, as was done in HBase. HBase did the formal removal in a major release (1.0) which is a lot cleaner, not sure if we have that luxury now that Hive 1.0 is forked. Thanks, Szehon On Tue, Apr 28, 2015 at 5:03 PM, Prasanth Jayachandran < pjayachand...@hortonworks.com> wrote: > I recently filed 5 issues (HIVE-10430, 10431, 10442, 10443, 10444) related > to build breakage of hadoop-1. There could potentially be more breakage. > Some patches were added to reduce the number of file systems calls to > improve performance but with supporting hadoop-1 we cannot directly use > such APIs. Also we are not enforcing hadoop-1 build checks in hive QA to > make sure every commit comes out clean on hadoop-1 and hadoop-2. I think it > will be good if we can focus only hadoop-2. Not only it will simplify > development but also will reduce the shims layer. > > Thanks > Prasanth > > > > On Apr 28, 2015, at 4:40 PM, Owen O'Malley <omal...@apache.org> wrote: > > > > It has been three years since Hadoop 2.0.0 was first released and I > believe > > that the vast majority of users that want to run Hive 1.x have moved over > > to Hadoop 2.x already. It will dramatically simplify Hive development if > we > > drop backwards compatibility with the old Hadoop 1.x line. > > > > Thanks, > > Owen > >
