serde: add Buf Schema Registry (BSR) protobuf support #2014
+1,299
−24
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit adds support for deserializing protobuf messages that use plain protobuf payloads but use Buf Schema Registry (BSR). Unlike Confluent Schema Registry which embeds schema information in the message payload, BSR stores schema metadata in Kafka record headers. The BSR wire format uses two headers to identify the schema: - buf.registry.value.schema.message: The fully-qualified message type - buf.registry.value.schema.commit: The schema version/commit hash The implementation includes: Backend Changes: - New BSRClient interface and HTTP client for fetching schemas from BSR - ProtobufBSRSerde for deserializing BSR-encoded messages - Configuration support for BSR endpoint URL and authentication token - Integration with existing serde service to automatically detect BSR messages - Comprehensive unit and integration tests Frontend Changes: - Added PAYLOAD_ENCODING_PROTOBUF_BSR enum value - Updated message preview components to display BSR encoding - Extended proto definitions and TypeScript interfaces The BSR serde is prioritized before other protobuf serdes in the deserialization pipeline since BSR messages are identifiable by their specific headers, allowing for efficient format detection. All existing tests pass and new tests verify BSR deserialization works correctly with dynamic protobuf messages.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit adds support for deserializing protobuf messages that use plain protobuf payloads but use Buf Schema Registry (BSR). Unlike Confluent Schema Registry which embeds schema information in the message payload, BSR stores schema metadata in Kafka record headers.
The BSR wire format uses two headers to identify the schema:
The implementation includes:
Backend Changes:
Frontend Changes:
The BSR serde is prioritized before other protobuf serdes in the deserialization pipeline since BSR messages are identifiable by their specific headers, allowing for efficient format detection.
All existing tests pass and new tests verify BSR deserialization works correctly with dynamic protobuf messages.