The GitHub Actions job "CI" on pekko-connectors.git/hbase-testing-util has failed. Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run: d4f9ac1c63e120e7edcbb9a7ccea174d676fc83b / PJ Fanning <[email protected]> Run the hbase tests against an in-JVM mini cluster The hbase tests ran against harisekhon/hbase:2.1, an unmaintained image whose newest tag is from 2018. Being stuck on a server that old is what makes an hbase client upgrade look impossible: hbase 3 clients default to RpcConnectionRegistry, and a 2.1 master has no ClientMetaService to answer them. hbase-shaded-testing-util starts a mini ZooKeeper, mini HDFS, master and region server inside the test JVM, which is how hbase itself, Phoenix and the Spark and Flink hbase connectors test. It runs the same code paths a real cluster runs, and it is the flavour of testing-util that pairs with the hbase-shaded-client we already depend on. The client versions are unchanged at 2.6.6. Two settings are needed to get the cluster up on a current JDK: the master and region server web UIs are switched off, because their JAXB stack needs java.lang opened to reflect; and the WAL provider is set to filesystem, because the default asyncfs writer reflects into protobuf internals in a way the shaded hbase/hadoop combination does not survive. ZooKeeper is pinned to its default port, so a plain HBaseConfiguration.create() reaches the cluster and the documentation snippets stay unchanged. Local run: 14 tests (7 scala, 7 java) pass in about 80s, no docker. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Report URL: https://github.com/apache/pekko-connectors/actions/runs/33960984744 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
