Re: [DISCUSS] Increased use of feature branches

I would like to understand the trunk-incompat part of the proposal a little better. Is trunk-incompat always going to be a superset of trunk? If yes, is it just a change in naming convention with a hope that our approach to trunk stability changes as Sangjin mentioned? Or, is it okay for

[jira] [Created] (HDFS-10516) Fix bug when warming up multiple EDEKs

Xiao Chen created HDFS-10516: Summary: Fix bug when warming up multiple EDEKs Key: HDFS-10516 URL: https://issues.apache.org/jira/browse/HDFS-10516 Project: Hadoop HDFS Issue Type: Bug

Re: [DISCUSS] Increased use of feature branches

Thanks for your thoughts Anu. Regarding your question > And then comes the question, once 3.0 becomes official, where do we > check-in a change, if that would break something? so this will lead us > back to trunk being the unstable – 3.0 being the new “branch-2”. Andrew mentioned in the

Hadoop-Hdfs-trunk-Java8 - Build # 1333 - Still Failing

See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/1333/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 6221 lines...] [INFO] [INFO] ---

Build failed in Jenkins: Hadoop-Hdfs-trunk-Java8 #1333

See Changes: [aajisaka] HADOOP-13213. Small Documentation bug with AuthenticatedURL in -- [...truncated 6024 lines...] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:

Re: [DISCUSS] Increased use of feature branches

I actively work on two branches (Diskbalancer and ozone) and I agree with most of what Sangjin said. There is an overhead in working with branches, there are both technical costs and administrative issues which discourages developers from using branches. I think the biggest issue with branch

Build failed in Jenkins: Hadoop-Hdfs-trunk-Java8 #1332

See Changes: [wangda] YARN-3426. Add jdiff support to YARN. (vinodkv via wangda) [jing9] HADOOP-13249. RetryInvocationHandler need wrap InterruptedException in -- [...truncated 6007

Hadoop-Hdfs-trunk-Java8 - Build # 1332 - Failure

See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/1332/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 6204 lines...] [INFO] [INFO] ---

Re: Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

Interestingly, that FindBugs warning in hadoop-azure-datalake was not flagged during pre-commit before I committed HADOOP-12666. I'm going to propose that we address it in scope of HADOOP-12875. --Chris Nauroth On 6/10/16, 10:30 AM, "Apache Jenkins Server" wrote:

Jenkins build is back to normal : Hadoop-Hdfs-trunk-Java8 #1331

See - To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org

Re: [DISCUSS] Increased use of feature branches

Having worked on a major feature in a feature branch, I have some thoughts and observations on feature branch development. IMO feature branch development v. direct commits to trunk in piecemeal is really a choice of *granularity*. Do we want a series of fine-grained state changes on trunk or

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/58/ No changes -1 overall The following subsystems voted -1: findbugs unit The following subsystems voted -1 but were configured to be filtered/ignored: cc checkstyle javac javadoc pylint

Re: [DISCUSS] Increased use of feature branches

Thanks for the notes Andrew, Junping, Karthik. Here are some of my understandings: - Trunk is the "latest and greatest" of Hadoop. If a user starts using Hadoop today, without legacy workloads, trunk is what he/she should use. - Therefore, each commit to trunk should be transactional -- atomic,

Re: [DISCUSS] Increased use of feature branches

Inline. On Fri, Jun 10, 2016 at 6:56 AM, Junping Du wrote: > Comparing with advantages, I believe the disadvantages of shipping any > releases directly from trunk are more obvious and significant: > - A lot of commits (incompatible, risky, uncompleted feature, etc.) have >

[jira] [Created] (HDFS-10515) libhdfs++: Implement mkdirs, rmdir, rename, and remove

Anatoli Shein created HDFS-10515: Summary: libhdfs++: Implement mkdirs, rmdir, rename, and remove Key: HDFS-10515 URL: https://issues.apache.org/jira/browse/HDFS-10515 Project: Hadoop HDFS

Re: [DISCUSS] Increased use of feature branches

Comparing with advantages, I believe the disadvantages of shipping any releases directly from trunk are more obvious and significant: - A lot of commits (incompatible, risky, uncompleted feature, etc.) have to wait to commit to trunk or put into a separated branch that could delay feature

[jira] [Reopened] (HDFS-5805) TestCheckpoint.testCheckpoint fails intermittently on branch2

[ https://issues.apache.org/jira/browse/HDFS-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger reopened HDFS-5805: --- I've been able to get this test to fail consistently about 1/3 of the time on my local cluster. I checked

Hadoop-Hdfs-trunk-Java8 - Build # 1330 - Still Failing

See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/1330/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 7126 lines...] [INFO] [INFO] ---

Build failed in Jenkins: Hadoop-Hdfs-trunk-Java8 #1330

See Changes: [aajisaka] MAPREDUCE-6741. Refactor UncompressedSplitLineReader.fillBuffer(). -- [...truncated 6929 lines...] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/57/ [Jun 9, 2016 4:28:49 PM] (stevel) HADOOP-13237: s3a initialization against public bucket fails if caller [Jun 9, 2016 7:30:58 PM] (vinodkv) YARN-5191. Renamed the newly added “download=true” option for

Re: [DISCUSS] Increased use of feature branches

Thanks for restarting this thread Andrew. I really hope we can get this across to a VOTE so it is clear. I see a few advantages shipping from trunk: - The lack of need for one additional backport each time. - Feature rot in trunk Instead of creating branch-3, I recommend creating

[DISCUSS] Increased use of feature branches

Hi all, On a separate thread, a question was raised about 3.x branching and use of feature branches going forward. We discussed this previously on the "Looking to a Hadoop 3 release" thread that has spanned the years, with Vinod making this proposal (building on ideas from others who also