You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fail to parse InlongMessage when exporting Pulsar.
The reason is that DataProxy puts the InlongGroupId and InlongStreamId into the Pulsar header with the key "groupId" and "streamId" when the transmission protocol is InlongMessage V0.
While the key with InlongMessage V1 is "inlongGroupId" and "inlongStreamId", which leads to the null value when the pulsar sink handler tries to parse this information from the message header.
What you expected to happen
Parse correctly.
How to reproduce
Use InlongMessage V0 as the transmission protocol, and try to export Pulsar.
vernedeng
changed the title
[Bug][Sort] Fail to parse InlongMessage when exporting Pulsar and Kafka
[Bug][Sort] Fail to parse InlongMessage when exporting Pulsar
Oct 10, 2023
What happened
Fail to parse InlongMessage when exporting Pulsar.
The reason is that DataProxy puts the InlongGroupId and InlongStreamId into the Pulsar header with the key "groupId" and "streamId" when the transmission protocol is InlongMessage V0.
While the key with InlongMessage V1 is "inlongGroupId" and "inlongStreamId", which leads to the null value when the pulsar sink handler tries to parse this information from the message header.
What you expected to happen
Parse correctly.
How to reproduce
Use InlongMessage V0 as the transmission protocol, and try to export Pulsar.
Environment
No response
InLong version
master
InLong Component
InLong Sort
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: