Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
HDFS >> mail # dev >> Re-swizzle 2.3


Copy link to this message
-
Re: Re-swizzle 2.3
Thanks for the link Arun, I went ahead and punted one HADOOP blocker, and
the remaining two HADOOP/HDFS looks like they're under active review.

Post-swizzle, it seems like most blockers for 2.4 would also apply to 2.3,
so I looked at that list too:

https://issues.apache.org/jira/issues/?filter=12326375&jql=project%20in%20(HADOOP%2C%20YARN%2C%20HDFS%2C%20MAPREDUCE)%20AND%20priority%20%3D%20Blocker%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20%22Target%20Version%2Fs%22%20%3D%20%222.4.0%22

YARN-1673 IIUC relates to the AHS, so is actually only in branch-2 and not
branch-2.3.

HADOOP-10048, Jason's comment says he's okay with it not being a blocker.

HDFS-5796 hasn't seen much action. Kihwal or Haohui, could you comment on
the importance/status? I don't have much context in this area.

Best,
Andrew

On Fri, Jan 31, 2014 at 4:29 PM, Arun C Murthy <[EMAIL PROTECTED]> wrote:

> Thanks Vinod, appreciate it!
>
> I think we are very close.
>
> Here is a handy ref. to the list of blockers:
> http://s.apache.org/hadoop-2.3.0-blockers
>
> I'd appreciate if folks can help expedite these fixes, and, equally
> importantly bring up others they feel should be blockers for 2.3.0.
>
> thanks,
> Arun
>
> On Jan 30, 2014, at 12:42 PM, Vinod Kumar Vavilapalli <[EMAIL PROTECTED]>
> wrote:
>
> > 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.
> >
> > Thanks,
> > +Vinod
> >
> > On Jan 29, 2014, at 10:49 PM, Vinod Kumar Vavilapalli <
> [EMAIL PROTECTED]> wrote:
> >
> >>
> >> Okay, I'll look at YARN and MR CHANGES.txt problems. Seems like they
> aren't addressed yet.
> >>
> >> +Vinod
> >>
> >>
> >> On Jan 29, 2014, at 3:24 PM, Andrew Wang <[EMAIL PROTECTED]>
> 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 <[EMAIL PROTECTED]>
> wrote:
> >>>>
> >>>> On Wed, Jan 29, 2014 at 12:30 PM, Jason Lowe <[EMAIL PROTECTED]>
> 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
> >>
> >
> >
> > --
> > 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.
> > <signature.asc>
>
> --
> 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