[jira] [Resolved] (HADOOP-12337) compile and resut of compile should probably be split

2015-08-18 Thread Allen Wittenauer (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-12337. --- Resolution: Duplicate Yup. Incorporating this into HADOOP-12257 so that scala builds

[DISCUSS] Proposal for allowing merge workflows on feature branches

2015-08-18 Thread Andrew Wang
Hi common-dev, Based on the prior [DISCUSS] thread, I've put together a new [VOTE] proposal which modifies the branch development practices edified by the [VOTE] when we switched from SVN to git [1]. This new proposal modifies the third and fourth points of the earlier [VOTE], copied here for your

[jira] [Resolved] (HADOOP-11019) Queued IPC calls are not aborted if the connection drops

2015-08-18 Thread Daryn Sharp (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daryn Sharp resolved HADOOP-11019. -- Resolution: Duplicate > Queued IPC calls are not aborted if the connection drops > ---

Re: [DISCUSS] git rebase vs. git merge for branch development

2015-08-18 Thread Sangjin Lee
One other (long shot) option might be to do git cherry-picks of all new *trunk* commits into the feature branch when you uprev. But I'm not sure if that will be a sustainable practice, given the number of commits that are happening on the trunk. Unless you're upreving very often (e.g. daily), this

[jira] [Created] (HADOOP-12341) patch file confuses test-patch

2015-08-18 Thread Allen Wittenauer (JIRA)
Allen Wittenauer created HADOOP-12341: - Summary: patch file confuses test-patch Key: HADOOP-12341 URL: https://issues.apache.org/jira/browse/HADOOP-12341 Project: Hadoop Common Issue Type

Re: [DISCUSS] git rebase vs. git merge for branch development

2015-08-18 Thread Andrew Wang
Sounds like we have a lot of support for also allowing merge workflows. Let me draft a proper proposal and go through the [DISCUSS] and [VOTE] process. One thing I think we should amend from the previous [VOTE] is using "git merge --no-ff" rather than "rebase --onto" for branch -> trunk integration

[jira] [Created] (HADOOP-12340) test-patch docker mode fails in downloading findbugs with curl

2015-08-18 Thread Kengo Seki (JIRA)
Kengo Seki created HADOOP-12340: --- Summary: test-patch docker mode fails in downloading findbugs with curl Key: HADOOP-12340 URL: https://issues.apache.org/jira/browse/HADOOP-12340 Project: Hadoop Common

[jira] [Created] (HADOOP-12339) Wrong help message about --curl-cmd option

2015-08-18 Thread Kengo Seki (JIRA)
Kengo Seki created HADOOP-12339: --- Summary: Wrong help message about --curl-cmd option Key: HADOOP-12339 URL: https://issues.apache.org/jira/browse/HADOOP-12339 Project: Hadoop Common Issue Type

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

2015-08-18 Thread Apache Jenkins Server
See Changes: [xyao] HDFS-8883. NameNode Metrics : Add FSNameSystem lock Queue Length. Contributed by Anu Engineer. [wang] HDFS-8713. Convert DatanodeDescriptor to use SLF4J logging. [wheat9] HDFS-6407. Add sorting and pagina

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

2015-08-18 Thread Apache Jenkins Server
See Changes: [xyao] HDFS-8883. NameNode Metrics : Add FSNameSystem lock Queue Length. Contributed by Anu Engineer. [wang] HDFS-8713. Convert DatanodeDescriptor to use SLF4J logging. [wheat9] HDFS-6407. Add sorting and pagination

Re: [DISCUSS] git rebase vs. git merge for branch development

2015-08-18 Thread Vinayakumar B
+1, I agree with the support for git-merge based workflows for large branch merge. I have experienced the pain of re-basing the entire branch HDFS-7285, just for verification though, and I found even a line change in trunk in core files ( ex: FSNameSystem.java, BlockManager.java ) makes it hard to