We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
master
When resetting offsets of a consumer group by reset type "EARLIEST" the consumer group is reset to latest.
The same happens with the reset type "TIMESTAMP" and "OFFSET".
The topic offsets of the consumer group are set with the respective method chosen.
App version: 83b5a60 v0.7.2
Running inside a container as described here
No response
A green pop up, indicating that the reset has been successful, is shown after pressing the "Reset Offset" button.
The text was updated successfully, but these errors were encountered:
Hello there ges1227! 👋
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. 👀
Sorry, something went wrong.
This repo is not maintained (#4255). Happy to see your bug reports here: https://github.com/kafbat/kafka-ui
No branches or pull requests
Issue submitter TODO list
master
-labeled docker image and the issue still persists thereDescribe the bug (actual behavior)
When resetting offsets of a consumer group by reset type "EARLIEST" the consumer group is reset to latest.
The same happens with the reset type "TIMESTAMP" and "OFFSET".
Expected behavior
The topic offsets of the consumer group are set with the respective method chosen.
Your installation details
App version: 83b5a60 v0.7.2
Running inside a container as described here
Steps to reproduce
Screenshots
No response
Logs
No response
Additional context
A green pop up, indicating that the reset has been successful, is shown after pressing the "Reset Offset" button.
The text was updated successfully, but these errors were encountered: