aIbrahiim commented on issue #39268: URL: https://github.com/apache/beam/issues/39268#issuecomment-4977953632
I looked into this workflow failures after the Java 21 bump and here's my findings: We get ServiceConfigurationError for org.apache.hadoop.hbase.shaded.org.xbill.DNS.spi.DnsjavaInetAddressResolverProvider not found After that, MiniZK / HBase client setup fails same root error for HBaseIOTest, HbaseIOWriteRowMutationsTest, and HBaseSharedConnectionTest. and I think the root cause is hbase-shaded-client / hbase-shaded-testing-util ship a service file META-INF/services/java.net.spi.InetAddressResolverProvider that points at a shaded dnsjava class, but that class is not actually loadable from the jar (shade / multi-release packing issue which is same kind of problem I found out as [HADOOP-19288](https://issues.apache.org/jira/browse/HADOOP-19288) / [dnsjava#338](https://github.com/dnsjava/dnsjava/issues/338)). so on Java 17 this SPI was not used the same way so tests passed but on Java 18+ InetAddress loads that SPI and blows up so --add-opens, JVM flags, or OpenModuleAgent. wont fix this so should we stop advertising that broken provider in the shaded jars (exclude that META-INF/services entry in the shade build, like HADOOP-19288), then release a new HBase version so beam can bump hbase_version after that? @Abacn -- 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]
