Re: Branch merges and 3.0.0-beta1 scope

We should avoid turning this into a replay of Apache Hadoop 2.6.0 (and to a lesser degree, 2.7.0 and 2.8.0) where a bunch of last minute “experimental” features derail stability for a significantly long period of time.

Re: Map reduce sample program

On 8/19/17 3:28 AM, Remil Mohanan wrote: I am trying to pass multiple non key values from mapper to reducer. The only way to pass data from the mapper to the reducer is through passing key-values. One common trick is to designate a special key as the out-of-band information key and then use

Re: Branch merges and 3.0.0-beta1 scope

On 8/22/17 3:20 AM, Steve Loughran wrote: On 21 Aug 2017, at 22:22, Vinod Kumar Vavilapalli wrote: Steve, You can be strict & ruthless about the timelines. Anything that doesn’t get in by mid-September, as was originally planned, can move to the next release - whether

Re: [VOTE] Merge feature branch YARN-5355 (Timeline Service v2) to trunk

Such a great community effort - hats off, team! Thanks +Vinod > On Aug 21, 2017, at 11:32 PM, Vrushali Channapattan > wrote: > > Hi folks, > > Per earlier discussion [1], I'd like to start a formal vote to merge > feature branch YARN-5355 [2] (Timeline Service v.2)

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/500/ [Aug 21, 2017 6:08:38 PM] (manojpec) HDFS-11988. Verify HDFS Snapshots with open files captured are [Aug 21, 2017 6:48:51 PM] (arp) HDFS-12325. SFTPFileSystem operations should restore cwd. Contributed by

Re: Branch merges and 3.0.0-beta1 scope

> On 21 Aug 2017, at 22:22, Vinod Kumar Vavilapalli wrote: > > Steve, > > You can be strict & ruthless about the timelines. Anything that doesn’t get > in by mid-September, as was originally planned, can move to the next release > - whether it is feature work on branches

[VOTE] Merge feature branch YARN-5355 (Timeline Service v2) to trunk

Hi folks, Per earlier discussion [1], I'd like to start a formal vote to merge feature branch YARN-5355 [2] (Timeline Service v.2) to trunk. The vote will run for 7 days, and will end August 29 11:00 PM PDT. We have previously completed one merge onto trunk [3] and Timeline Service v2 has been

RE: Branch merges and 3.0.0-beta1 scope

IMHO, when we propose any feature branch merge, we might need to consider following aspects 1)Use cases 2) Pluggable ---> if it's not pluggable , give the reason 3) API Compatibility 4) Impact---> when it's enable 5) Performance 6) Stability 7) Test Sufficiency 8) Documentation Above points