There are other such isolated and well understood bug-fixes that we pushed to 2.1.1 in the interesting of making progress with 2.1.0 and the corresponding API changes.
2.1.1 should happen soon enough after this. Thanks, +Vinod On Aug 16, 2013, at 4:22 PM, Roman Shaposhnik wrote: > What are the downsides of getting this fix into the 2.1? It appears > that the fix is pretty isolated and well understood. > > Thoughts? > > Thanks, > Roman. > > On Fri, Aug 16, 2013 at 3:04 PM, Kihwal Lee <kih...@yahoo-inc.com> wrote: >> I've changed the target version of HADOOP-9880 to 2.1.1. Please change it >> back, if you feel that it needs to be in 2.1.0-beta. >> >> >> Kihwal >> >> >> ________________________________ >> From: Kihwal Lee <kih...@yahoo-inc.com> >> To: Arun Murthy <a...@hortonworks.com>; "common-dev@hadoop.apache.org" >> <common-dev@hadoop.apache.org> >> Cc: "mapreduce-...@hadoop.apache.org" <mapreduce-...@hadoop.apache.org>; >> "hdfs-...@hadoop.apache.org" <hdfs-...@hadoop.apache.org>; >> "yarn-...@hadoop.apache.org" <yarn-...@hadoop.apache.org> >> Sent: Friday, August 16, 2013 4:55 PM >> Subject: Re: [VOTE] Release Apache Hadoop 2.1.0-beta >> >> >> It's your call, Arun. I.e. as long you believe rc2 meets the expectations >> and objectives of 2.1.0-beta. >> >> Kihwal >> >> >> ________________________________ >> From: Arun Murthy <a...@hortonworks.com> >> To: "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org> >> Cc: Kihwal Lee <kih...@yahoo-inc.com>; "mapreduce-...@hadoop.apache.org" >> <mapreduce-...@hadoop.apache.org>; "hdfs-...@hadoop.apache.org" >> <hdfs-...@hadoop.apache.org>; "yarn-...@hadoop.apache.org" >> <yarn-...@hadoop.apache.org> >> Sent: Friday, August 16, 2013 3:44 PM >> Subject: Re: [VOTE] Release Apache Hadoop 2.1.0-beta >> >> >> That makes sense too. >> >> >> On Aug 16, 2013, at 10:39 AM, Vinod Kumar Vavilapalli >> <vino...@hortonworks.com> wrote: >> >>> >>> We need to make a call on what blockers will be. From my limited >>> understanding, this doesn't seem like a API or a compatibility issue. Can >>> we not fix it in subsequent bug-fix releases? >>> >>> I do see a lot of follow up releases to 2.1.0. Getting this release out >>> will help downstream projects start testing with all the API stuff that has >>> already gone in 2.1.0. >>> >>> Thanks, >>> +Vinod >>> >>> On Aug 16, 2013, at 10:13 AM, Kihwal Lee wrote: >>> >>>> We have found HADOOP-9880, which prevents Namenode HA from running with >>>> security. >>>> >>>> Kihwal >>>> >>>> >>>> ________________________________ >>>> From: Arun C Murthy <a...@hortonworks.com> >>>> To: "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>; >>>> "hdfs-...@hadoop.apache.org" <hdfs-...@hadoop.apache.org>; >>>> "mapreduce-...@hadoop.apache.org" <mapreduce-...@hadoop.apache.org>; >>>> "yarn-...@hadoop.apache.org" <yarn-...@hadoop.apache.org> >>>> Sent: Thursday, August 15, 2013 4:15 PM >>>> Subject: [VOTE] Release Apache Hadoop 2.1.0-beta >>>> >>>> >>>> Folks, >>>> >>>> I've created a release candidate (rc2) for hadoop-2.1.0-beta that I would >>>> like to get released - this fixes the bugs we saw since the last go-around >>>> (rc1). >>>> >>>> The RC is available at: >>>> http://people.apache.org/~acmurthy/hadoop-2.1.0-beta-rc2/ >>>> The RC tag in svn is here: >>>> http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.1.0-beta-rc2 >>>> >>>> The maven artifacts are available via repository.apache.org. >>>> >>>> Please try the release and vote; the vote will run for the usual 7 days. >>>> >>>> thanks, >>>> Arun >>>> >>>> -- >>>> Arun C. Murthy >>>> Hortonworks Inc. >>>> http://hortonworks.com/ >>>> >>>> >>>> >>>> -- >>>> CONFIDENTIALITY NOTICE >>>> NOTICE: This message is intended for the use of the individual or entity to >>>> which it is addressed and may contain information that is confidential, >>>> privileged and exempt from disclosure under applicable law. If the reader >>>> of this message is not the intended recipient, you are hereby notified that >>>> any printing, copying, dissemination, distribution, disclosure or >>>> forwarding of this communication is strictly prohibited. If you have >>>> received this communication in error, please contact the sender immediately >>>> and delete it from your system. Thank You. >>> >>> >>> -- >>> CONFIDENTIALITY NOTICE >>> NOTICE: This message is intended for the use of the individual or entity to >>> which it is addressed and may contain information that is confidential, >>> privileged and exempt from disclosure under applicable law. If the reader >>> of this message is not the intended recipient, you are hereby notified that >>> any printing, copying, dissemination, distribution, disclosure or >>> forwarding of this communication is strictly prohibited. If you have >>> received this communication in error, please contact the sender immediately >>> and delete it from your system. Thank You. >> >> -- >> CONFIDENTIALITY NOTICE >> NOTICE: This message is intended for the use of the individual or entity to >> which it is addressed and may contain information that is confidential, >> privileged and exempt from disclosure under applicable law. If the reader >> of this message is not the intended recipient, you are hereby notified that >> any printing, copying, dissemination, distribution, disclosure or >> forwarding of this communication is strictly prohibited. If you have >> received this communication in error, please contact the sender immediately >> and delete it from your system. Thank You. -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
