Closed turboFei closed 1 week ago
the recent protobuf java versions introduced "runtime jar version" and "generated code version" check, it may affect the case: if we pull a thrid-party dependency that contains the generated protobuf code, we should be careful on bumping protobuf runtime jars version. For the Celeborn case, please also test Ratis gRPC mode when bumping protobuf versions.
For ratis:
The protobuf is shaded and the shaded.protobuf.version
is 3.24.4 in ratis 3.1.1 and 3.1.2
https://github.com/apache/ratis/blob/45a30d890451a44ec918fdee2732c5fff80ea17c/pom.xml#L216C1-L217C1
Will test celeborn.master.ha.ratis.raft.rpc.type=grpc
.
@pan3793 how about adding the UT with grpc mode?
The protobuf is shaded in ratis and the shaded.protobuf.version is 3.24.4 in ratis 3.1.1 and 3.1.2.
it should has no issue if ratis uses a shaded protobuf
What changes were proposed in this pull request?
Bump protobuf from 3.21.7 to 3.25.5.
Why are the changes needed?
To fix CVE: https://github.com/advisories/GHSA-735f-pc8j-v9w8
Does this PR introduce any user-facing change?
No.
How was this patch tested?
GA.