Sure. Will do it that way.
Thanks the feedback.
Marton
On 10/12/19 7:27 PM, Vinod Kumar Vavilapalli wrote:
On Mon, Sep 23, 2019 at 4:02 PM Elek, Marton wrote:
As the overall feedback was positive (in fact many of the answers were
simple +1 votes) I don't think the thread should be repea
On Mon, Sep 23, 2019 at 4:02 PM Elek, Marton wrote:
> As the overall feedback was positive (in fact many of the answers were
> simple +1 votes) I don't think the thread should be repeated under
> [VOTE] subject. Therefore I call it for a lazy consensus.
>
Let's please not do this in the future.
17/19 05:48:32To:
hdfs-dev@hadoop.apache.org,
mapreduce-...@hadoop.apache.org, common-...@hadoop.apache.org,
yarn-...@hadoop.apache.org
Subject: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk
source tree
TLDR; I propose to move Ozone related code out from Hadoop trunk and
stor
gt;>
>> On Tue, Sep 17, 2019 at 9:58 AM Salvatore LaMendola (BLOOMBERG/ 731 LEX) <
>> slamendo...@bloomberg.net> wrote:
>>
>>> +1
>>>
>>> From: e...@apache.org At: 09/17/19 05:48:32To:
>> hdfs-dev@hadoop.apache.org,
>>> mapreduce-
+1 (non-binding)
BR,
Wanqiang Ji
On Tue, Sep 17, 2019 at 5:48 PM Elek, Marton wrote:
>
>
> TLDR; I propose to move Ozone related code out from Hadoop trunk and
> store it in a separated *Hadoop* git repository apache/hadoop-ozone.git
>
>
>
>
> When Ozone was adopted as a new Hadoop subproject i
+1 (non-binding)
On Fri, Sep 20, 2019 at 8:01 AM Rakesh Radhakrishnan
wrote:
> +1
>
> Rakesh
>
> On Fri, Sep 20, 2019 at 12:29 AM Aaron Fabbri wrote:
>
> > +1 (binding)
> >
> > Thanks to the Ozone folks for their efforts at maintaining good
> separation
> > with HDFS and common. I took a lot of
+1
Rakesh
On Fri, Sep 20, 2019 at 12:29 AM Aaron Fabbri wrote:
> +1 (binding)
>
> Thanks to the Ozone folks for their efforts at maintaining good separation
> with HDFS and common. I took a lot of heat for the unpopular opinion that
> they should be separate, so I am glad the process has worke
+1 (binding)
Thanks to the Ozone folks for their efforts at maintaining good separation
with HDFS and common. I took a lot of heat for the unpopular opinion that
they should be separate, so I am glad the process has worked out well for
both codebases. It looks like my concerns were addressed and
in that case,
+1 from me (binding)
On Wed, Sep 18, 2019 at 4:33 PM Elek, Marton wrote:
> > one thing to consider here as you are giving up your ability to make
> > changes in hadoop-* modules, including hadoop-common, and their
> > dependencies, in sync with your own code. That goes for file
+1.
Thanks,
Junping
Elek, Marton 于2019年9月17日周二 下午5:48写道：
>
>
> TLDR; I propose to move Ozone related code out from Hadoop trunk and
> store it in a separated *Hadoop* git repository apache/hadoop-ozone.git
>
>
>
>
> When Ozone was adopted as a new Hadoop subproject it was proposed[1] to
> be p
+1
> On Sep 17, 2019, at 2:49 AM, Elek, Marton wrote:
>
>
>
> TLDR; I propose to move Ozone related code out from Hadoop trunk and store it
> in a separated *Hadoop* git repository apache/hadoop-ozone.git
>
>
>
>
> When Ozone was adopted as a new Hadoop subproject it was proposed[1] to b
> one thing to consider here as you are giving up your ability to make
> changes in hadoop-* modules, including hadoop-common, and their
> dependencies, in sync with your own code. That goes for filesystem
contract
> tests.
>
> are you happy with that?
Yes. I think we can live with it.
Fortun
one thing to consider here as you are giving up your ability to make
changes in hadoop-* modules, including hadoop-common, and their
dependencies, in sync with your own code. That goes for filesystem contract
tests.
are you happy with that?
On Tue, Sep 17, 2019 at 10:48 AM Elek, Marton wrote:
>
lvatore LaMendola (BLOOMBERG/ 731 LEX)
> <
> > slamendo...@bloomberg.net> wrote:
> >
> > > +1
> > >
> > > From: e...@apache.org At: 09/17/19 05:48:32To:
> > hdfs-dev@hadoop.apache.org,
> > > mapreduce-...@hadoop.apache.org, common-...@hado
5:48:32To:
> hdfs-dev@hadoop.apache.org,
> > mapreduce-...@hadoop.apache.org, common-...@hadoop.apache.org,
> > yarn-...@hadoop.apache.org
> > Subject: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk
> > source tree
> >
> >
> > TLDR; I pr
net> wrote:
> +1
>
> From: e...@apache.org At: 09/17/19 05:48:32To: hdfs-dev@hadoop.apache.org,
> mapreduce-...@hadoop.apache.org, common-...@hadoop.apache.org,
> yarn-...@hadoop.apache.org
> Subject: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk
> source tr
apache.org,
> yarn-...@hadoop.apache.org
> Subject: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk
> source tree
>
>
> TLDR; I propose to move Ozone related code out from Hadoop trunk and
> store it in a separated *Hadoop* git repository apache/hadoop-ozone.git
>
>
> W
+1
From: e...@apache.org At: 09/17/19 05:48:32To: hdfs-dev@hadoop.apache.org,
mapreduce-...@hadoop.apache.org, common-...@hadoop.apache.org,
yarn-...@hadoop.apache.org
Subject: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk source tree
TLDR; I propose to move Ozone related
+1
—Anu
> On Sep 17, 2019, at 2:49 AM, Elek, Marton wrote:
>
>
>
> TLDR; I propose to move Ozone related code out from Hadoop trunk and store it
> in a separated *Hadoop* git repository apache/hadoop-ozone.git
>
>
>
>
> When Ozone was adopted as a new Hadoop subproject it was proposed[1]
TLDR; I propose to move Ozone related code out from Hadoop trunk and
store it in a separated *Hadoop* git repository apache/hadoop-ozone.git
When Ozone was adopted as a new Hadoop subproject it was proposed[1] to
be part of the source tree but with separated release cadence, mainly
beca
20 matches
Mail list logo
