Closed shivakumarss closed 4 years ago
Edit :
It turned out to be bug in the confluent cloud UI. I have validated the data in the consumer and its fine.
References : https://groups.google.com/g/confluent-platform/c/3pSU1TsNg3A/m/7wNWu27UAAAJ https://stackoverflow.com/questions/63826163/confluent-cloud-java-avro-serialization-junk-characters-in-value https://github.com/confluentinc/examples/issues/780#issuecomment-690233778
Closing this ticket.
i am using this client to create the schema and send avro messages to topic. This works fine in my local machine ( macOS ) and in my GCP compute unit where downloaded version of confluent is running.
After the trails i got the confluent cloud access and tried with basic avro serialization doesnt seems to work as expected. The value section is always prefixed with junk characters and doesn't have the same behaviour which worked out in my local machine and my GCP single machine.
Here is the details and code snippet and the process which is followed.
sample_topic_003
Golang Code snippet for sending the data to confluent cloud
value.id
andvalue.name
but i get only value having prefixed with junk character.I believe it is as per confluent wire order doc where first byte is 0 and then 1-4 bytes are of schema ID and then the actual message. ( https://docs.confluent.io/current/schema-registry/serdes-develop/index.html#wire-format )
The same program works for in my local setup ( macOX ) and in my GCP where confluent is installed. following is the screenshot of the same.
The output of my client program when ran in my local setup .
Console output of my local setup
Notes :