pan3793 commented on PR #56660: URL: https://github.com/apache/spark/pull/56660#issuecomment-4775032683
> so does this upgrade not fix the build? @HyukjinKwon I think so. Actually, the log4j community claimed to have fixed the issue in 2.26.0, but later withdrew and claims this would be fixed in 2.27.0. You can read the conversion in https://github.com/apache/spark/pull/51719 for more information. And again, this is unrelated to JDK 25, it's a pure log4j bug. I think the safe choice for now is to downgrade log4j2 to 2.24.3 (for functionality perspective), but this means we will bring the CVE back - direct CVE links can be found in https://mvnrepository.com/artifact/org.apache.logging.log4j/log4j-core/2.24.3 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
