hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vinod Kumar Vavilapalli <vino...@apache.org>
Subject Re: Re-swizzle 2.3
Date Thu, 30 Jan 2014 20:42:10 GMT
That was quite some exercise, but I'm done with it now. Updated YARN's and MAPREDUCE's CHANGES.txt
on trunk, branch-2 and branch-2.3. Let me know if you find some inaccuracies.


On Jan 29, 2014, at 10:49 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org> wrote:

> Okay, I'll look at YARN and MR CHANGES.txt problems. Seems like they aren't addressed
> +Vinod
> On Jan 29, 2014, at 3:24 PM, Andrew Wang <andrew.wang@cloudera.com> wrote:
>> I just finished tuning up branch-2.3 and fixing up the HDFS and Common
>> CHANGES.txt in trunk, branch-2, and branch-2.3. I had to merge back a few
>> JIRAs committed between the swizzle and now where the fix version was 2.3
>> but weren't in branch-2.3.
>> I think the only two HDFS and Common JIRAs that are marked for 2.4 are
>> these:
>> HDFS-5842 Cannot create hftp filesystem when using a proxy user ugi and a
>> doAs on a secure cluster
>> HDFS-5781 Use an array to record the mapping between FSEditLogOpCode and
>> the corresponding byte value
>> Jing, these both look safe to me if you want to merge them back, or I can
>> just do it.
>> Thanks,
>> Andrew
>> On Wed, Jan 29, 2014 at 1:21 PM, Doug Cutting <cutting@apache.org> wrote:
>>> On Wed, Jan 29, 2014 at 12:30 PM, Jason Lowe <jlowe@yahoo-inc.com> wrote:
>>>> It is a bit concerning that the JIRA history showed that the target
>> version
>>>> was set at some point in the past but no record of it being cleared.
>>> Perhaps the version itself was renamed?
>>> Doug

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.

View raw message