Sorry for jumping in late into the fray of this discussion.
It seems Ozone is a large feature. I appreciate the development effort and
the desire to get this into the hands of users.
I understand the need to iterate quickly and to reduce overhead for
development.
I also agree that Hadoop can benef
That makes sense to me, after merge to trunk and branch 2, it probably
makes sense to create a new jira and feature branch for atsv2 additional
feature dev.
Cheers,
Joep
On Fri, Aug 25, 2017 at 3:05 PM, Vrushali C wrote:
> Hi Subru,
>
> Thanks for your vote and your response!
>
> Regarding you
+1 (non-binding) for the merge
@Vinod I hope that means a +1 from you as well!
Cheers,
Joep
On Tue, Aug 22, 2017 at 11:15 AM, Vinod Kumar Vavilapalli <
vino...@apache.org> wrote:
> Such a great community effort - hats off, team!
>
> Thanks
> +Vinod
>
> > On Aug 21, 2017, at 11:32 PM, Vrushali
Thanks Vrushali for being entirely open as to the current status of ATSv2.
I appreciate that we want to ensure things are tested at scale, and as you
said we are working on that right now on our clusters.
We have tested the feature to demonstrate it works at what we consider
moderate scale.
I thin
Hi Vinod,
We've gone through the various lists of upstream jiras and wanted to
provide our take on what we'd like to see in 2.6.1 release.
In addition, we have ~58 jiras (some a group of work such as DN maintenance
state) that we already have in production
in a pre-2.6 release. I've gone through a
Here are some of our thought on the discussions of the past few days with
respect to backwards compatibility.
In general at Twitter we're not necessarily against backwards incompatible
changes per se.
*It depends on the "Return on Pain". While it is hard to quantify the
returns in the a
+1 (non-binding)
Joep
On Fri, May 31, 2013 at 9:27 PM, Konstantin Boudnik wrote:
> All,
>
> I have created a release candidate (rc1) for hadoop-2.0.5-alpha that I
> would
> like to release.
>
> This is a stabilization release that includes fixed for a couple a of
> issues
> discovered in the t
Thanks for fixing Cos.
http://people.apache.org/~cos/hadoop-2.0.5-alpha-rc1/
looks good to me.
+1 (non-binding)
Thanks,
Joep
On Fri, May 31, 2013 at 8:25 PM, Konstantin Boudnik wrote:
> Ok, WRT HDFS-4646 - it is all legit and the code is in branch-2.0.4-alpha
> and
> later. It has been commit
Thanks for the hadoop-2.0.5-alpha RC0 Cos!
+1 (non-binding) in principle for a 2.0.5-alpha release.
Similar to Alejandro I see that:
/hadoop-2.0.5-alpha-src/hadoop-hdfs-project/README.txt (has 2.0.4 release
date missing):
Release 2.0.5-alpha - UNRELEASED
Release 2.0.4-alpha - UNRELEASED
/hadoop-
Different versions of the patch are supposed to have the same name, and
could be sorted by date.
A different name should be used to indicate the target branch.
See the "Naming your patch" section on
http://wiki.apache.org/hadoop/HowToContribute
Cheers,
Joep
On Fri, Dec 23, 2011 at 12:13 PM, Pat
10 matches
Mail list logo
