Re: [VOTE] Release Apache Hadoop 3.4.2

2025-08-20 Thread Anuj Modi
Hi, Ahmar Here are the PRs for the fix raised for ABFS close() causing NPE raised on RC. PR on branch-3.4.2: https://github.com/apache/hadoop/pull/7888 PR on branch-3.4: https://github.com/apache/hadoop/pull/7889 Feel free to merge them as per the release timelines. Thanks On Wed, Aug 20, 2025

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

2025-08-20 Thread Apache Jenkins Server
For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/2030/ [Aug 19, 2025, 12:36:06 AM] (github) HDFS-12431. [JDK17] Upgrade JUnit from 4 to 5 in hadoop-hdfs Part12. (#7873) [Aug 19, 2025, 12:43:50 AM] (github) HADOOP-19653. Bump ByteBuddy 1.17.6 and ASM 9.8

Re: [VOTE] Release Apache Hadoop 3.4.2

2025-08-20 Thread Steve Loughran
just discovering as I do the third party compatibility testing of the latest sdk that the fs.s3a.create.checksum.algorithm stuff is a bit broken -nothing to worry about though as its a new feature so not a regression On Wed, 20 Aug 2025 at 16:13, Suhail, Ahmar wrote: > Hey all, > > I've fixed th

Re: [VOTE] Release Apache Hadoop 3.4.2

2025-08-20 Thread Suhail, Ahmar
Hey all, I've fixed the following issues: 1) Issues with changelog, release notes and landing page. Created a new build so they now include all the JIRA's that were missing before. 2) Create the lean tar on ubuntu so you won't get the tar: Ignoring unknown extended header keyword 'LIBARCHIVE.xa

Apache Hadoop qbt Report: branch-2.10+JDK7 on Linux/x86_64

2025-08-20 Thread Apache Jenkins Server
For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1853/ No changes -1 overall The following subsystems voted -1: asflicense hadolint mvnsite pathlen unit The following subsystems voted -1 but were configured to be filtered/ignored: cc

Re: [VOTE] Release Apache Hadoop 3.4.2

2025-08-20 Thread Masatake Iwasaki
Since I have to regenerate the site and changelog, do I need to do the whole build again or is there an easier way to do that? (just by regenerating the site manually and updating the artifacts in SVN maybe?) I think just running the create-release[1] script could be an easy way while it does