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
I inspected the messages websocket and confirmed that the message that was displayed came from the backend. I suspect what is returned is simply what Kafka stores internally, but I was wondering if it's possible to strip out these types when deserializing from an Avro schema?
The text was updated successfully, but these errors were encountered:
@chrisjbremner I just pushed a commit that potentially fixes this. Could you give it a spin? If this hasn't fixed it I'm afraid I can't do much about it and in that case it might make sense to submit an issue in the repo of the go-avro client maintained by Linkedin.
Looks like someone already made one (linkedin/goavro#167) there's linkedin/goavro#201 that fixes this, but it's been open for a while and hasn't been merged
I noticed that on the topic detail page, if I have a topic with the following Avro schema:
Then when a message is displayed in the topic detail page, it shows up as:
Ideally, it would display as:
I inspected the
messages
websocket and confirmed that the message that was displayed came from the backend. I suspect what is returned is simply what Kafka stores internally, but I was wondering if it's possible to strip out these types when deserializing from an Avro schema?The text was updated successfully, but these errors were encountered: