[jira] [Resolved] (HADOOP-10367) Hadoop 2.2 Building error

[ https://issues.apache.org/jira/browse/HADOOP-10367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haohui Mai resolved HADOOP-10367. - Resolution: Invalid > Hadoop 2.2 Building error > - > >

[jira] [Resolved] (HADOOP-10795) unale to build hadoop 2.4.1(redhat5.8 x64)

[ https://issues.apache.org/jira/browse/HADOOP-10795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haohui Mai resolved HADOOP-10795. - Resolution: Invalid > unale to build hadoop 2.4.1(redhat5.8 x64) > -

[jira] [Resolved] (HADOOP-11192) Change old subversion links to git

[ https://issues.apache.org/jira/browse/HADOOP-11192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haohui Mai resolved HADOOP-11192. - Resolution: Invalid site.xml no longer contains the svn information. > Change old subversion li

[jira] [Resolved] (HADOOP-11366) Fix findbug warnings after move to Java 7

[ https://issues.apache.org/jira/browse/HADOOP-11366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haohui Mai resolved HADOOP-11366. - Resolution: Duplicate It has been fixed in HADOOP-10477. > Fix findbug warnings after move to J

[jira] [Resolved] (HADOOP-11633) Convert remaining branch-2 .apt.vm files to markdown

[ https://issues.apache.org/jira/browse/HADOOP-11633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haohui Mai resolved HADOOP-11633. - Resolution: Fixed > Convert remaining branch-2 .apt.vm files to markdown > -

Re: about CHANGES.txt

I think the general consensus is don’t include the changes.txt file in your commit. It won’t be correct for both branches if such a commit is destined for both. (No, the two branches aren’t the same.) No, git log isn’t more accurate. The problems are: a) cherry picks b) branch mergers c) “who

[jira] [Created] (HADOOP-11716) Bump netty version to 4.1

Haohui Mai created HADOOP-11716: --- Summary: Bump netty version to 4.1 Key: HADOOP-11716 URL: https://issues.apache.org/jira/browse/HADOOP-11716 Project: Hadoop Common Issue Type: Bug

Re: about CHANGES.txt

Thanks Esteban, I assume this report gets info purely from the jira database, but not "git log" of a branch, right? I hope we get the info from "git log" of a release branch because that'd be more accurate. --Yongjun On Fri, Mar 13, 2015 at 3:11 PM, Esteban Gutierrez wrote: > JIRA already prov

Re: about CHANGES.txt

Thanks Sean, that'd be even better! --Yongjun On Fri, Mar 13, 2015 at 3:01 PM, Sean Busbey wrote: > So long as you include the issue number, you can automate pulling the type > from jira directly instead of putting it in the message. > > On Fri, Mar 13, 2015 at 4:49 PM, Yongjun Zhang > wrote:

Request wiki access

Hi, I would like to create a wiki page https://wiki.apache.org/hadoop/GSoC2015 to record the ideas for GSoC 2015. Your help on granting me the permissions to edit the wiki is appreciated. Thanks, Haohui

Re: about CHANGES.txt

JIRA already provides a report: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12327179&styleName=Html&projectId=12310240 cheers, esteban. -- Cloudera, Inc. On Fri, Mar 13, 2015 at 3:01 PM, Sean Busbey wrote: > So long as you include the issue number, you can automate pul

Re: about CHANGES.txt

So long as you include the issue number, you can automate pulling the type from jira directly instead of putting it in the message. On Fri, Mar 13, 2015 at 4:49 PM, Yongjun Zhang wrote: > Hi, > > I found that changing CHANGES.txt when committing a jira is error prone > because of the different s

about CHANGES.txt

Hi, I found that changing CHANGES.txt when committing a jira is error prone because of the different sections in the file, and sometimes we forget about changing this file. After all, git log would indicate the history of a branch. I wonder if we could switch to a new method: 1. When committing,

[jira] [Created] (HADOOP-11715) azureFs::getFileStatus doesn't check the file system scheme and thus could throw a misleading exception.

Brandon Li created HADOOP-11715: --- Summary: azureFs::getFileStatus doesn't check the file system scheme and thus could throw a misleading exception. Key: HADOOP-11715 URL: https://issues.apache.org/jira/browse/HADOO

[jira] [Created] (HADOOP-11714) Add more trace log4j messages to SpanReceiverHost

Colin Patrick McCabe created HADOOP-11714: - Summary: Add more trace log4j messages to SpanReceiverHost Key: HADOOP-11714 URL: https://issues.apache.org/jira/browse/HADOOP-11714 Project: Hadoop

[jira] [Resolved] (HADOOP-11712) Error : ExecuteStatement finished with operation state: CLOSED_STATE” :

[ https://issues.apache.org/jira/browse/HADOOP-11712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haohui Mai resolved HADOOP-11712. - Resolution: Not a Problem The jira system only logs bugs in the core hadoop. Please redirect the

[jira] [Created] (HADOOP-11712) Error : ExecuteStatement finished with operation state: CLOSED_STATE” :

ankush created HADOOP-11712: --- Summary: Error : ExecuteStatement finished with operation state: CLOSED_STATE” : Key: HADOOP-11712 URL: https://issues.apache.org/jira/browse/HADOOP-11712 Project: Hadoop Commo

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

See Changes: [xgong] YARN-3338. Exclude jline dependency from YARN. Contributed by Zhijie [szetszwo] HDFS-6833. DirectoryScanner should not register a deleting block with memory of DataNode. Contributed by Shinichi Yamashita [c

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

See Changes: [xgong] YARN-3338. Exclude jline dependency from YARN. Contributed by Zhijie [szetszwo] HDFS-6833. DirectoryScanner should not register a deleting block with memory of DataNode. Contributed by Shinichi Yamashit