-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Support deserializing binary protobuf encoded message keys #1699
Comments
Hello there jdechicchis! 👋 Thank you and congratulations 🎉 for opening your very first issue in this project! 💖 In case you want to claim this issue, please comment down below! We will try to get back to you as soon as we can. 👀 |
Hey, thanks for reaching out! Glad you like it. Let's discuss and we'll see about the PR. @iliax, what do you think? |
I am ok with this. Will be happy to review PR, @jdechicchis |
deserialized using a protobuf schema if the config is set. Otherwise message keys are treated as strings. Closes provectus#1699
@iliax @Haarolean Made a PR #1729. Would appreciate a review. I noticed that there didn't seem to be much documentation on how to use protobuf files with Kafka UI (maybe I missed it). I'm happy to document this change better if desired |
@jdechicchis hey, yeah, unfortunately there's not much documentation for this. Would appreciate any documentation improvements. |
@Haarolean Happy to add some docs in this PR (or a separate one if you prefer). I was thinking of adding a |
@jdechicchis would be cool! The same PR is fine, the path is okay as well. |
Updated the PR with some docs |
* Add protobufMessageNameForKeyByTopic option to config. Message keys are deserialized using a protobuf schema if the config is set. Otherwise message keys are treated as strings. Closes #1699 * Add documentation around kafkaui's protobuf support * Add protobufMessageNameForKey config option * Update README with info about default types * Imeplement support for protobufMessageNameForKeyByTopic * fallback to FALLBACK_FORMATTER * Add ability to publish message with protobuf key * Change log levels to debug and add @nullable annotations * Attempt at fixing documentation workflow Co-authored-by: Ilya Kuramshin <ilia-2k@rambler.ru> Co-authored-by: Roman Zabaluev <rzabaluev@provectus.com> Co-authored-by: Roman Zabaluev <github@haarolean.dev>
…us#1729) * Add protobufMessageNameForKeyByTopic option to config. Message keys are deserialized using a protobuf schema if the config is set. Otherwise message keys are treated as strings. Closes provectus#1699 * Add documentation around kafkaui's protobuf support * Add protobufMessageNameForKey config option * Update README with info about default types * Imeplement support for protobufMessageNameForKeyByTopic * fallback to FALLBACK_FORMATTER * Add ability to publish message with protobuf key * Change log levels to debug and add @nullable annotations * Attempt at fixing documentation workflow Co-authored-by: Ilya Kuramshin <ilia-2k@rambler.ru> Co-authored-by: Roman Zabaluev <rzabaluev@provectus.com> Co-authored-by: Roman Zabaluev <github@haarolean.dev>
First off, Kafka UI is great, thanks for maintaining it!
I noticed this TODO in
ProtobufFileRecordSerDe
:I think it would be nice to provide the ability to deserialize binary protobuf encoded message keys in addition to message values. To support this, I think a new configuration value such as
Map<String, String> protobufMessageNameByTopicForKey
could be added (open to suggestions here). In terms of how a message key is deserialized when usingProtobufFileRecordSerDe
I feel this precedence order would make sense:protobufMessageNameByTopicForKey
deserialize the message key using a descriptor.Happy to make a PR for this (I've been playing around with the code and doesn't seem like it would be terribly difficult to add), but wanted to discuss if adding such a configuration makes sense
The text was updated successfully, but these errors were encountered: