hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tsz Wo Sze <szets...@yahoo.com>
Subject Re: VOTE: HDFS-347 merge
Date Tue, 05 Mar 2013 23:08:59 GMT
Hi Colin,

It is great to hear that you agree to keep HDFS-2246.  Please as well address my comments
posted on HDFS-347 and let me know once you have posted a new patch on HDFS-347.  Thanks
a lot!

BTW, you should conclude the VOTE you started and use a separated thread for other discussion
as Suresh mentioned earlier.  I hope you could use our convention on voting.  Otherwise,
it is hard for others to follow.


 From: Suresh Srinivas <suresh@hortonworks.com>
To: "hdfs-dev@hadoop.apache.org" <hdfs-dev@hadoop.apache.org> 
Sent: Wednesday, March 6, 2013 5:09 AM
Subject: Re: VOTE: HDFS-347 merge
Thanks Colin. Will check it out as soon as I can.

On Tue, Mar 5, 2013 at 12:24 PM, Colin McCabe <cmccabe@alumni.cmu.edu>wrote:

> On Tue, Feb 26, 2013 at 5:09 PM, Suresh Srinivas <suresh@hortonworks.com>
> wrote:
> >>
> >> Suresh, if you're willing to "support and maintain" HDFS-2246, do you
> >> have cycles to propose a patch to the HDFS-347 branch reintegrating
> >> HDFS-2246 with the simplifications you outlined? In your review, did
> >> you find anything else you'd like to address prior to the merge, or is
> >> this the only item? -C
> >
> >
> > Yes, I can work on adding HDFS-2246 back in HDFS-347 branch. I will get
> to
> > it
> > in a week or two, if that is okay.
> >
> > I have not looked at the patch closely. But I think any issues found
> could
> > be fixed in trunk and should not block the merge.
> Hi Suresh,
> HDFS-4538 adds the ability to use the old block reader in the HDFS-347
> branch.  Check it out.
> Colin

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message