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 utilizing the official Kafka Client with Schema Registry enabled, messages produced include a leading 0 followed by the next 4 bytes representing the SchemaId. Consequently, the actual message content begins at byte 6 (index 5).
The TriggerMesh KafkaSource currently overlooks this behavior, resulting in the generated events being invalid JSON. As a consequence, these events are NULL cannot be processed successfully.
Steps to Reproduce
Enable Schema Registry for the Kafka Client.
Produce messages using the Kafka Client.
Observe the leading 0 and SchemaId in the message structure.
Trigger the KafkaSource in a scenario where it consumes these messages.
Expected Behavior
The KafkaSource should handle messages produced with Schema Registry, recognizing the leading 0 and SchemaId, and correctly extracting the actual message content from byte 6 onwards.
Actual Behavior
The KafkaSource does not account for the Schema Registry format, resulting in invalid JSON events that cannot be processed.
Issue Description
When utilizing the official Kafka Client with Schema Registry enabled, messages produced include a leading 0 followed by the next 4 bytes representing the SchemaId. Consequently, the actual message content begins at byte 6 (index 5).
The TriggerMesh KafkaSource currently overlooks this behavior, resulting in the generated events being invalid JSON. As a consequence, these events are NULL cannot be processed successfully.
Steps to Reproduce
Expected Behavior
The KafkaSource should handle messages produced with Schema Registry, recognizing the leading 0 and SchemaId, and correctly extracting the actual message content from byte 6 onwards.
Actual Behavior
The KafkaSource does not account for the Schema Registry format, resulting in invalid JSON events that cannot be processed.
Code from the Confluent Kafka Go Client
JsonSerializer
Serde
The text was updated successfully, but these errors were encountered: