Unsubscribe please

On 17 Aug 2015 20:31, "Tao Jie (JIRA)" wrote: > Tao Jie created HADOOP-12331: > > > Summary: FSShell Delete and Rename should operate on symlinks > rather than their target > Key: HADOOP-12331 > URL: https://issues.ap

[jira] [Created] (HADOOP-12338) Improvement on MutableStat

Xianyin Xin created HADOOP-12338: Summary: Improvement on MutableStat Key: HADOOP-12338 URL: https://issues.apache.org/jira/browse/HADOOP-12338 Project: Hadoop Common Issue Type: Improvement

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

Allen Wittenauer created HADOOP-12337: - Summary: compile and resut of compile should probably be split Key: HADOOP-12337 URL: https://issues.apache.org/jira/browse/HADOOP-12337 Project: Hadoop Comm

[jira] [Created] (HADOOP-12336) github_jira_bridge doesn't work

Allen Wittenauer created HADOOP-12336: - Summary: github_jira_bridge doesn't work Key: HADOOP-12336 URL: https://issues.apache.org/jira/browse/HADOOP-12336 Project: Hadoop Common Issue Typ

[jira] [Created] (HADOOP-12335) Add exponential weighted moving average in metrics2.util

Xianyin Xin created HADOOP-12335: Summary: Add exponential weighted moving average in metrics2.util Key: HADOOP-12335 URL: https://issues.apache.org/jira/browse/HADOOP-12335 Project: Hadoop Common

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

I also think allowing merges as a way to uprev with trunk would be a good idea. AFAIK, git rebase works well when your branch is short-lived and contains a fairly small number of commits, but doesn't work so well if your branch is large. Also, the cost of rebase will only go up as time goes. On the

Re: IPv6 Feature branch

Absolutely. On Mon, Aug 17, 2015 at 5:04 PM, Elliott Clark wrote: > Nate (nkedel) and I have been working on IPv6 on Hadoop and HBase lately. > We're getting somewhere but there are a lot of different places that make > assumptions about network. That means there will be a good deal of follow >

IPv6 Feature branch

Nate (nkedel) and I have been working on IPv6 on Hadoop and HBase lately. We're getting somewhere but there are a lot of different places that make assumptions about network. That means there will be a good deal of follow on patches as we find more and more places that need some TLC. Would a featu

[jira] [Created] (HADOOP-12334) Change Mode Of Copy Operation of HBase WAL Archiving to bypass Azure Storage Throttling after retries

Gaurav Kanade created HADOOP-12334: -- Summary: Change Mode Of Copy Operation of HBase WAL Archiving to bypass Azure Storage Throttling after retries Key: HADOOP-12334 URL: https://issues.apache.org/jira/browse/HAD

[jira] [Created] (HADOOP-12333) UserGroupInformation method to log in and relogin with password

john lilley created HADOOP-12333: Summary: UserGroupInformation method to log in and relogin with password Key: HADOOP-12333 URL: https://issues.apache.org/jira/browse/HADOOP-12333 Project: Hadoop Com

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

I think we should allow merge-based workflows. I worked and am working in several big feature branches, including HDFS-2802 (>100 subtasks) and HDFS-7285 (currently already > 200 subtasks), and tried both the merge-based and rebase-based workflows. When the feature change becomes big, the rebase wi

[jira] [Created] (HADOOP-12332) UserGroupInformation.reloginFromKeytab() timeout can leave UGI in unusable state

john lilley created HADOOP-12332: Summary: UserGroupInformation.reloginFromKeytab() timeout can leave UGI in unusable state Key: HADOOP-12332 URL: https://issues.apache.org/jira/browse/HADOOP-12332 Pr

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

Hi all, I've thought about this topic more over the last week, and felt I should play devil's advocate for a merge workflow. A few comments: - The issue of merges "polluting history" is mainly an issue when using a github PR workflow, which results in one merge per PR. Clearly this is no

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

Thanks for the clarification Andrew. So is the proposal on the table squashing commits (on the feature branch) when we rebase the feature branch with the latest from trunk? How would the process work? A simple schematic example might be helpful in understanding the proposal. If the feature branch

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

@Sangjin, I believe this is covered by the [VOTE] I linked to above, key excerpt being: 3. Force-push on feature-branches is allowed. Before pulling in a feature, the feature-branch should be rebased on latest trunk and the changes applied to trunk through "git rebase --onto" or "git che

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

Just to be clear, are we discussing the process of uprev'ing the feature development branch with the latest from the trunk from time to time, or making the final merge of the feature branch onto the trunk? On Mon, Aug 17, 2015 at 10:21 AM, Steve Loughran wrote: > I haven't done a bit piece of wo

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

I haven't done a bit piece of work in the ASF code repo since the migration to git; though I have done it in the svn era. Currently with private git repos -anyone gets SCM control of their source -you can commit for your own reasons (about to make a change, want a private jenkins run, ...) and

[jira] [Created] (HADOOP-12331) FSShell Delete and Rename should operate on symlinks rather than their target

Tao Jie created HADOOP-12331: Summary: FSShell Delete and Rename should operate on symlinks rather than their target Key: HADOOP-12331 URL: https://issues.apache.org/jira/browse/HADOOP-12331 Project: Hado

[jira] [Created] (HADOOP-12330) Decouple smart-apply-patch from apache

Allen Wittenauer created HADOOP-12330: - Summary: Decouple smart-apply-patch from apache Key: HADOOP-12330 URL: https://issues.apache.org/jira/browse/HADOOP-12330 Project: Hadoop Common Is

[jira] [Resolved] (HADOOP-12328) Hadoop/MapReduce ignores hidden (dot) files

[ https://issues.apache.org/jira/browse/HADOOP-12328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-12328. --- Resolution: Won't Fix Closing this as won't fix. This is working as designed. Chan

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

See Changes: [kasha] YARN-3534. Collect memory/cpu usage on the node. (Inigo Goiri via kasha) [kasha] YARN-4055. Report node resource utilization in heartbeat. (Inigo Goiri via kasha)

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

See Changes: [kasha] YARN-3534. Collect memory/cpu usage on the node. (Inigo Goiri via kasha) [kasha] YARN-4055. Report node resource utilization in heartbeat. (Inigo Goiri via kasha) -- [.

[jira] [Created] (HADOOP-12329) io.file.buffer.size is only for SequenceFiles

Kun Yan created HADOOP-12329: Summary: io.file.buffer.size is only for SequenceFiles Key: HADOOP-12329 URL: https://issues.apache.org/jira/browse/HADOOP-12329 Project: Hadoop Common Issue Type: I