You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-user@hadoop.apache.org by Jian Fang <ji...@gmail.com> on 2013/04/09 18:37:22 UTC
HDFS-4354 and HDFS-4416
Hi,
I saw HDFS-4354 and HDFS-4416 have been used in Cloudera's CDH4.2 to
improve short circuit read. Is there any plan to apply them to Hadoop 2.0.X
branches? Seems the short circuit read implementation in current Hadoop
2.0.x branches are quite different from HDFS-4354 and HDFS-4416.
Thanks in advance,
Jian
Re: HDFS-4354 and HDFS-4416
Posted by Jian Fang <ji...@gmail.com>.
Thanks Harsh for your quick response.
On Tue, Apr 9, 2013 at 11:45 AM, Harsh J <ha...@cloudera.com> wrote:
> These are part of the HDFS-347 branch which should be merged to trunk
> soon (and then hopefully, onto one of the upcoming 2.x releases, via a
> backport).
>
> On Tue, Apr 9, 2013 at 10:07 PM, Jian Fang
> <ji...@gmail.com> wrote:
> > Hi,
> >
> > I saw HDFS-4354 and HDFS-4416 have been used in Cloudera's CDH4.2 to
> improve
> > short circuit read. Is there any plan to apply them to Hadoop 2.0.X
> > branches? Seems the short circuit read implementation in current Hadoop
> > 2.0.x branches are quite different from HDFS-4354 and HDFS-4416.
> >
> > Thanks in advance,
> >
> > Jian
> >
>
>
>
> --
> Harsh J
>
Re: HDFS-4354 and HDFS-4416
Posted by Jian Fang <ji...@gmail.com>.
Thanks Harsh for your quick response.
On Tue, Apr 9, 2013 at 11:45 AM, Harsh J <ha...@cloudera.com> wrote:
> These are part of the HDFS-347 branch which should be merged to trunk
> soon (and then hopefully, onto one of the upcoming 2.x releases, via a
> backport).
>
> On Tue, Apr 9, 2013 at 10:07 PM, Jian Fang
> <ji...@gmail.com> wrote:
> > Hi,
> >
> > I saw HDFS-4354 and HDFS-4416 have been used in Cloudera's CDH4.2 to
> improve
> > short circuit read. Is there any plan to apply them to Hadoop 2.0.X
> > branches? Seems the short circuit read implementation in current Hadoop
> > 2.0.x branches are quite different from HDFS-4354 and HDFS-4416.
> >
> > Thanks in advance,
> >
> > Jian
> >
>
>
>
> --
> Harsh J
>
Re: HDFS-4354 and HDFS-4416
Posted by Jian Fang <ji...@gmail.com>.
Thanks Harsh for your quick response.
On Tue, Apr 9, 2013 at 11:45 AM, Harsh J <ha...@cloudera.com> wrote:
> These are part of the HDFS-347 branch which should be merged to trunk
> soon (and then hopefully, onto one of the upcoming 2.x releases, via a
> backport).
>
> On Tue, Apr 9, 2013 at 10:07 PM, Jian Fang
> <ji...@gmail.com> wrote:
> > Hi,
> >
> > I saw HDFS-4354 and HDFS-4416 have been used in Cloudera's CDH4.2 to
> improve
> > short circuit read. Is there any plan to apply them to Hadoop 2.0.X
> > branches? Seems the short circuit read implementation in current Hadoop
> > 2.0.x branches are quite different from HDFS-4354 and HDFS-4416.
> >
> > Thanks in advance,
> >
> > Jian
> >
>
>
>
> --
> Harsh J
>
Re: HDFS-4354 and HDFS-4416
Posted by Jian Fang <ji...@gmail.com>.
Thanks Harsh for your quick response.
On Tue, Apr 9, 2013 at 11:45 AM, Harsh J <ha...@cloudera.com> wrote:
> These are part of the HDFS-347 branch which should be merged to trunk
> soon (and then hopefully, onto one of the upcoming 2.x releases, via a
> backport).
>
> On Tue, Apr 9, 2013 at 10:07 PM, Jian Fang
> <ji...@gmail.com> wrote:
> > Hi,
> >
> > I saw HDFS-4354 and HDFS-4416 have been used in Cloudera's CDH4.2 to
> improve
> > short circuit read. Is there any plan to apply them to Hadoop 2.0.X
> > branches? Seems the short circuit read implementation in current Hadoop
> > 2.0.x branches are quite different from HDFS-4354 and HDFS-4416.
> >
> > Thanks in advance,
> >
> > Jian
> >
>
>
>
> --
> Harsh J
>
Re: HDFS-4354 and HDFS-4416
Posted by Harsh J <ha...@cloudera.com>.
These are part of the HDFS-347 branch which should be merged to trunk
soon (and then hopefully, onto one of the upcoming 2.x releases, via a
backport).
On Tue, Apr 9, 2013 at 10:07 PM, Jian Fang
<ji...@gmail.com> wrote:
> Hi,
>
> I saw HDFS-4354 and HDFS-4416 have been used in Cloudera's CDH4.2 to improve
> short circuit read. Is there any plan to apply them to Hadoop 2.0.X
> branches? Seems the short circuit read implementation in current Hadoop
> 2.0.x branches are quite different from HDFS-4354 and HDFS-4416.
>
> Thanks in advance,
>
> Jian
>
--
Harsh J
Re: HDFS-4354 and HDFS-4416
Posted by Harsh J <ha...@cloudera.com>.
These are part of the HDFS-347 branch which should be merged to trunk
soon (and then hopefully, onto one of the upcoming 2.x releases, via a
backport).
On Tue, Apr 9, 2013 at 10:07 PM, Jian Fang
<ji...@gmail.com> wrote:
> Hi,
>
> I saw HDFS-4354 and HDFS-4416 have been used in Cloudera's CDH4.2 to improve
> short circuit read. Is there any plan to apply them to Hadoop 2.0.X
> branches? Seems the short circuit read implementation in current Hadoop
> 2.0.x branches are quite different from HDFS-4354 and HDFS-4416.
>
> Thanks in advance,
>
> Jian
>
--
Harsh J
Re: HDFS-4354 and HDFS-4416
Posted by Harsh J <ha...@cloudera.com>.
These are part of the HDFS-347 branch which should be merged to trunk
soon (and then hopefully, onto one of the upcoming 2.x releases, via a
backport).
On Tue, Apr 9, 2013 at 10:07 PM, Jian Fang
<ji...@gmail.com> wrote:
> Hi,
>
> I saw HDFS-4354 and HDFS-4416 have been used in Cloudera's CDH4.2 to improve
> short circuit read. Is there any plan to apply them to Hadoop 2.0.X
> branches? Seems the short circuit read implementation in current Hadoop
> 2.0.x branches are quite different from HDFS-4354 and HDFS-4416.
>
> Thanks in advance,
>
> Jian
>
--
Harsh J
Re: HDFS-4354 and HDFS-4416
Posted by Harsh J <ha...@cloudera.com>.
These are part of the HDFS-347 branch which should be merged to trunk
soon (and then hopefully, onto one of the upcoming 2.x releases, via a
backport).
On Tue, Apr 9, 2013 at 10:07 PM, Jian Fang
<ji...@gmail.com> wrote:
> Hi,
>
> I saw HDFS-4354 and HDFS-4416 have been used in Cloudera's CDH4.2 to improve
> short circuit read. Is there any plan to apply them to Hadoop 2.0.X
> branches? Seems the short circuit read implementation in current Hadoop
> 2.0.x branches are quite different from HDFS-4354 and HDFS-4416.
>
> Thanks in advance,
>
> Jian
>
--
Harsh J