[ISSUE #10284] Fix consumerOffset deserialization error#10287
[ISSUE #10284] Fix consumerOffset deserialization error#10287ChineseTony wants to merge 1 commit intoapache:developfrom
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #10287 +/- ##
=============================================
- Coverage 48.96% 48.88% -0.09%
+ Complexity 13464 13440 -24
=============================================
Files 1375 1375
Lines 100450 100452 +2
Branches 12973 12973
=============================================
- Hits 49183 49101 -82
- Misses 45268 45342 +74
- Partials 5999 6009 +10 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
793f4fd to
a444b8d
Compare
a444b8d to
8746274
Compare
|
ConsumerOffsetSerializeWrapper cannot generate setter lambda via JDK8 LambdaMetafactory when using fastjson2 2.0.61 |
|
This issue is caused by a FastJSON bug. It will be completely fixed once FastJSON releases an official patch. We adopt a temporary workaround for immediate mitigation. |
|
Sorry for the late reply. Just to confirm, this PR and #10283 are both trying to address #10284, but the approaches look different. #10283 changes the generic RemotingSerializable decode path, while this PR narrows the fix to the ConsumerOffset response shape. If we keep this approach, could we add a regression test covering the mixed offsetTable + pullOffsetTable response returned by GET_ALL_CONSUMER_OFFSET? |
Which Issue(s) This PR Fixes
Brief Description
Discussion about this fix: #10283
Problem Introduction
update fastjson2 version to avoid deserialization error
How Did You Test This Change?