Re: Jira Lock Down Upgraded?

FYI - I pinged infra but the answer is only people with PMC/committer/contributor *Roles* on jira can comment. Hadoop's contributor list seems to be reached it's limit, so cannot be added. Hopefully we can restore after said May 12 2300 UTC. Maybe we should increase the contributor limit or add

Re: Jira Lock Down Upgraded?

Looks like side effects of this lock down are: 1. person (non-admin) who logged JIRA cannot comment on the JIRA 2. result of QA run cannot be posted onto JIRA (at least for hbase tests) :-( On Thu, May 12, 2016 at 3:10 PM, Andrew Wang wrote: > Try asking on

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

See Changes: [wang] HADOOP-13142. Change project version from 3.0.0 to 3.0.0-alpha1. -- [...truncated 5581 lines...] Running org.apache.hadoop.util.TestChunkedArrayList Tests run: 5,

[jira] [Resolved] (HADOOP-13142) Change project version from 3.0.0 to 3.0.0-alpha1

[ https://issues.apache.org/jira/browse/HADOOP-13142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang resolved HADOOP-13142. -- Resolution: Fixed Fix Version/s: 3.0.0-alpha1 Thanks for the review Colin, committed

Re: [VOTE] Merge feature branch HADOOP-12930

+1. I looked at the patches on the branch, wasn't too bad to review. As Allen said, there's some code movement, assorted other nice doc and shell fixups. Found one extra typo, which I added to HADOOP-13129. Best, Andrew On Wed, May 11, 2016 at 1:14 AM, Sean Busbey wrote:

Re: Compatibility guidelines for toString overrides

How about this idea: Define a new annotation "StableImplUnstableInterface" which means consumers can't assume stability but producers can't change things. Mark all toStrings with this annotation. Then, in a lazy fashion, as the need arises to change various toString methods, diligence can be

Re: Looking to a Hadoop 3 release

I am with Vinod on avoiding merging mostly_complete_branches to trunk since we are not shipping any release off it. If 3.x releases going off of trunk is going to help with this, I am fine with that approach. We should still make sure to keep trunk-incompat small and not include large features.

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

See - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org

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

See - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org

[jira] [Created] (HADOOP-13142) Change project version from 3.0.0 to 3.0.0-alpha1

Andrew Wang created HADOOP-13142: Summary: Change project version from 3.0.0 to 3.0.0-alpha1 Key: HADOOP-13142 URL: https://issues.apache.org/jira/browse/HADOOP-13142 Project: Hadoop Common

[jira] [Resolved] (HADOOP-9292) NullPointerException in httpfs tests

[ https://issues.apache.org/jira/browse/HADOOP-9292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-9292. -- Resolution: Cannot Reproduce Target Version/s: (was: ) Stale. >

[jira] [Resolved] (HADOOP-12093) pre-patch findbugs fails on a branch-based pre-commit runs

[ https://issues.apache.org/jira/browse/HADOOP-12093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-12093. --- Resolution: Cannot Reproduce > pre-patch findbugs fails on a branch-based

[jira] [Resolved] (HADOOP-9837) Hadoop Token Command

[ https://issues.apache.org/jira/browse/HADOOP-9837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-9837. -- Resolution: Implemented This looks like a dupe of HADOOP-12563. Closing as such. >

[jira] [Resolved] (HADOOP-13141) Mini HDFS Cluster fails to start on trunk

[ https://issues.apache.org/jira/browse/HADOOP-13141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang resolved HADOOP-13141. -- Resolution: Fixed > Mini HDFS Cluster fails to start on trunk >

[jira] [Created] (HADOOP-13141) Mini HDFS Cluster fails to start on trunk

Xiaobing Zhou created HADOOP-13141: -- Summary: Mini HDFS Cluster fails to start on trunk Key: HADOOP-13141 URL: https://issues.apache.org/jira/browse/HADOOP-13141 Project: Hadoop Common

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

See Changes: [jlowe] YARN-5053. More informative diagnostics when applications killed by a [aw] HADOOP-12581. ShellBasedIdMapping needs suport for Solaris (Alan -- [...truncated 3876

Re: Jira Lock Down Upgraded?

Try asking on infra.chat (Apache INFRA's hipchat). I was in that room earlier today, and they were working on the ongoing JIRA spam. On Thu, May 12, 2016 at 3:03 PM, Xiao Chen wrote: > Hello, > > I'm not sure if common-dev is the right contact list, please redirect me if >

[jira] [Resolved] (HADOOP-12435) Findbugs is broken on trunk

[ https://issues.apache.org/jira/browse/HADOOP-12435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-12435. --- Resolution: Won't Fix Target Version/s: (was: ) > Findbugs is broken on

[jira] [Resolved] (HADOOP-8497) Shell needs a way to list amount of physical consumed space in a directory

[ https://issues.apache.org/jira/browse/HADOOP-8497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-8497. -- Resolution: Duplicate Target Version/s: (was: ) > Shell needs a way to

Jira Lock Down Upgraded?

Hello, I'm not sure if common-dev is the right contact list, please redirect me if not. It seems the jira lock down is somehow being more strict? I was able to comment on an HDFS jira

[jira] [Resolved] (HADOOP-8854) Document backward incompatible changes between hadoop-1.x and 2.x

[ https://issues.apache.org/jira/browse/HADOOP-8854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-8854. -- Resolution: Won't Fix a) This is stale b) The Incompatible flag in JIRA + Apache Yetus

Re: Compatibility guidelines for toString overrides

As a downstream user of Hadoop, it would be much clearer if the toString functions included the appropriate annotations to say they're non-public, evolving, or whatever. Most downstream users of Hadoop aren't going to remember in-detail exceptions to the java API compatibility rules, once they

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

See Changes: [stevel] HADOOP-13028 add low level counter metrics for S3A; use in read -- [...truncated 5162 lines...] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.934

Re: Compatibility guidelines for toString overrides

> On 12 May 2016, at 17:57, Chris Nauroth wrote: > > I'm in favor of making a statement in the compatibility guidelines that > there is no guarantee of stability or backwards-compatibility for > toString() output. If a proposed patch introduces new dependencies on a >

Re: Compatibility guidelines for toString overrides

Hello Allen, The intent is not for this rule to override other compatibility rules, such as the important CLI output rule. It's also not intended to give us free reign to change existing toString() implementations without due diligence. If a patch changes an existing toString() implementation

Re: Compatibility guidelines for toString overrides

-1 without an audit of every toString usage. We have recent examples (e.g., HDFS-9732) where toString was used for output from CLI utilities. (which, IMO, should never have been done, but it’s too late now...) Output of CLI utilities is most definitely covered by the compatibility

Re: [DISCUSS] Set minimum version of Hadoop 3 to JDK8 (HADOOP-11858)

I’d like to bring YARN-4977 into attention for using Java 8. HADOOP-13083 does the maven change and in yarn-api there are ~5000 javadoc warnings. Li Lu > On May 10, 2016, at 08:32, Akira AJISAKA wrote: > > Hi developers, > > Before cutting 3.0.0-alpha RC, I'd

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

See Changes: [sjlee] YARN-4577. Enable aux services to have their own custom classpath/jar [stevel] MAPREDUCE-6639 Process hangs in LocatedFileStatusFetcher if [wang] Update project version to 3.0.0-alpha1-SNAPSHOT.

Re: Release numbering for 3.x leading up to GA

Hi folks, I think it's working, though it takes some time for the rename to propagate in JIRA. JIRA is also currently being hammered by spammers, which might be related. Anyway, the new "3.0.0-alpha1" version should be live for all four subprojects, so have at it! Best, Andrew On Thu, May 12,

[jira] [Resolved] (HADOOP-12844) Recover when S3A fails on IOException in read()

[ https://issues.apache.org/jira/browse/HADOOP-12844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved HADOOP-12844. - Resolution: Fixed Fix Version/s: 2.8.0 > Recover when S3A fails on IOException

[jira] [Resolved] (HADOOP-13058) S3A FS fails during init against a read-only FS if multipart purge is enabled

[ https://issues.apache.org/jira/browse/HADOOP-13058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved HADOOP-13058. - Resolution: Duplicate fixed in HADOOP-13028 > S3A FS fails during init against a

[jira] [Resolved] (HADOOP-13047) S3a Forward seek in stream length to be configurable

[ https://issues.apache.org/jira/browse/HADOOP-13047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved HADOOP-13047. - Resolution: Duplicate > S3a Forward seek in stream length to be configurable >

Re: Release numbering for 3.x leading up to GA

Thanks Andrew for driving. Sounds good. Go ahead please. Good luck :-) Regards, Uma On 5/12/16, 10:52 AM, "Andrew Wang" wrote: >Hi all, > >Sounds like we have general agreement on this release numbering scheme for >3.x. > >I'm going to attempt some mvn and JIRA

Re: Release numbering for 3.x leading up to GA

Hi all, Sounds like we have general agreement on this release numbering scheme for 3.x. I'm going to attempt some mvn and JIRA invocations to get the version numbers lined up for alpha1, wish me luck. Best, Andrew On Tue, May 3, 2016 at 9:52 AM, Roman Shaposhnik wrote:

Re: Compatibility guidelines for toString overrides

+1. Thanks, Sangjin On Thu, May 12, 2016 at 10:05 AM, Ravi Prakash wrote: > Thanks sounds reasonable Colin. +1 to not using toString() as an API > > On Thu, May 12, 2016 at 9:57 AM, Chris Nauroth > wrote: > > > I'm in favor of making a statement

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

See Changes: [stevel] HADOOP-13116 Jets3tNativeS3FileSystemContractTest does not run. -- [...truncated 5161 lines...] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.895

Re: [DISCUSS] Set minimum version of Hadoop 3 to JDK8 (HADOOP-11858)

+1 Masatake On 5/12/16 13:11, Gangumalla, Uma wrote: +1 Regards, Uma On 5/10/16, 2:24 PM, "Andrew Wang" wrote: +1 On Tue, May 10, 2016 at 12:36 PM, Ravi Prakash wrote: +1. Thanks for driving this Akira On Tue, May 10, 2016 at 10:25 AM,

Re: Compatibility guidelines for toString overrides

Thanks sounds reasonable Colin. +1 to not using toString() as an API On Thu, May 12, 2016 at 9:57 AM, Chris Nauroth wrote: > I'm in favor of making a statement in the compatibility guidelines that > there is no guarantee of stability or backwards-compatibility for >

Re: Compatibility guidelines for toString overrides

I'm in favor of making a statement in the compatibility guidelines that there is no guarantee of stability or backwards-compatibility for toString() output. If a proposed patch introduces new dependencies on a stable toString() output, such as for UI display or object serialization, then I'd

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

See - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Compatibility guidelines for toString overrides

Hi all, Recently a discussion came up on HADOOP-13028 about the wisdom of overloading S3AInputStream#toString to output statistics information. It's a difficult judgement for me to make, since I'm not aware of any compatibility guidelines for InputStream#toString. Do we have compatibility

[jira] [Resolved] (HADOOP-13078) switch hadoop-aws back to using the (heavy) amazon-sdk JAR

[ https://issues.apache.org/jira/browse/HADOOP-13078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved HADOOP-13078. - Resolution: Won't Fix > switch hadoop-aws back to using the (heavy) amazon-sdk JAR >

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

See Changes: [stevel] HADOOP-13122 Customize User-Agent header sent in HTTP requests by S3A. -- [...truncated 5581 lines...] Running org.apache.hadoop.util.TestChunkedArrayList Tests

[jira] [Created] (HADOOP-13139) Branch-2: S3a to use thread pool that blocks clients

Pieter Reuse created HADOOP-13139: - Summary: Branch-2: S3a to use thread pool that blocks clients Key: HADOOP-13139 URL: https://issues.apache.org/jira/browse/HADOOP-13139 Project: Hadoop Common

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

See - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org

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

See - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org

[jira] [Created] (HADOOP-13137) TraceAdmin should support Kerberized NameNode

Wei-Chiu Chuang created HADOOP-13137: Summary: TraceAdmin should support Kerberized NameNode Key: HADOOP-13137 URL: https://issues.apache.org/jira/browse/HADOOP-13137 Project: Hadoop Common

[jira] [Created] (HADOOP-13136) shade protobuf in the hadoop-common jar

Haohui Mai created HADOOP-13136: --- Summary: shade protobuf in the hadoop-common jar Key: HADOOP-13136 URL: https://issues.apache.org/jira/browse/HADOOP-13136 Project: Hadoop Common Issue Type: