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: [VOTE] Merge HADOOP-13345 (S3Guard feature branch)

+1 (non-binding) On Tue, Aug 22, 2017 at 10:24 AM, Steve Loughran wrote: > video being processed: https://www.youtube.com/watch? > v=oIe5Zl2YsLE=youtu.be > > its actually quite hard to show any benefits of s3guard on the command > line, so I've ended up showing some

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)

Re: [VOTE] Merge HADOOP-13345 (S3Guard feature branch)

video being processed: https://www.youtube.com/watch?v=oIe5Zl2YsLE=youtu.be its actually quite hard to show any benefits of s3guard on the command line, so I've ended up showing some scala tests where I turn on the (bundled) inconsistent AWS client to show how you then need to enable s3guard

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: hadoop 3 scripts & classpath setup

> On Aug 22, 2017, at 6:00 AM, Steve Loughran wrote: > > > I'm having problems getting the s3 classpath setup on the CLI & am trying to > work out what I'm doing wrong. > > > without setting things up, you can't expect to talk to blobstores > > hadoop fs -ls

[jira] [Created] (HADOOP-14801) s3guard diff demand creates a new table

Steve Loughran created HADOOP-14801: --- Summary: s3guard diff demand creates a new table Key: HADOOP-14801 URL: https://issues.apache.org/jira/browse/HADOOP-14801 Project: Hadoop Common

[jira] [Created] (HADOOP-14800) eliminate double stack trace on some s3guard CLI failures

Steve Loughran created HADOOP-14800: --- Summary: eliminate double stack trace on some s3guard CLI failures Key: HADOOP-14800 URL: https://issues.apache.org/jira/browse/HADOOP-14800 Project: Hadoop

hadoop 3 scripts & classpath setup

I'm having problems getting the s3 classpath setup on the CLI & am trying to work out what I'm doing wrong. without setting things up, you can't expect to talk to blobstores hadoop fs -ls wasb://something/ hadoop fs -ls s3a://landsat-pds/ That's expected. but what I can't do is get the aws

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

Re: [VOTE] Merge HADOOP-13345 (S3Guard feature branch)

+1 (binding) I'm happy with it; it's a great piece of work by (in no particular order): Chris Nauroth, Aaron Fabbri, Sean McRory & Mingliang Liu. plus a few bits in the corners where I got to break things while they were all asleep. Also deserving a mention: Thomas Demoor & Ewan Higgs @ WDC

[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