I think this is a problem for the 3.0.0 release. When upgrading to 2.0.0, we shaded the protobuf and upgrade the version to 3.x. But for coprocessor, the protobuf version is still 2.5.0, and we made a hbase-protocol module for it.
So we still keep this solution when releasing 3.0.0? Which means the protobuf version for coprocessor will always be 2.5.0? Seems not a good solution. And since we are allowed to make breaking changes on the CP hooks during major version, I think letting the CPs use a new version of protobuf is also fine? Suggestions? Thanks.
