clintropolis commented on PR #18977: URL: https://github.com/apache/druid/pull/18977#issuecomment-3839877718
>why not jdk25 which is the LTS after jdk 21? supporting 25 is a bit non-trivial at this point, any extension that uses hadoopy stuff (hdfs storage, parquet, avro, orc readers) will fail with an error related to https://docs.oracle.com/en/java/javase/24/security/security-manager-is-permanently-disabled.html, when i was testing i saw something like ``` java.lang.UnsupportedOperationException: getSubject is not supported at java.base/javax.security.auth.Subject.getSubject(Subject.java:277) ~[?:?] at org.apache.hadoop.security.UserGroupInformation.getCurrentUser(UserGroupInformation.java:577) ~[?:?] at org.apache.hadoop.fs.FileSystem$Cache$Key.<init>(FileSystem.java:3884) ~[?:?] at org.apache.hadoop.fs.FileSystem$Cache$Key.<init>(FileSystem.java:3874) ~[?:?] at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3662) ~[?:?] at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:557) ~[?:?] at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:290) ~[?:?] at org.apache.druid.storage.hdfs.HdfsStorageDruidModule.configure(HdfsStorageDruidModule.java:96) ~[?:?] at ``` I believe hadoop 3.5.0 will fix this if i understand https://issues.apache.org/jira/browse/HADOOP-19744 correctly, so i suppose it is possible we could have this fixed in time for 37... though that would also i think technically eliminate the need to actually remove hadoop indexing from druid (though i think if we don't delete it we should move it to be an actual contrib extension so it isn't bundled by default, which hopefully shouldn't be all that much work after #18247). Regardless of 25 support, I think it is fine to move forward with this PR, we are just making a commitment that either we will delete hadoop indexing before 37 (i totally volunteer to do this... it sounds very satisfying), or if 3.5.0 is released and fixes the problems. I created #18980 to help track 25 support. -- 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]
