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
Fix SegmentCompletionProtocol to ignore unknown json fields #5376
Conversation
Our compatibility guarantees are around upgrading the controller first and then the broker and then the server. So, it is possible that the controller sends a new field in the response (in SegmentCompletionProtocol) The server should ignore new fields that it does not understand
@@ -395,6 +396,7 @@ public SegmentStoppedConsuming(Params params) { | |||
public Response() { | |||
} | |||
|
|||
@JsonIgnoreProperties(ignoreUnknown = true) |
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.
This line should be added before line 388
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.
good catch, thanks
Issue #5359 This change must go into 0.4.0 |
@haibow please make sure this commit gets into 0.4.0 thanks |
Codecov Report
@@ Coverage Diff @@
## master #5376 +/- ##
==========================================
- Coverage 66.44% 56.97% -9.47%
==========================================
Files 1075 1079 +4
Lines 54773 55004 +231
Branches 8168 8237 +69
==========================================
- Hits 36396 31341 -5055
- Misses 15700 21190 +5490
+ Partials 2677 2473 -204
Continue to review full report at Codecov.
|
Our compatibility guarantees are around upgrading the controller first
and then the broker and then the server. So, it is possible that the
controller sends a new field in the response (in SegmentCompletionProtocol)
The server should ignore new fields that it does not understand