-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
parseMessageMetadata error when broker entry metadata enable #10967
Labels
type/bug
The PR fixed a bug or issue reported a bug
Comments
yangl
pushed a commit
to yangl/pulsar
that referenced
this issue
Jun 23, 2021
apache#10968) Fixes apache#10967 ### Motivation fix parseMessageMetadata error cause by not skip broker entry metadata ### Modifications skip broker entry metadata if exist before parsing message metadata
eolivelli
pushed a commit
to datastax/pulsar
that referenced
this issue
Sep 6, 2021
apache#10968) Fixes apache#10967 ### Motivation fix parseMessageMetadata error cause by not skip broker entry metadata ### Modifications skip broker entry metadata if exist before parsing message metadata (cherry picked from commit 0774b5f)
bharanic-dev
pushed a commit
to bharanic-dev/pulsar
that referenced
this issue
Mar 18, 2022
apache#10968) Fixes apache#10967 ### Motivation fix parseMessageMetadata error cause by not skip broker entry metadata ### Modifications skip broker entry metadata if exist before parsing message metadata
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
If broker entry metadata enabled, we may get the following exception in many cases :
this problem also reported in :
#10950
#9255
#10924
this is caused by #9046,
Before #9046 code is
After #9046,
this PR removed code
So, this may cause exceptions when parseMessageMetadata
The text was updated successfully, but these errors were encountered: