@mattisonchao

LockManagerTest.acquireLocks:56 » NoClassDefFound Could not initialize class io.oxia.proto.ShardAssignmentsRequest

@mattisonchao The protobuf version used in oxia-client-java isn't compatible with Pulsar's protobuf version:
https://github.com/oxia-db/oxia-client-java/blob/e1ecf0a95b8df36e6bf7b13981540d2c4e786b9a/pom.xml#L79
There was a major version bump in protobuf from 3.x to 4.x fairly recently and it seems that there's no compatibility any more. Here's the announcement:
https://protobuf.dev/news/v26/#breaking-compatibility-with-old-generated-code

One possible way to solve this would be to have multiple sub modules in oxia-client-java for different protobuf versions.
The default could be for 4.x, but it could be possible to exclude the dependency and replace it with another dependency.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.17%. Comparing base (4a4e692) to head (ea8e8a4).
⚠️ Report is 7 commits behind head on master.

@@             Coverage Diff              @@
##             master   #24689      +/-   ##
============================================
- Coverage     74.38%   74.17%   -0.21%     
+ Complexity    33105    33084      -21     
============================================
  Files          1893     1895       +2     
  Lines        147811   147954     +143     
  Branches      17098    17130      +32     
============================================
- Hits         109950   109749     -201     
- Misses        29149    29459     +310     
- Partials       8712     8746      +34     

@mattisonchao This depends on #24438 for branch-3.0 and branch-3.3 . Is there a need to update Oxia support in those branches?