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

For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1468/ 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

[jira] [Resolved] (HADOOP-19161) S3A: option "fs.s3a.performance.flags" to take list of performance flags

[ https://issues.apache.org/jira/browse/HADOOP-19161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved HADOOP-19161. - Fix Version/s: 3.5.0 3.4.1 Resolution: Fixed > S3A: option "f

Re: Need help with gpg signing while creating 3.4.1 release using MacOS M3

On Fri, 26 Jul 2024 at 23:08, Mukund Madhav Thakur wrote: > Omg Steve already found and fixed the JAVA_HOME issue in create-release > for arm64 which I had to spend some time recently. > https://github.com/apache/hadoop/pull/6962 > i really don't remember that. Why did you have to repeat it...di

[DISCUSS] what needs to be done to switch to java17

A lot of projects are moving off java8. making java17 the new baseline what do we need to there that is blocker rather than just "nice"'?

Re: [DISCUSS] what needs to be done to switch to java17

I think this is worth considering. I think it would require a minor release like 3.5.0 as opposed to considering it for future 3.4.x patch releases. I tend to build locally with Java 11, by default and I haven't hit major issues building Hadoop. There may be some gotcha somewhere but it is likely t

Re: Need help with gpg signing while creating 3.4.1 release using MacOS M3

+ one thing to consider is you don't need to sign the macos releases, or publish to maven staging. all we want is that native lib hadoop release support takes the 86 tarball and builds a new tar with a different name, the lib swapped over but the exact same jar files, then signs it outside of the

Re: [DISCUSS] what needs to be done to switch to java17

Depends on what we mean by switching to JDK-17, Compile time support or Runtime support, We don't have compile time support for JDK-11 too, it is just runtime, We have a daily build as well for JDK-11, which has now some genuine failures now, need to check [1], as of now the version is hardcoded he

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

For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1653/ No changes -1 overall The following subsystems voted -1: blanks hadolint pathlen spotbugs unit xml The following subsystems voted -1 but were configured to be filtered/ignored: cc chec

Re: [DISCUSS] what needs to be done to switch to java17

Thank you very much for initiating this discussion! I am also very much looking forward to JDK 17. I have observed that using --add-opens= is quite common in other Apache projects. One thing I know is that it is necessary to upgrade JUnit 4 to JUnit 5. There are some JIRA issues currently being wor

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

For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java11-linux-x86_64/714/ No changes -1 overall The following subsystems voted -1: blanks hadolint mvnsite pathlen spotbugs unit xml The following subsystems voted -1 but were configured to be filtered/ignored:

Re: [DISCUSS] what needs to be done to switch to java17

Thanks, everyone, for starting this discussion. This sounds like a good plan to start with. As I was working on the JUnit 4 to 5 upgrade, I paused for a while as I got occupied with other stuff. But I would be happy to complete it as part of the Java switch process. On Tue, Jul 30, 2024 at 4:21 AM

[jira] [Created] (HADOOP-19241) NoSuchMethodError in aws sdk third party logger in hadoop aws 3.4

ashutoshraina created HADOOP-19241: -- Summary: NoSuchMethodError in aws sdk third party logger in hadoop aws 3.4 Key: HADOOP-19241 URL: https://issues.apache.org/jira/browse/HADOOP-19241 Project: Hado