kafka-ui
kafka-ui copied to clipboard
Messages pagination is broken
Describe the bug In case Topic has 100+ messages, only 100 are displayed
Set up http://master.internal.kafka-ui.provectus.io/
Pre-conditions:
- Create a Topic
- Add 100+ messages to Topic
Steps to Reproduce
- Navigate to Topics
- Turn to Messages
- Make sure 100 messages are displayed
- Scroll down
- Press "Next" to turn to next page
Actual behavior The same 100 messages are displayed
Expected behavior On each page should be displayed corresponding count of Messages
Screenshots
https://user-images.githubusercontent.com/104780608/209350091-1fec5758-c70a-4f26-a12b-3189ab435fee.mov
To be done after #3504
In my opinion this is a pretty important bug that should be prioritized - my (and I imagine many other people's) primary use case for kafka-ui is to be able to view messages in a sane/convenient UI and only being able to view 100 messages for any given topic is a major flaw. Thanks!
Same problem here with the v0.7.1 every time the same messages are browse and when you sort in oldest first it's even worse because UI consume a huge amount of messages to sort them and when you go to next page it re-consume everything again
I've temporarily deployed an old (probably insecure) version of kafka-ui that didn't have this bug to get around this issue for my personal testing, in case anyone else wanted to try that.
Hi, @musabshak
Can you tell me what version you fixed this issue with?
I keep going down to lower versions, but it's not working. (I use Chart 6.2 version)
@95jinhong there wasn't a readily available helm chart at the version i had to go down to to avoid the bug so i had to do some manual helm chart modifications from what i remember.
the commit i have running that doesn't have this bug is: https://github.com/provectus/kafka-ui/commit/521ba0c
i see that i have chart version 0.4.4 but i manually override the image to be: image: docker.io/provectuslabs/kafka-ui:521ba0cb2f63110eb2ed13a7054a4d70238a862a
It is quite silly that I have to do this workaround to get what is in my opinion the core feature of this app the work lol. Thankfully I'm only testing locally so I don't have to worry about security vulnerabilities I am exposing myself to.
@musabshak This is exactly what I wanted~! I'll only be using it on my internal network, so I don't see a problem.
Cheers
For anyone interested, I merged the MessagesV2 API changes and implemented the respective UI changes to support the new API in my fork. It solves all the pagination and sorting issues with the current master branch. I also applied most of the updates for the packages to reduce the vulnerabilities. There is also a docker image under my name. I am not a UI engineer so don't expect a lot on the implementation itself :). Hopefully once the active development is back we will get a better version of it. Fork is at https://github.com/gimral/kafka-ui Image is at https://hub.docker.com/r/gimral/kafka-ui/tags
It is quite silly that I have to do this workaround to get what is in my opinion the core feature of this app the work lol. Thankfully I'm only testing locally so I don't have to worry about security vulnerabilities I am exposing myself to.
Bugs do exist and applications' features, even the core ones, tend to become broken sometimes.
Besides, for the attention of whom it may concern, here's an announcement published in September regarding the project's state: https://github.com/provectus/kafka-ui/discussions/4255
Also, all the issues regarding messages have been addressed here: https://github.com/kafbat/kafka-ui/releases/tag/v1.0.0