-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[kafkareceiver] - Add string unmarshaler #21730
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Pinging code owners for receiver/kafka: @pavolloffay @MovieStoreGuy. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Could you give more details as to why you believe string should be an encoding type? I am not exactly sure the difference to raw here. |
Yeah actually. I'm sending a string "Event" in kafka consumer and I receive "RXZlbnQ=" in Splunk Dashboard i.e. base64 encoding of "Event". |
See #20734 |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Closing as it's duplicate |
Component(s)
No response
Is your feature request related to a problem? Please describe.
I can't send and receive raw strings.
Describe the solution you'd like
Currently, if I use a console producer and console consumer, kafkareceiver only allows to unmarshal otlp, zipkin or jaeger.
If I'm just sending raw string, the only option I have is to select raw unmarshaler and it will send data in bytes.
It would be great to have a string unmarshaler.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: