[jira] [Created] (HADOOP-13056) Print expected values when rejecting a server's determined principal

Harsh J created HADOOP-13056: Summary: Print expected values when rejecting a server's determined principal Key: HADOOP-13056 URL: https://issues.apache.org/jira/browse/HADOOP-13056 Project: Hadoop Common

Re: Looking to a Hadoop 3 release

Tx for your replies, Andrew. >> For exit criteria, how about we time box it? My plan was to do monthly > alphas through the summer, leading up to beta in late August / early Sep. > At that point we freeze and stabilize for GA in Nov/Dec. Time-boxing is a reasonable exit-criterion. > In this ca

Re: Looking to a Hadoop 3 release

> On Apr 22, 2016, at 6:10 PM, Vinod Kumar Vavilapalli > wrote: > > Nope. > > I’m proposing making a new 3.x release (as has been discussed in this thread) > off today’s trunk (instead of creating a fresh branch-3) and create a new > trunk-incompt where incompatible changes that we don’t wan

Re: Looking to a Hadoop 3 release

Great comments Vinod, thanks for replying. Since trunk is a superset of branch-2.8, I think the two efforts are mostly aligned. The 2.8 blockers are likely also 3.0 blockers. For example, the create-release and L&N JIRAs I mentioned are in this camp. The difference between the two is the expectati

Re: Looking to a Hadoop 3 release

Nope. I’m proposing making a new 3.x release (as has been discussed in this thread) off today’s trunk (instead of creating a fresh branch-3) and create a new trunk-incompt where incompatible changes that we don’t want in 3.x go. This is mainly to avoid repeating the “we are not releasing 3.x of

Re: Looking to a Hadoop 3 release

> On Apr 22, 2016, at 5:38 PM, Vinod Kumar Vavilapalli > wrote: > > On an unrelated note, offline I was pitching to a bunch of contributors > another idea to deal with rotting trunk post 3.x: *Make 3.x releases off of > trunk directly*. > > What this gains us is that > - Trunk is always near

Re: Looking to a Hadoop 3 release

Hi, While welcoming the push for alphas, i think we should set some exit criteria. Otherwise, I can imagine us doing 3/4/5 alpha releases, and then getting restless about calling it beta or GA of whatever. Essentially, instead of today’s questions as to "why we aren’t doing a 3.x release", we’d

Re: Looking to a Hadoop 3 release

I kind of echo Junping’s comment too. While 2.8 and 3.0 don’t need to be serialized in theory, in practice I’m desperately looking for help on 2.8.0. We haven’t been converging on 2.8.0 what with 50+ blocker / critical patches still unfinished. If postponing 3.x alpha to after a 2.8.0 alpha mea

Re: [Release thread] 2.8.0 release activities

We are not converging - there’s still 58 more. I need help from the community in addressing / review 2.8.0 blockers. If folks can start with reviewing Patch available tickets, that’ll be great. Thanks +Vinod > On Apr 4, 2016, at 2:16 PM, Vinod Kumar Vavilapalli > wrote: > > Here we go again

Jenkins build is back to normal : Hadoop-common-trunk-Java8 #1383

See

Jenkins build is back to normal : Hadoop-Common-trunk #2668

See

Build failed in Jenkins: Hadoop-common-trunk-Java8 #1382

See Changes: [kihwal] HADOOP-13052. ChecksumFileSystem mishandles crc file permissions. -- [...truncated 5548 lines...] Running org.apache.hadoop.util.TestVersionUtil Tests run: 1, Fail

Re: Commit History Edit Alert

FWIW, the Hadoop team at Cloudera, in the past, allowed force pushes for our internal repo. It was common practice to email rest of the team when force-pushing to make sure we don't lose commits. It was quite painful, and we decided to disallow force pushes and life has gotten much better. PS: We

Re: Commit History Edit Alert

Owen, I agree force-pushes likely make for cleaner history, but they also allow losing commits in case of race conditions. Since the previous decision of disabling force pushes was discussed in a DISCUSS thread and others might want to weigh in with their opinions, mind starting a DISCUSS thread fo

Build failed in Jenkins: Hadoop-Common-trunk #2667

See Changes: [wangda] YARN-4846. Fix random failures for -- [...truncated 5147 lines...] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.327 sec - in org.apache.hadoop.util

Build failed in Jenkins: Hadoop-common-trunk-Java8 #1381

See Changes: [wangda] YARN-4846. Fix random failures for -- [...truncated 5574 lines...] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.697 sec - in org.apache.hadoo

Re: Commit History Edit Alert

In my opinion, prohibiting forced updates causes more pain than it helps. The much more important part is that someone should make tags for the recent releases in the "rel/*" namespace so that they can't be modified. I'd suggest at least: release-2.6.4 release-2.7.2 .. Owen On Fri, Apr 22, 2016

Re: Commit History Edit Alert

Recent changes to branch policies have affected this. Our trunk seems protected, but not branch-* branches. I had filed INFRA-11236 to address this. I can't ping on the JIRA anymore because comments from non-contributors are disabled. To prevent unintentional major messes, it is highly recommended

Build failed in Jenkins: Hadoop-common-trunk-Java8 #1380

See Changes: [raviprak] Revert "HADOOP-12563. Updated utility (dtutil) to create/modify token -- [...truncated 5564 lines...] Running org.apache.hadoop.fs.contract.ftp.TestFTPContractOp

Jenkins build is back to normal : Hadoop-Common-trunk #2666

See

[jira] [Created] (HADOOP-13055) Implement linkMergeSlash for ViewFs

Zhe Zhang created HADOOP-13055: -- Summary: Implement linkMergeSlash for ViewFs Key: HADOOP-13055 URL: https://issues.apache.org/jira/browse/HADOOP-13055 Project: Hadoop Common Issue Type: New Fea

Build failed in Jenkins: Hadoop-common-trunk-Java8 #1379

See Changes: [kihwal] HDFS-9555. LazyPersistFileScrubber should still sleep if there are -- [...truncated 5554 lines...] Running org.apache.hadoop.util.TestVersionUtil Tests run: 1, Fai

[jira] [Reopened] (HADOOP-12563) Updated utility to create/modify token files

[ https://issues.apache.org/jira/browse/HADOOP-12563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash reopened HADOOP-12563: --- > Updated utility to create/modify token files > >

[jira] [Created] (HADOOP-13054) Use proto delimited IO to fix tests broken by HADOOP-12563

Matthew Paduano created HADOOP-13054: Summary: Use proto delimited IO to fix tests broken by HADOOP-12563 Key: HADOOP-13054 URL: https://issues.apache.org/jira/browse/HADOOP-13054 Project: Hadoop C

Build failed in Jenkins: Hadoop-Common-trunk #2665

See Changes: [kihwal] HDFS-9555. LazyPersistFileScrubber should still sleep if there are -- [...truncated 5147 lines...] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.181

[jira] [Created] (HADOOP-13053) FS Shell should use File system API, not FileContext

Eric Badger created HADOOP-13053: Summary: FS Shell should use File system API, not FileContext Key: HADOOP-13053 URL: https://issues.apache.org/jira/browse/HADOOP-13053 Project: Hadoop Common

[jira] [Created] (HADOOP-13052) ChecksumFileSystem mishandles crc file permissions

Daryn Sharp created HADOOP-13052: Summary: ChecksumFileSystem mishandles crc file permissions Key: HADOOP-13052 URL: https://issues.apache.org/jira/browse/HADOOP-13052 Project: Hadoop Common

[jira] [Created] (HADOOP-13051) Test for special characters in path being respected during globPaths

Harsh J created HADOOP-13051: Summary: Test for special characters in path being respected during globPaths Key: HADOOP-13051 URL: https://issues.apache.org/jira/browse/HADOOP-13051 Project: Hadoop Common

Jenkins build is back to normal : Hadoop-common-trunk-Java8 #1378

See

Re: Commit History Edit Alert

Thanks for the clarification, Andrew. Yes, I'll add a comment about the results of my "testing". :) On Fri, Apr 22, 2016 at 2:06 AM, Andrew Wang wrote: > Squashing means force pushing, so please don't do that per ASF policies. > The normal recommendation is just not to fix it, commit message ty

[jira] [Resolved] (HADOOP-13009) add option for lazy open() on s3a

[ https://issues.apache.org/jira/browse/HADOOP-13009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved HADOOP-13009. - Resolution: Invalid Fix Version/s: 2.8.0 S3A doesn't open the input stream; hasn'

[jira] [Created] (HADOOP-13050) Upgrade to AWS SDK 10.10+ for Java 8u60+

Steve Loughran created HADOOP-13050: --- Summary: Upgrade to AWS SDK 10.10+ for Java 8u60+ Key: HADOOP-13050 URL: https://issues.apache.org/jira/browse/HADOOP-13050 Project: Hadoop Common Issu

Slack channel for Hadoop developers

Hi, I created slack channel for Hadoop community unofficially and experimentally: https://hadoopdev.slack.com/ I know that there is IRC channel and it's good to log. However, Slack is very also good tool to join easily and have a communication interactively. It will be also useful to join followi