Re: When are incompatible changes acceptable (HDFS-12990)

(Re-sent. Just found that my previous email seems not delivered to common-dev.) > > The question is: how are we going to fix it?>> What do you propose? -C First of all, let's state clearly what is the problem about.  Please help me out if I have missed anything. The problem reported by

Re: Hadoop 3.1.0 release discussion

What's the status on resource profiles?  I believe there are still a couple of open JIRAs to rethink some of the design choices. Daniel On 1/17/18 11:33 AM, Wangda Tan wrote: Hi All, Since we're fast approaching previously proposed feature freeze date (Jan 30, about 13 days from today). If

Re: Hadoop 3.1.0 release discussion

HI Wangda, Thank you for the head-up mail. We are in the branch (HDFS-10285) and trying to push the tasks sooner before the deadline. Regards, Uma On 1/17/18, 11:35 AM, "Wangda Tan" wrote: Hi All, Since we're fast approaching previously proposed feature

[jira] [Reopened] (HADOOP-12751) While using kerberos Hadoop incorrectly assumes names with '@' to be non-simple

[ https://issues.apache.org/jira/browse/HADOOP-12751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko reopened HADOOP-12751: -- > While using kerberos Hadoop incorrectly assumes names with '@' to be >

[jira] [Created] (HADOOP-15178) Generalize NetUtils#wrapException to handle other subclasses with String Constructor.

Ajay Kumar created HADOOP-15178: --- Summary: Generalize NetUtils#wrapException to handle other subclasses with String Constructor. Key: HADOOP-15178 URL: https://issues.apache.org/jira/browse/HADOOP-15178

Re: What's the difference between branch-3 and branch-3.0?

I filed INFRA-15859 to have branch-3 deleted. Jason On Wed, Jan 17, 2018 at 1:23 PM, Eric Payne < eric.payne1...@yahoo.com.invalid> wrote: > +1 for removing the branch-3 branch. It should be done soon so more > confusion can be avoided. Thanks Jason for tracking this down. > -Eric > > >

Re: Hadoop 3.1.0 release discussion

Hi All, Since we're fast approaching previously proposed feature freeze date (Jan 30, about 13 days from today). If you've any features which live in a branch and targeted to 3.1.0, please reply this email thread. Ideally, we should finish branch merging before feature freeze date. Here's an

Re: What's the difference between branch-3 and branch-3.0?

+1 for removing the branch-3 branch. It should be done soon so more confusion can be avoided. Thanks Jason for tracking this down. -Eric From: Jason Lowe To: Hadoop Common ; ma...@cloudera.com Sent: Wednesday, January 17, 2018 12:42 PM

Re: I want to inquire about hadoop licence.

There is a licensing FAQ for that http://www.apache.org/foundation/license-faq.html#IsItFee .. Owen > On Jan 17, 2018, at 11:06, 파란구름 wrote: > > Dear in charge of the hadoop manager. > > Thank you for providing hadoop service. > I want to inquire about hadoop licence. >

I want to inquire about hadoop licence.

Dear in charge of the hadoop manager. Thank you for providing hadoop service. I want to inquire about hadoop licence. Recently, I'm making a computer project to use hadoop service. I know hadoop is open source software. If my project is commercialized by using hadoop, then should i pay a fee? If

Re: What's the difference between branch-3 and branch-3.0?

+1 on deleting branch-3. On Wed, Jan 17, 2018 at 10:42 AM, Jason Lowe wrote: > This was created accidentally when HDFS-11847 was committed. As such we > should delete the branch-3 branch and port over the commits that went into > branch-3 instead of branch-3.0. For the

Re: What's the difference between branch-3 and branch-3.0?

This was created accidentally when HDFS-11847 was committed. As such we should delete the branch-3 branch and port over the commits that went into branch-3 instead of branch-3.0. For the former, I'm assuming that requires an INFRA ticket since I would hope any committer would not have the

Re: What's the difference between branch-3 and branch-3.0?

IMHO,we no need to have *branch-3* still trunk moves.Shall we remove as it make confuses.?? Brahma Reddy Battula On Wed, Jan 17, 2018 at 9:41 PM, Jason Lowe wrote: > I recently noticed some committers posting commits to branch-3 and marking > the JIRA as fixed in

[jira] [Created] (HADOOP-15177) Update the release year to 2018

Akira Ajisaka created HADOOP-15177: -- Summary: Update the release year to 2018 Key: HADOOP-15177 URL: https://issues.apache.org/jira/browse/HADOOP-15177 Project: Hadoop Common Issue Type:

What's the difference between branch-3 and branch-3.0?

I recently noticed some committers posting commits to branch-3 and marking the JIRA as fixed in 3.0.1. I thought branch-3.0 was tracking 3.0.x releases, including branch-3.0.1 as of now, so I am confused what branch-3 is for. The versions in the poms between branch-3 and branch-3.0 both say they

[jira] [Created] (HADOOP-15176) Enhance IAM assumed role support in S3A client

Steve Loughran created HADOOP-15176: --- Summary: Enhance IAM assumed role support in S3A client Key: HADOOP-15176 URL: https://issues.apache.org/jira/browse/HADOOP-15176 Project: Hadoop Common

Apache Hadoop qbt Report: branch2+JDK7 on Linux/x86

For more details, see https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/107/ [Jan 16, 2018 3:31:02 AM] (rohithsharmaks) YARN-6736. Consider writing to both ats v1 & v2 from RM for smoother [Jan 16, 2018 10:59:13 AM] (brahma) HDFS-8693. refreshNamenodes does not support adding a