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
When creating a changefeed with Kafka sink, the codec will be used to encode RowChangedEvent into a message. At the moment, TiCDC support several different codec protocols, we should make sure all protocol can handle the content of RowChangedEvent correctly, especially the Column.Value field, which is an interface.
What did you expect to see?
All protocols can handle Column.Value field correctly, but some failed.
What did you see instead?
The server panic.
Versions of the cluster
Upstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):
Most recent bug report happened in v5.4.0, but we should check all release branches.
What did you do?
When creating a changefeed with Kafka sink, the codec will be used to encode
RowChangedEvent
into a message. At the moment, TiCDC support several different codec protocols, we should make sure all protocol can handle the content ofRowChangedEvent
correctly, especially theColumn.Value
field, which is an interface.What did you expect to see?
All protocols can handle
Column.Value
field correctly, but some failed.What did you see instead?
The server panic.
Versions of the cluster
Upstream TiDB cluster version (execute
SELECT tidb_version();
in a MySQL client):Most recent bug report happened in
v5.4.0
, but we should check all release branches.Related issues
Canal-JSON / Canal
unsigned
intostring
, causecanal-json
panic. #4635Open protocol
test
unsigned
to integration test #4787The text was updated successfully, but these errors were encountered: