Re: [DISCUSS] Branch Proposal: HADOOP 15407: ABFS

There's not a lot of (required) ceremony. Any committer can create the branch, including branch committers after the PMC adds them (see bylaws [1]). -C [1]: http://hadoop.apache.org/bylaws.html On Thu, May 17, 2018 at 9:16 AM, Steve Loughran wrote: > Now, what's next? I

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

]. -C [1]: https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/ On Tue, May 15, 2018 at 10:27 AM, Allen Wittenauer <a...@effectivemachines.com> wrote: > >> On May 15, 2018, at 10:16 AM, Chris Douglas <cdoug...@apache.org> wrote: >> >> They've been

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

They've been failing for a long time. It can't install bats, and that's fatal? -C On Tue, May 15, 2018 at 9:43 AM, Allen Wittenauer wrote: > > > FYI: > > I’m going to disable the branch-2 nightly jobs. >

Re: Apache Hadoop qbt Report: trunk+JDK8 on Windows/x64

Thanks, Allen. On Thu, Mar 15, 2018 at 10:20 AM, Iñigo Goiri wrote: >> * It ALWAYS applies HADOOP-14667.05.patch prior to running. As a result, >> this is only set up for trunk with no parameterization to run other >> branches. I tried to get this running in my environment a

Re: Cleaning up the Hadoop dist area

gt; stable > stable2 > > I also deleted the obsolete md5 files and added the preferred sha256 files. > > .. Owen > > On Mon, Mar 5, 2018 at 3:23 PM, Chris Douglas <cdoug...@apache.org> wrote: > >> On Mon, Mar 5, 2018 at 1:24 PM, Owen O'Malley <owen.omal...@gm

Re: [EVENT] HDFS Bug Bash: March 12

gt; per-meetup-charge issue, but will double check. Let me know if there are > more meetups planned in the near future and we can use this. > > Thanks > +Vinod > > On Mar 6, 2018, at 7:48 PM, Chris Douglas <cdoug...@apache.org> wrote: > > Found a meetup alterna

Re: [EVENT] HDFS Bug Bash: March 12

We're using a shared doc to track work in progress, PA/review ready, and committed [1]. -C [1]: https://s.apache.org/RLlx On Mon, Mar 12, 2018 at 9:17 AM, Chris Douglas <cdoug...@apache.org> wrote: > On Fri, Mar 9, 2018 at 7:52 PM, 俊平堵 <junping...@apache.org> wrote: >>

Re: [EVENT] HDFS Bug Bash: March 12

in the project. -C [1]: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=75965105 > 2018-03-05 16:03 GMT-08:00 Chris Douglas <cdoug...@apache.org>: > >> [Cross-posting, as this affects the rest of the project] >> >> Hey folks- >> >>

Re: [EVENT] HDFS Bug Bash: March 12

ng else I > can help here. > > Thanks, > > Junping > > 2018-03-05 16:03 GMT-08:00 Chris Douglas <cdoug...@apache.org>: > >> [Cross-posting, as this affects the rest of the project] >> >> Hey folks- >> >> As discussed last month [1],

Re: [EVENT] HDFS Bug Bash: March 12

05 On Tue, Mar 6, 2018 at 7:48 PM, Chris Douglas <cdoug...@apache.org> wrote: > Found a meetup alternative (thanks Subru): > https://meetingstar.io/event/fk13172f1d75KN > > So we can get a rough headcount, please add (local) if you plan to > attend in-person. -C > > &g

[EVENT] HDFS Bug Bash: March 12

[Cross-posting, as this affects the rest of the project] Hey folks- As discussed last month [1], the HDFS build hasn't been healthy recently. We're dedicating a bug bash to stabilize the build and address some longstanding issues with our unit tests. We rely on our CI infrastructure to keep the

Re: Cleaning up the Hadoop dist area

On Mon, Mar 5, 2018 at 1:24 PM, Owen O'Malley wrote: > The Apache Release Process > https://www.apache.org/legal/release-policy.html says > that we should only keep the latest release on each branch. That would take > us to: > > >- hadoop-1.2.1 >- hadoop-2.6.5 >

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

branch-3 has reappeared. Filed INFRA-16086 [1]. -C [1]: https://issues.apache.org/jira/browse/INFRA-16086 On Wed, Jan 17, 2018 at 12:32 PM, Jason Lowe wrote: > I filed INFRA-15859 to have branch-3 deleted. > > Jason > > On Wed, Jan 17, 2018 at 1:23 PM, Eric Payne < >

[jira] [Created] (HADOOP-15251) Upgrade surefire version in branch-2

Chris Douglas created HADOOP-15251: -- Summary: Upgrade surefire version in branch-2 Key: HADOOP-15251 URL: https://issues.apache.org/jira/browse/HADOOP-15251 Project: Hadoop Common Issue

[jira] [Resolved] (HADOOP-14077) Improve the patch of HADOOP-13119

[ https://issues.apache.org/jira/browse/HADOOP-14077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved HADOOP-14077. Resolution: Fixed This has already been part of a release. Please leave it resolved

Re: Apache Hadoop 3.0.1 Release plan

On Fri, Feb 2, 2018 at 10:22 AM, Arpit Agarwal wrote: > Do you plan to roll an RC with an uncommitted fix? That isn't the right > approach. The fix will be committed to the release branch. We'll vote on the release, and if it receives a majority of +1 votes then it

Re: [VOTE] Merge YARN-6592 feature branch to trunk

+1 Looking forward to this. -C On Fri, Jan 26, 2018 at 7:28 AM, Arun Suresh wrote: > Hello yarn-dev@ > > Based on the positive feedback from the DISCUSS thread [1], I'd like to > start a formal vote to merge YARN-6592 [2] to trunk. The vote will run for 5 > days, and will end

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

and 3.0.1 are compatible. How could we explain 3.0.0 and 3.0.1 are >> incompatible due to convenience?3.2) Revert it in 4.0.0. There is no >> compatibility issue since 3.0.0 and 4.0.0 are allowed to have incompatible >> changes according to our policy. >> Since compati

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

le to 3.0.0. If the "bug" is that serious, why not fixing it in >4.0.0 and declare 3.x as dead? >- It seems obvious that no one has seriously tested it so that the >problem is not uncovered until now. Are there bugs in our current release >procedure? > > > Thanks &g

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

oth negative side > effects of reverting as well as incompatible minor release change. Thanks > > Regards, > Eric > > From: larry mccay <lmc...@apache.org> > Date: Wednesday, January 10, 2018 at 10:53 AM > To: Daryn Sharp <da...@oath.com> > Cc: "Aaron T. Myers

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

Particularly since 9820 isn't in the contiguous range of ports in HDFS-9427, is there any value in this change? Let's change it back to prevent the disruption to users, but downstream projects should treat this as a bug in their tests. Please open JIRAs in affected projects. -C On Tue, Jan 9,

Re: Missing some trunk commit history

trunk, it might be more efficient for analyze bugs for > pre-commit builds. > > regards, > Eric > > On Thu, Dec 14, 2017 at 6:52 PM, Chris Douglas <cdoug...@apache.org> wrote: > >> Eric- >> >> What problem are you trying to solve? Most of us unders

Re: Missing some trunk commit history

ks best for maintenance branches. However, I am not > convinced that rebase + merge strategy is the efficient way to manage trunk > stability. Is there be a better way to manage this? Probably, we can > recommend trunk to use merge without rebase, but maintenance branches apply > rebase +

Re: Missing some trunk commit history

s to find the root cause. IMHO, I think the number of clicks between > pagination vs drop down on github branch selection, the later seems more > work, but it is usually less clicks for feature branches that lived for a > couple months. > > Regards, > Eric > > On 12/14/1

Re: Missing some trunk commit history

I'd rather have the history. Otherwise tools like blame point only to a parent/umbrella JIRA, not the issue where the change was discussed. We can force a merge commit so it's clear the branch was developed outside the mainline. -C On Thu, Dec 14, 2017 at 1:18 PM, Eric Yang

[jira] [Created] (HADOOP-15106) FileSystem::open(PathHandle) should throw a specific exception on validation failure

Chris Douglas created HADOOP-15106: -- Summary: FileSystem::open(PathHandle) should throw a specific exception on validation failure Key: HADOOP-15106 URL: https://issues.apache.org/jira/browse/HADOOP-15106

[jira] [Resolved] (HADOOP-15102) HADOOP-14831

[ https://issues.apache.org/jira/browse/HADOOP-15102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved HADOOP-15102. Resolution: Invalid > HADOOP-14831 > > > Key:

[jira] [Created] (HADOOP-15080) Cat-X transitive dependency on org.json library via json-lib

Chris Douglas created HADOOP-15080: -- Summary: Cat-X transitive dependency on org.json library via json-lib Key: HADOOP-15080 URL: https://issues.apache.org/jira/browse/HADOOP-15080 Project: Hadoop

Re: [VOTE] Release Apache Hadoop 2.9.0 (RC3)

+1 (binding) Verified source tarball. Checksum and signature match, built from source, ran some unit tests. Skimmed NOTICE/LICENSE. -C On Mon, Nov 13, 2017 at 4:10 PM, Arun Suresh wrote: > Hi Folks, > > Apache Hadoop 2.9.0 is the first release of Hadoop 2.9 line and will be

Re: [VOTE] Release Apache Hadoop 2.9.0 (RC0)

The labor required for these release formalisms is exceeding their value. Our minor releases have more bugs than our patch releases (we hope), but every consumer should understand how software versioning works. Every device I own has bugs on major OS updates. That doesn't imply that every minor

[jira] [Created] (HADOOP-14992) Upgrade Avro patch version

Chris Douglas created HADOOP-14992: -- Summary: Upgrade Avro patch version Key: HADOOP-14992 URL: https://issues.apache.org/jira/browse/HADOOP-14992 Project: Hadoop Common Issue Type

Re: [DISCUSS] HADOOP-9122 Add power mock library for writing better unit tests

rvices in > Hadoop-yarn-services-api project. > Without ability to inject fault into the system, it is harder to test > negative cases. However, I found it difficult to attempt this in Hadoop code > base. Suggestion? > > Regards, > Eric > > On 10/2/17, 3:09 PM, "Chris

[jira] [Created] (HADOOP-14986) Enforce JDK limitations

Chris Douglas created HADOOP-14986: -- Summary: Enforce JDK limitations Key: HADOOP-14986 URL: https://issues.apache.org/jira/browse/HADOOP-14986 Project: Hadoop Common Issue Type: Bug

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

Sean/Junping- Ignoring the epistemology, it's a problem. Let's figure out what's causing memory to balloon and then we can work out the appropriate remedy. Is this reproducible outside the CI environment? To Junping's point, would YETUS-561 provide more detailed information to aid debugging? -C

Re: [VOTE] Release Apache Hadoop 2.8.2 (RC1)

+1 (binding) Looked through the src distribution. Checksum, signatures match, ran some of the unit tests. Also checked the site docs; thanks for updating the Docker container security docs. Thanks, Junping. -C On Thu, Oct 19, 2017 at 5:42 PM, Junping Du wrote: > Hi folks,

Re: [DISCUSS] HADOOP-9122 Add power mock library for writing better unit tests

e-opening this issue. > > Regards, > Eric > > From: Steve Loughran <ste...@hortonworks.com> > Date: Sunday, October 1, 2017 at 12:36 PM > To: Eric Yang <ey...@hortonworks.com> > Cc: Andrew Wang <andrew.w...@cloudera.com>, Chris Douglas > <cdoug...@apac

Re: [DISCUSS] HADOOP-9122 Add power mock library for writing better unit tests

ards, > > Eric > > > > From: Andrew Wang <andrew.w...@cloudera.com> > Date: Friday, September 29, 2017 at 1:55 PM > To: Chris Douglas <cdoug...@apache.org> > Cc: Eric Yang <ey...@hortonworks.com>, "common-dev@hadoop.apache.org" > <common

[jira] [Created] (HADOOP-14897) Loosen compatibility guidelines for native dependencies

Chris Douglas created HADOOP-14897: -- Summary: Loosen compatibility guidelines for native dependencies Key: HADOOP-14897 URL: https://issues.apache.org/jira/browse/HADOOP-14897 Project: Hadoop Common

Re: Trunk fails

On Tue, Sep 19, 2017 at 8:55 AM, Allen Wittenauer wrote: > We need to get over this idea that precommit is going to find all > problems every time. Committers actually do need to spend some time with a > patch. Besides, in this particular case, it was

[jira] [Resolved] (HADOOP-14670) Increase minimum cmake version for all platforms

[ https://issues.apache.org/jira/browse/HADOOP-14670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved HADOOP-14670. Resolution: Fixed > Increase minimum cmake version for all platfo

Re: [DISCUSS] Can we make our precommit test robust to dependency changes while staying usable?

On Thu, Sep 14, 2017 at 1:43 PM, Ray Chiang wrote: > The other solution I've seen (from Oozie?) is to re-run just the subset of > failing tests once more. That should help cut down the failures except for > the mostly flaky of flakies. Many of our unit tests generate random

Re: [DISCUSS] Can we make our precommit test robust to dependency changes while staying usable?

This has gotten bad enough that people are dismissing legitimate test failures among the noise. On Thu, Sep 14, 2017 at 1:20 PM, Allen Wittenauer wrote: > Someone should probably invest some time into integrating the HBase > flaky test code a) into Yetus and

Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)

d that it shouldn't be enabled in secure environments. How are users supposed to make this determination without it? > Vote still continue until a real blocker comes. Soright. I remain -1. -C > ________ > From: Chris Douglas <cdoug...@apache.org> > Sent: M

Re: [VOTE] Release Apache Hadoop 2.8.2 (RC0)

-1 (binding) I don't think we should release this without YARN-6622. Since this doesn't happen often: a -1 in this case is NOT a veto. Releases are approved by majority vote of the PMC. -C On Mon, Sep 11, 2017 at 11:45 AM, Junping Du wrote: > Thanks Mikols for notifying

Re: Question about how to best contribute

Lars- Welcome! As a mild refinement of enthusiasm for this proposal: when you approach a "cleanup", please consider the cost to tracing the lineage of changes in the codebase. Working on a project as large and long-running as Hadoop, we often need to trace what motivated a particular change

[jira] [Created] (HADOOP-14742) Document multi-URI replication Inode for ViewFS

Chris Douglas created HADOOP-14742: -- Summary: Document multi-URI replication Inode for ViewFS Key: HADOOP-14742 URL: https://issues.apache.org/jira/browse/HADOOP-14742 Project: Hadoop Common

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

+1 (binding) Looked through the src tarball. Checksum and signature match, skimmed NOTICE/LICENSE, ran some unit tests. -C On Sat, Jul 29, 2017 at 4:29 PM, Konstantin Shvachko wrote: > Hi everybody, > > Here is the next release of Apache Hadoop 2.7 line. The previous

[jira] [Created] (HADOOP-14726) Remove FileStatus#isDir

Chris Douglas created HADOOP-14726: -- Summary: Remove FileStatus#isDir Key: HADOOP-14726 URL: https://issues.apache.org/jira/browse/HADOOP-14726 Project: Hadoop Common Issue Type: Task

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

gt; On Mon, Jul 31, 2017 at 3:56 PM Chris Douglas <cdoug...@apache.org> wrote: > >> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko >> <shv.had...@gmail.com> wrote: >> > For the packaging, here is the exact phrasing from the sited >> release-policy &

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko wrote: > For the packaging, here is the exact phrasing from the sited release-policy > document relevant to binaries: > "As a convenience to users that might not have the appropriate tools to > build a compiled version of

[jira] [Resolved] (HADOOP-14354) SysInfoWindows is not thread safe

[ https://issues.apache.org/jira/browse/HADOOP-14354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved HADOOP-14354. Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 3.0.0-alpha3 +1 lgtm

CVE-2017-3162: Apache Hadoop DataNode web UI vulnerability

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 CVE-2017-3162: Apache Hadoop DataNode web UI vulnerability Severity: Important Vendor: The Apache Software Foundation Versions affected: Hadoop 2.6.x and earlier Description: HDFS clients interact with a servlet on the DataNode to browse the

CVE-2017-3161: Apache Hadoop NameNode XSS vulnerability

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 CVE-2017-3161: Apache Hadoop NameNode XSS vulnerability Severity: Important Vendor: The Apache Software Foundation Versions affected: Hadoop 2.6.x and earlier Description: The HDFS web UI is vulnerable to a cross-site scripting (XSS) attack

Re: Can we update protobuf's version on trunk?

On Wed, Mar 29, 2017 at 4:59 PM, Stack wrote: >> The former; an intermediate handler decoding, [modifying,] and >> encoding the record without losing unknown fields. >> > > I did not try this. Did you? Otherwise I can. Yeah, I did. Same format. -C >> This looks fine. -C >> >>

Re: Can we update protobuf's version on trunk?

On Wed, Mar 29, 2017 at 1:13 PM, Stack wrote: > Is the below evidence enough that pb3 in proto2 syntax mode does not drop > 'unknown' fields? (Maybe you want evidence that java tooling behaves the > same?) I reproduced your example with the Java tooling, including changing some

Re: Can we update protobuf's version on trunk?

On Tue, Mar 28, 2017 at 4:18 PM, Andrew Wang wrote: > Unfortunately, it sounds like these are intrinsic differences with PB3. That's too bad... but possibly not fatal: most of the data we proxy through client code is, if not opaque, it's at least immutable (particularly

Re: Can we update protobuf's version on trunk?

On Tue, Mar 28, 2017 at 3:04 PM, Andrew Wang wrote: > There's no mention of the convenient "Embedded messages are compatible with >> bytes if the bytes contain an encoded version of the message" semantics in >> proto3. > > > I checked the proto3 guide, and I think this

[jira] [Created] (HADOOP-14225) Remove xmlenc dependency

Chris Douglas created HADOOP-14225: -- Summary: Remove xmlenc dependency Key: HADOOP-14225 URL: https://issues.apache.org/jira/browse/HADOOP-14225 Project: Hadoop Common Issue Type

[jira] [Resolved] (HADOOP-13037) Refactor Azure Data Lake Store as an independent FileSystem

[ https://issues.apache.org/jira/browse/HADOOP-13037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved HADOOP-13037. Resolution: Fixed Target Version/s: 2.8.0 (was: 2.9.0) Committed through

[jira] [Reopened] (HADOOP-13037) Refactor Azure Data Lake Store as an independent FileSystem

[ https://issues.apache.org/jira/browse/HADOOP-13037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas reopened HADOOP-13037: Reopening for backport to branch-2. Talked to [~djp], and will backport to branch-2.8

Re: [VOTE] Release Apache Hadoop 3.0.0-alpha2 RC0

On Wed, Jan 25, 2017 at 11:42 AM, Andrew Wang wrote: > Chris and Karthik, could you clarify the contingency of your votes? Is > fixing just the release notes sufficient? My +1 was not contingent on any changes. The release is fine as-is. Fixing any subset of the

Re: [VOTE] Release Apache Hadoop 3.0.0-alpha2 RC0

On Mon, Jan 23, 2017 at 9:32 PM, Allen Wittenauer wrote: > The problem here is that there is a 'license' directory and a file called > 'LICENSE'. If this gets extracted by jar via jar xf, it will fail. unzip > can be made to extract it via an option like -o. To

Re: [VOTE] Release Apache Hadoop 3.0.0-alpha2 RC0

Thanks for all your work on this, Andrew. It's great to see the 3.x series moving forward. If you were willing to modify the release notes and add the LICENSE to the jar, we don't need to reset the clock on the VOTE, IMO. What's the issue with the minicluster jar [1]? I tried to reproduce, but

Re: [VOTE] Release cadence and EOL

On Fri, Jan 20, 2017 at 2:50 PM, Sangjin Lee wrote: > The security patch for the 2.6.x line is a case in point. Without any > guideline, we would start with "What should we do for 2.6.x? Should we > continue to patch it?" With this guideline, the baseline is already "it's > been

Re: [VOTE] Release cadence and EOL

Sorry, I'd missed the end of the EOL discussion thread. As several people have pointed out, this is unenforceable. The release dates on the front page are a decent signal for liveness... do we need something more formal? All these hypothetical situations would be decided with more context. The

[jira] [Created] (HADOOP-13895) Make FileStatus Serializable

Chris Douglas created HADOOP-13895: -- Summary: Make FileStatus Serializable Key: HADOOP-13895 URL: https://issues.apache.org/jira/browse/HADOOP-13895 Project: Hadoop Common Issue Type: Bug

Re: [VOTE] Release Apache Hadoop 2.6.5 (RC0)

+1 Verified checksum and signature. Unpacked the jar, started single-node HDFS cluster, did some cursory checks. Read through the commit log from 2.6.4; particularly happy to see HADOOP-12893. -C On Tue, Sep 27, 2016 at 1:28 PM, Sangjin Lee wrote: > Hi folks, > > I have

Re: new look site

Reverted, resized to the same height as the original, pushed. -C On Tue, Sep 27, 2016 at 11:27 AM, Chris Douglas <chris.doug...@gmail.com> wrote: > Sure, I'll revert. Sorry, I'd only checked the main page, looked close > enough. -C > > On Tue, Sep 27, 2016 at 10:34 AM, And

Re: new look site

Sure, I'll revert. Sorry, I'd only checked the main page, looked close enough. -C On Tue, Sep 27, 2016 at 10:34 AM, Andrew Wang wrote: > Can we revert that change until we can get the site fixed? > > On Tue, Sep 27, 2016 at 10:06 AM, Steve Loughran

[jira] [Resolved] (HADOOP-13184) Add "Apache" to Hadoop project logo

[ https://issues.apache.org/jira/browse/HADOOP-13184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved HADOOP-13184. Resolution: Fixed Hadoop Flags: Reviewed I committed this. Thanks Abhishek! >

[jira] [Created] (HADOOP-13626) Remove distcp dependency on FileStatus serialization

Chris Douglas created HADOOP-13626: -- Summary: Remove distcp dependency on FileStatus serialization Key: HADOOP-13626 URL: https://issues.apache.org/jira/browse/HADOOP-13626 Project: Hadoop Common

Re: [VOTE] Merge HADOOP-13341

+1 (also on JIRA) -C On Wed, Sep 7, 2016 at 6:44 AM, Allen Wittenauer wrote: > > I’d like to call for a vote to run for 5 days (ending Mon 12, 2016 > at 7AM PT) to merge the HADOOP-13341 feature branch into trunk. This branch > was developed exclusively by

Re: [DISCUSS] Release numbering semantics with concurrent (>2) releases [Was Setting JIRA fix versions for 3.0.0 releases]

> I'm certainly open to alternate proposals for versioning and fix versions, > but to reiterate, I like this versioning since it imitates other enterprise > software. RHEL has versions like 6.2 Beta 2 and 7.0 Beta, so versions like > 3.0.0-alpha1 will be immediately familiar to end users.

Re: [DISCUSS] Release numbering semantics with concurrent (>2) releases [Was Setting JIRA fix versions for 3.0.0 releases]

I agree with Konst. The virtues of branching (instead of releasing from trunk) and using the version suffix for the 3.x releases are lost on me. Both introduce opportunities for error, in commits, in consistent JIRA tagging, in packaging... We can mark stability on the website. If someone builds

Re: Not being able to add HDFS contributors

I had the same problem. Infra was able to add them, but I kept getting an error. -C On Tue, Jul 19, 2016 at 2:29 PM, Zheng, Kai wrote: > Hi, > > I tried many times in the week at different time but just found it's not > possible to add more HDFS contributors. I can add some

Re: Why there are so many revert operations on trunk?

Reading through HDFS-9924, a request for a design doc- and a -1 on committing to trunk- was raised in mid-May, but commits to trunk continued. Why is that? Shouldn't this have paused while the details were discussed? Branching is neutral to the pace of feature development, but consensus on the

[jira] [Created] (HADOOP-13184) Add "Apache" to Hadoop project logo

Chris Douglas created HADOOP-13184: -- Summary: Add "Apache" to Hadoop project logo Key: HADOOP-13184 URL: https://issues.apache.org/jira/browse/HADOOP-13184 Project: Hadoop Common

[jira] [Created] (HADOOP-13175) Remove hadoop-ant from hadoop-tools

Chris Douglas created HADOOP-13175: -- Summary: Remove hadoop-ant from hadoop-tools Key: HADOOP-13175 URL: https://issues.apache.org/jira/browse/HADOOP-13175 Project: Hadoop Common Issue Type

Re: every JIRA is now getting a no-longer-employed message

I unsubscribed Randy from common-dev@. -C On Thu, May 5, 2016 at 6:36 AM, Mark Holderbaugh wrote: > FYI Randy is no longer with Yahoo.I will ping Yahoo Inc IT to try and get his > account to stop responding > It will also be great if a moderator for common-dev and

Re: Looking to a Hadoop 3 release

If we're not starting branch-3/trunk, what would distinguish it from trunk/trunk-incompat? Is it the same mechanism with different labels? That may be a reasonable strategy when we create branch-3, as a release branch for beta. Releasing 3.x from trunk will help us figure out which

Re: Branch policy question

On Sat, Mar 26, 2016 at 7:08 AM, Steve Loughran wrote: > Oh,I concur: but as we allow a single +1 for stuff done on, say, github, > we've actually got a higher standard for merging in patches from forks within > the ASF repo than there are from outside. The standard is

Re: Branch policy question

CTR is- and always has been- admissible in a branch. On Wed, Mar 23, 2016 at 2:11 PM, Steve Loughran wrote: > Given that only one +1 is needed to merge a non-branch patch, he could in > theory convert the entire branch into a single .patch for review. Not that > I'd

Re: Hadoop encryption module as Apache Chimera incubator project

equirements will put more challenges >>and uncertainties in where and how it should go, thus more risk in >>stalling. >> >>>> If the encryption libraries are the only ones you're interested in >>>>pulling out, then Apache Commons does seem like a better targ

Re: [DISCUSS] Looking to a 2.8.0 release

With two active sustaining branches (2.6, 2.7), what would you think of releasing trunk as 3.x instead of pushing 2.8? There are many new features (EC, Y1197, etc.), and trunk could be the source of several alpha/beta releases before we fork the 3.x line. -C On Sat, Sep 26, 2015 at 12:49 PM,

Re: CHANGES.TXT

On Mon, Sep 14, 2015 at 1:09 PM, Andrew Wang wrote: > I put some time into this a little while back, doing releasedocmaker > backports from the Yetus branch. IIRC from Allen, we still need to get lint > mode working before it's good to go. Probably a good bit of JIRA

Re: IPv6 Feature branch

+1 I don't suppose you could be conned into fixing multi-NIC and other networking issues also? ;) Do you have a list of contributors who plan to work on this feature? -C On Mon, Aug 17, 2015 at 5:04 PM, Elliott Clark ecl...@apache.org wrote: Nate (nkedel) and I have been working on IPv6 on

[jira] [Resolved] (HADOOP-9882) Trunk doesn't compile

[ https://issues.apache.org/jira/browse/HADOOP-9882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved HADOOP-9882. --- Resolution: Invalid Trunk doesn't compile - Key

Re: [DISCUSS] Additional maintenance releases for Hadoop 2.y versions

On Wed, Jul 15, 2015 at 2:07 PM, Sean Busbey bus...@cloudera.com wrote: Alternatively, why not appoint a Release Manager for the minor release line and then allow them to arbitrate when there's disagreement about inclusion? This has worked well in the HBase community. Release managers aren't

[jira] [Resolved] (HADOOP-9272) use macrodef and optimize build.xml

[ https://issues.apache.org/jira/browse/HADOOP-9272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved HADOOP-9272. --- Resolution: Won't Fix use macrodef and optimize build.xml

[jira] [Created] (HADOOP-12180) Move ResourceCalculatorPlugin from YARN to Common

Chris Douglas created HADOOP-12180: -- Summary: Move ResourceCalculatorPlugin from YARN to Common Key: HADOOP-12180 URL: https://issues.apache.org/jira/browse/HADOOP-12180 Project: Hadoop Common

Re: [DISCUSS] project for pre-commit patch testing (was Re: upstream jenkins build broken?)

+1 A separate project sounds great. It'd be great to have more standard tooling across the ecosystem. As a practical matter, how should projects consume releases? -C On Mon, Jun 15, 2015 at 4:47 PM, Sean Busbey bus...@cloudera.com wrote: Oof. I had meant to push on this again but life got in

[jira] [Resolved] (HADOOP-11747) Why not re-use the security model offered by SELINUX?

[ https://issues.apache.org/jira/browse/HADOOP-11747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved HADOOP-11747. Resolution: Invalid Please direct questions like this to the mailing list. JIRA

Fwd: [jira] [Created] (REEF-216) Protocol Buffers 2.5 no longer available for download

The Hadoop build instructions[1] also no longer apply. -C [1] https://git-wip-us.apache.org/repos/asf?p=hadoop.git;a=blob;f=BUILDING.txt -- Forwarded message -- From: Markus Weimer (JIRA) j...@apache.org Date: Fri, Mar 20, 2015 at 5:33 PM Subject: [jira] [Created] (REEF-216)

Re: Looking to a Hadoop 3 release

On Fri, Mar 6, 2015 at 4:32 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: I'd encourage everyone to post their wish list on the Roadmap wiki that *warrants* making incompatible changes forcing us to go 3.x. This is a useful exercise, but not a prerequisite to releasing 3.0.0 as an

Re: Looking to a Hadoop 3 release

On Mon, Mar 2, 2015 at 11:04 PM, Konstantin Shvachko shv.had...@gmail.com wrote: 2. If Hadoop 3 and 2.x are meant to exist together, we run a risk to manifest split-brain behavior again, as we had with hadoop-1, hadoop-2 and other versions. If that somehow beneficial for commercial vendors,

Re: Patch review process

+1; ChrisN's formulation is exactly right. The patch manager can't force (or shame) anyone into caring about your issue. One of the benefits of RTC is that parts of the code with a single maintainer are exposed. If you can't find collaborators, either (a) this isn't the right community for that

Re: Patch review process

On Wed, Feb 11, 2015 at 2:04 PM, Steve Loughran ste...@hortonworks.com wrote: At the same time, if only 1 person is looking at a part of the codebase submitting patches, they have inherently recused themselves from reviewing on their own patches. Ideally you want 1 committer tracking a

[jira] [Resolved] (HADOOP-11423) [Umbrella] Support Java 10 in Hadoop

[ https://issues.apache.org/jira/browse/HADOOP-11423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved HADOOP-11423. Resolution: Later Let's wait for Java 10 to be announced. [Umbrella] Support Java 10

Re: Patch review process

consistency across Apache has benefits. Issue INFRA-2205 has the discussion. The issue is closed, but there is recent discussion in the comments. https://issues.apache.org/jira/browse/INFRA-2205 Chris Nauroth Hortonworks http://hortonworks.com/ On 2/2/15, 3:56 AM, Chris Douglas cdoug

Re: Patch review process

, 2015, at 12:10 PM, Chris Douglas cdoug...@apache.org wrote: Release managers are just committers trying to roll releases; it's not an enduring role. A patch manager is just someone helping to track work and direct reviewers to issues. The job doesn't come with a hat. We could look into a badge

  1   2   >