jtuglu1 commented on PR #18759: URL: https://github.com/apache/druid/pull/18759#issuecomment-3554529369
> > Odd. All UT/IT tests passed. Is there a way we can somehow conditionally enable this so people who don't use hadoop ingests get the benefit of a newer compiler? Doesn't seem ideal to be stuck on JDK 11 compiler for a feature that has been deprecated. This could be done potentially with the hadoop maven profiles. > > If i understand things correctly, I think the issue is that it would allow using language level 17 features in Druid code which is what would actually break hadoop ingestion. We don't officially support java 11 anymore, but hadoop ingestion still works because none of the parts that run there need java 17 only stuff yet. Is there a way to just detect to use JDK 11 compiler when a Hadoop profile is being used? This way the project doesn't stagnate and isn't pinned down by deprecated features (for example, enabling virtual thread or other JDK 17+ features). -- 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]
