-
Notifications
You must be signed in to change notification settings - Fork 8.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HADOOP-19289. Protobuf-Java 3.25.5 #7072
Conversation
💔 -1 overall
This message was automatically generated. |
Let's do a new release of the third party lib before this |
With hadoop-thirdparty, can we call the next release 1.3.1? The upgrade from 1.3.0 isn't big. The current version is 1.4.0-SNAPSHOT. |
ok |
0f0398c
to
b911afc
Compare
💔 -1 overall
This message was automatically generated. |
failures look like race conditions, e.g. decommissioning failure
that is not protobuf related |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
I've seen those decommission tests fail in a few builds recently - in different PRs so not seemingly caused by the PR changes. Protobuf-Java 3.25.6 has just come out but has a major breaking change where it fails at runtime if you have Protobuf Generated Java code that is too old (ie generated with a fairly old version of protoc). Unfortunately, this doesn't seem uncommon. HBase looks like it will be quite affected. I came across the issue in Apache Pekko. The claim is that the old generated code is vulnerable to DoS. |
thirdparty update it is then -targeting 3.4.2, presumably. |
Description of PR
HADOOP-19289
How was this patch tested?
For code changes:
LICENSE
,LICENSE-binary
,NOTICE-binary
files?