This is an automated email from the ASF dual-hosted git repository.

pjfanning pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pekko-connectors.git


The following commit(s) were added to refs/heads/main by this push:
     new cc96893a0 Pin hbase to 2.x in scala-steward config (#1918)
cc96893a0 is described below

commit cc96893a00edb2dd5032c835dd38f5e84df4f66c
Author: PJ Fanning <[email protected]>
AuthorDate: Sun Sep 6 08:54:22 2026 +0100

    Pin hbase to 2.x in scala-steward config (#1918)
    
    hbase 3.0.0 changed the default connection registry from
    ZKConnectionRegistry to RpcConnectionRegistry. Our hbase tests build
    their config from a bare HBaseConfiguration.create(), so a 3.x client
    stops going to ZooKeeper and instead calls ClientMetaService on the
    master. The test server (harisekhon/hbase:2.1) predates that service
    and closes the connection, failing every hbase test.
    
    There is no newer published harisekhon/hbase tag and no official apache
    hbase image, so we cannot move the test server to 3.x, and a 3.x client
    against a 2.1 server is not a combination hbase supports in any case.
    
    Co-authored-by: Claude Opus 5 (1M context) <[email protected]>
---
 .scala-steward.conf | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/.scala-steward.conf b/.scala-steward.conf
index dad5d4976..4501c99ab 100644
--- a/.scala-steward.conf
+++ b/.scala-steward.conf
@@ -1,6 +1,9 @@
 updates.pin  = [
   # pin to hadoop 3.4.x until 3.5.x becomes more widely adopted
   { groupId = "org.apache.hadoop", version = "3.4." }
+  # hbase 3 clients default to RpcConnectionRegistry, which our test server
+  # (harisekhon/hbase:2.1, the newest published tag) is too old to serve
+  { groupId = "org.apache.hbase", version = "2." }
   # stick with solr 9 until 10 is more widely adopted
   { groupId = "org.apache.solr", version = "9." }
   # https://github.com/apache/pekko-connectors/issues/503


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to