on tasks in Phase I, we would label them with "erasure
>> coding" and maybe also set the target version as "2.9" for the convenience?
>> >>
>> >> -Original Message-
>> >> From: Jing Zhao [mailto:ji...@apache.org]
>> >> Sent: Tu
> coding" and maybe also set the target version as "2.9" for the convenience?
> >>
> >> -Original Message-
> >> From: Jing Zhao [mailto:ji...@apache.org]
> >> Sent: Tuesday, November 03, 2015 8:04 AM
> >> To: hdfs-dev@hadoop.apach
.@apache.org]
>> Sent: Tuesday, November 03, 2015 8:04 AM
>> To: hdfs-dev@hadoop.apache.org
>> Subject: Re: Erasure coding in branch-2 [Was Re: [VOTE] Merge HDFS-7285
>> (erasure coding) branch to trunk]
>>
>> +1 for the plan about Phase I & II.
>>
I don't really see the difference between 2.9 with a ton of scary changes
(EC is a lot more NN stuff than a usual release) and a 3.0.
What's the downside of getting a major version. It relaxes the compat a
little bit. It would allow some bake time before it's stable.
Put another way. I'm upgradin
Yes we can mostly likely help you. Please come over to dev@bigtop.
> On Nov 4, 2015, at 12:40 PM, Andrew Wang wrote:
>
> We used to get help from Bigtop when it comes to integration testing. Do we
> think that's possible for 2.8?
>
> On Wed, Nov 4, 2015 at 10:08 AM, Steve Loughran
> wrote:
>
We used to get help from Bigtop when it comes to integration testing. Do we
think that's possible for 2.8?
On Wed, Nov 4, 2015 at 10:08 AM, Steve Loughran
wrote:
>
> > On 2 Nov 2015, at 23:11, Vinod Vavilapalli
> wrote:
> >
> > Yes, I’ve already started looking at 2.8.0, that is exactly how I e
> On 2 Nov 2015, at 23:11, Vinod Vavilapalli wrote:
>
> Yes, I’ve already started looking at 2.8.0, that is exactly how I ended up
> with this discussion on the state of EC.
>
> +Vinod
>
>
> On Nov 2, 2015, at 3:02 PM, Haohui Mai
> mailto:ricet...@gmail.com>> wrote:
>
> Is it a good time t
y, November 03, 2015 8:04 AM
> > To: hdfs-dev@hadoop.apache.org
> > Subject: Re: Erasure coding in branch-2 [Was Re: [VOTE] Merge HDFS-7285
> (erasure coding) branch to trunk]
> >
> > +1 for the plan about Phase I & II.
> >
> > BTW, maybe out of the scope
, 2015 8:04 AM
> To: hdfs-dev@hadoop.apache.org
> Subject: Re: Erasure coding in branch-2 [Was Re: [VOTE] Merge HDFS-7285
> (erasure coding) branch to trunk]
>
> +1 for the plan about Phase I & II.
>
> BTW, maybe out of the scope of this thread, just want to mention we sho
: hdfs-dev@hadoop.apache.org
Subject: Re: Erasure coding in branch-2 [Was Re: [VOTE] Merge HDFS-7285
(erasure coding) branch to trunk]
If we use an umbrella JIRA to categorize all the ongoing EC work, that will let
us more easily change the target version later. For instance, if we decide to
bump
; -Original Message-
> From: Jing Zhao [mailto:ji...@apache.org]
> Sent: Tuesday, November 03, 2015 8:04 AM
> To: hdfs-dev@hadoop.apache.org
> Subject: Re: Erasure coding in branch-2 [Was Re: [VOTE] Merge HDFS-7285
> (erasure coding) branch to trunk]
>
> +1 for the pla
..@apache.org]
Sent: Tuesday, November 03, 2015 8:04 AM
To: hdfs-dev@hadoop.apache.org
Subject: Re: Erasure coding in branch-2 [Was Re: [VOTE] Merge HDFS-7285
(erasure coding) branch to trunk]
+1 for the plan about Phase I & II.
BTW, maybe out of the scope of this thread, just want to mention we
...@intel.com]
> > Sent: Tuesday, November 03, 2015 5:41 AM
> > To: hdfs-dev@hadoop.apache.org
> > Subject: Re: Erasure coding in branch-2 [Was Re: [VOTE] Merge HDFS-7285
> > (erasure coding) branch to trunk]
> >
> > +1 for EC to go into 2.9. Yes, 3.x woul
ugh release date.
>
> Regards,
> Kai
>
> -Original Message-
> From: Gangumalla, Uma [mailto:uma.ganguma...@intel.com]
> Sent: Tuesday, November 03, 2015 5:41 AM
> To: hdfs-dev@hadoop.apache.org
> Subject: Re: Erasure coding in branch-2 [Was Re: [VOTE] Merge HDFS-72
nguma...@intel.com]
Sent: Tuesday, November 03, 2015 5:41 AM
To: hdfs-dev@hadoop.apache.org
Subject: Re: Erasure coding in branch-2 [Was Re: [VOTE] Merge HDFS-7285
(erasure coding) branch to trunk]
+1 for EC to go into 2.9. Yes, 3.x would be long way to go when we plan
+to
have 2.8 and 2.9 rel
Yes, I’ve already started looking at 2.8.0, that is exactly how I ended up with
this discussion on the state of EC.
+Vinod
On Nov 2, 2015, at 3:02 PM, Haohui Mai
mailto:ricet...@gmail.com>> wrote:
Is it a good time to start the discussion on the issues of releasing 2.8?
t; wrote:
>>>>>>>
>>>>>>>> Branch has been merged to trunk, thanks again to everyone who
>>>>>>>>worked
>>>>> on
>>>>>>>> the
>>>>>>>> feature!
>>>>&g
feature!
>>>>>>>
>>>>>>> On Tue, Sep 29, 2015 at 10:44 PM, Zhe Zhang
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Thanks everyone who has participated in this discussion.
>>>>>>
;>>
> > > >>>>>>> Thanks everyone who has participated in this discussion.
> > > >>>>>>>
> > > >>>>>>> With 7 +1's (5 binding and 2 non-binding), and no -1, this vote
> > > >> has
>
oudera.com>
> > >>>>> wrote:
> > >>>>>
> > >>>>>> Branch has been merged to trunk, thanks again to everyone who
> worked
> > >>> on
> > >>>>>> the
> > >>>>>> feature!
> > >>>&
;>>>>> ---
> >>>>>>> Zhe Zhang
> >>>>>>>
> >>>>>>> On Thu, Sep 24, 2015 at 11:08 PM, Liu, Yi A
> >>>>>> wrote:
> >>>>>>>
> >>>>>>>> (Change i
binding and 2 non-binding), and no -1, this vote
>> has
>>>>>> passed.
>>>>>>> I will do a final 'git merge' with trunk and work with Andrew to
>>> merge
>>>>>> the
>>>>>>> branch to trunk. I&
> On 17 Oct 2015, at 03:04, Vinayakumar B wrote:
>
> Is anyone else also thinks that feature is ready to goto branch-2 as well?
>
> Its > 2 weeks EC landed on trunk. IMo Looks Its quite stable since then and
> ready to go in branch-2.
2 weeks on jenkins -given jenkin's persistent instability
> >> >
> > > >> > ---
> > > >> > Zhe Zhang
> > > >> >
> > > >> > On Thu, Sep 24, 2015 at 11:08 PM, Liu, Yi A
> > > >>wrote:
> > > >> >
> > > >> > > (Change i
t; ---
> > >> > Zhe Zhang
> > >> >
> > >> > On Thu, Sep 24, 2015 at 11:08 PM, Liu, Yi A
> > >>wrote:
> > >> >
> > >> > > (Change it to binding.)
> > >> > >
> > >> > > +1
> > >> >
> >> > >
> >> > > +1
> >> > > I have been involved in the development and code review on the
> >>feature
> >> > > branch. It's a great feature and I think it's ready to merge it into
> >> > trunk.
> >> &
gt; +1
>> > > I have been involved in the development and code review on the
>>feature
>> > > branch. It's a great feature and I think it's ready to merge it into
>> > trunk.
>> > >
>> > > Thanks all for the contribution.
>> > >
>> > > R
to trunk
> > >
> > > +1 (non-binding)
> > > I have been involved in the development and code review on the feature
> > > branch. It's a great feature and I think it's ready to merge it into
> > trunk.
> > >
> > > Thanks all for th
i Liu
> >
> >
> > -Original Message-----
> > From: Liu, Yi A
> > Sent: Friday, September 25, 2015 1:51 PM
> > To: hdfs-dev@hadoop.apache.org
> > Subject: RE: [VOTE] Merge HDFS-7285 (erasure coding) branch to trunk
> >
> > +1 (non-binding)
>
nks all for the contribution.
>
> Regards,
> Yi Liu
>
>
> -Original Message-
> From: Liu, Yi A
> Sent: Friday, September 25, 2015 1:51 PM
> To: hdfs-dev@hadoop.apache.org
> Subject: RE: [VOTE] Merge HDFS-7285 (erasure coding) branch to trunk
>
> +1 (non-binding)
&g
September 25, 2015 1:51 PM
To: hdfs-dev@hadoop.apache.org
Subject: RE: [VOTE] Merge HDFS-7285 (erasure coding) branch to trunk
+1 (non-binding)
I have been involved in the development and code review on the feature branch.
It's a great feature and I think it's ready to merge it into tr
apache.org]
Sent: Friday, September 25, 2015 12:21 PM
To: hdfs-dev@hadoop.apache.org
Subject: Re: [VOTE] Merge HDFS-7285 (erasure coding) branch to trunk
+1,
I've been involved starting from design and development of ErasureCoding. I
think phase 1 of this development is ready to be merged t
out and hope it helps.
> > Thanks!
> >
> > Regards,
> > Kai
> >
> > -Original Message-
> > From: Gangumalla, Uma [mailto:uma.ganguma...@intel.com]
> > Sent: Wednesday, September 23, 2015 8:50 AM
> > To: hdfs-dev@hadoop.apache.org; common-
sday, September 23, 2015 8:50 AM
> To: hdfs-dev@hadoop.apache.org; common-...@hadoop.apache.org
> Subject: Re: [VOTE] Merge HDFS-7285 (erasure coding) branch to trunk
>
> +1
>
> Great addition to HDFS. Thanks all contributors for the nice work.
>
> Regards,
> Uma
>
> On 9/22/15, 3:4
AM
To: hdfs-dev@hadoop.apache.org; common-...@hadoop.apache.org
Subject: Re: [VOTE] Merge HDFS-7285 (erasure coding) branch to trunk
+1
Great addition to HDFS. Thanks all contributors for the nice work.
Regards,
Uma
On 9/22/15, 3:40 PM, "Zhe Zhang" wrote:
>Hi,
>
>I'd like t
+1
Great addition to HDFS. Thanks all contributors for the nice work.
Regards,
Uma
On 9/22/15, 3:40 PM, "Zhe Zhang" wrote:
>Hi,
>
>I'd like to propose a vote to merge the HDFS-7285 feature branch back to
>trunk. Since November 2014 we have been designing and developing this
>feature under the
+1
I've been involved in design discussions and reviews on the branch, I think
we're ready to merge to trunk. Stability has looked good in cluster testing.
Many thanks to all the contributors for their hard work!
Best,
Andrew
On Tue, Sep 22, 2015 at 3:40 PM, Zhe Zhang wrote:
> Hi,
>
> I'd lik
Hi,
I'd like to propose a vote to merge the HDFS-7285 feature branch back to
trunk. Since November 2014 we have been designing and developing this
feature under the umbrella JIRAs HDFS-7285 and HADOOP-11264, and have
committed approximately 210 patches.
The HDFS-7285 feature branch was created to
38 matches
Mail list logo
