Skip to content
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

[bug]topic messages show incorrect string value #4461

Closed
4 tasks done
hashkey-ops-admin opened this issue Jun 20, 2024 · 3 comments
Closed
4 tasks done

[bug]topic messages show incorrect string value #4461

hashkey-ops-admin opened this issue Jun 20, 2024 · 3 comments
Labels
status/triage Issues pending maintainers triage type/bug Something isn't working

Comments

@hashkey-ops-admin
Copy link

Issue submitter TODO list

  • I've looked up my issue in FAQ
  • I've searched for an already existing issues here
  • I've tried running master-labeled docker image and the issue still persists there
  • I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

The topic messages show incorrect string value as we use fastjson to serialize the topic message like this:

RecordMetadata recordMetadata = producer.send(<TOPIC_NAME>, JSON.toJSONString(message)).get();

We expected to see topic message like this:

{
      "userId":1712238412889623552,
      "totalStatus":2,
      "time":1718850732154,
      "msgId":"b00976ea-ab16-4ac5-8e23-4f8a4194b5c4"
}

However, we got message like this on kafka-ui:

{
	"msgId": "b00976ea-ab16-4ac5-8e23-4f8a4194b5c4",
	"time": 1718850732154,
	"totalStatus": 2,
	"userId": 1712238412889623600
}

As you can see, the userId is different.
Can u help check why this happened? Looks like it's due to something wrong happens during the deserialization of Long type to string(the userId is in Long type).

Expected behavior

No response

Your installation details

We deployed kafka-ui with docker image, this image is:

provectuslabs/kafka-ui latest cf4ebffbd785 11 months ago 260MB

Current time is 2024/06/20 UTC, we didn't see any bug fix in this year(2024).

Steps to reproduce

You could produce topic message like what I described in the detail part and check it on kafka-ui, then you should get the different userId.

Screenshots

No response

Logs

No response

Additional context

No response

@hashkey-ops-admin hashkey-ops-admin added status/triage Issues pending maintainers triage type/bug Something isn't working labels Jun 20, 2024
Copy link

Hello there hashkey-ops-admin! 👋

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. 👀

@Haarolean
Copy link
Contributor

Hi, PTAL at #4255
And I believe we fixed this here: https://github.com/kafbat/kafka-ui

@hashkey-ops-admin
Copy link
Author

@Haarolean Appreciate for ur quick answer.
I've tried the latest image from ghcr.io/kafbat/kafka-ui:latest and it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/triage Issues pending maintainers triage type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants