-
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
Usage of ProtobufRawDecoder unclear #4382
Comments
Hello there PreNoob! 👋 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. 👀 |
We are stuck here too. How do you make this work? |
We were able to get this to work by using the |
coming back to this one to log my experience I tried to follow @pranavkapoorfanatics instructions and indeed running the I would like to reiterate @PreNoob initial suggestion, would be great to have proper documentation on how to setup/use the |
Got it working by using the latest helm chart from here https://artifacthub.io/packages/helm/kafka-ui/kafka-ui Added below env variables, worked like charm.
Yes, I believe documentation requires some update. |
hey @SubhraB, are you also using the |
Using helm chart version 1.4.5, I believe it is behind main, but it works. |
Issue submitter TODO list
master
-labeled docker image and the issue still persists thereDescribe the bug (actual behavior)
I want to use the ProtobufRawDecoder as mentioned in the docs here.
I configured it like so:
Resulting in the following error
After that I've checked the code for the protobuf raw serde and the name here is
ProtobufDecodeRaw
.results in a similar error
Adding
className: com.provectus.kafka.ui.serdes.builtin.ProtobufRawSerde
resulted in the following error:Expected behavior
I would like to have proper documentation on how to setup/use the
ProtobufRawDecoder
.Your installation details
Steps to reproduce
Deployed the helm chart with the above mentioned configuration.
Screenshots
No response
Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: