Before deciding that, we should pool the user list to see if this would be too disruptive for anyone..
Ashish -----Original Message----- From: Ning Zhang [mailto:[email protected]] Sent: Thursday, July 29, 2010 12:18 PM To: <[email protected]> Subject: Re: Hive should start moving to the new hadoop mapreduce api. Maybe we should decide hive-0.7 as the last branch to support hadoop pre-0.20 API and later branches of Hive will be switched to the new hadoop API? On Jul 29, 2010, at 11:53 AM, Ashish Thusoo wrote: > Yes these are mutually exclusive. > > Ashish > > -----Original Message----- > From: Edward Capriolo [mailto:[email protected]] > Sent: Thursday, July 29, 2010 11:20 AM > To: [email protected] > Subject: Re: Hive should start moving to the new hadoop mapreduce api. > > Aren't these things mutually exclusive? > The new Map Reduce API appeared in 20. > Deprecating 17 seems reasonable, but we still have to support the old api for > 18 and 19 correct? > > On Thu, Jul 29, 2010 at 2:11 PM, Ashish Thusoo <[email protected]> wrote: >> +1 to this >> >> Ashish >> >> -----Original Message----- >> From: yongqiang he [mailto:[email protected]] >> Sent: Thursday, July 29, 2010 10:54 AM >> To: [email protected] >> Subject: Hive should start moving to the new hadoop mapreduce api. >> >> Hi all, >> >> In offline discussions when we fixing HIVE-1492, we think it maybe good now >> to start thinking to move Hive to use new MapReduce context API, and also >> start deprecating Hadoop-0.17.0 support in Hive. >> Basically the new MapReduce API gives Hive more control at runtime. >> >> Any thoughts on this? >> >> >> Thanks >>
