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

Fix newest sort slowness and wrong record number #1371

Merged

Conversation

AlexisSouquiere
Copy link
Collaborator

  • Added a check to stop polling the topic when we are the end offset. It prevents user from experiencing a latency = akhq.topic-data.poll-timeout parameter the first time you try to see the topic content with NEWEST sort
  • Fixed the first offset of the search that was causing inconsistency between akhq.topic-data.size and the number of records displayed (returning one more record by partition than expected) when using pagination (no issues on the first page but starting at page 2 we were receiving one more record by partition)

- Fixing wrong number of records with pagination
@tchiotludo tchiotludo merged commit c470b97 into tchiotludo:dev Feb 9, 2023
@tchiotludo
Copy link
Owner

thanks a lot 🚀

@PavelYadrov
Copy link

Hello @tchiotludo, could you please tell, approximately, when is the next release?
We have a problem with Newest sorting and waiting for this fix

@tchiotludo
Copy link
Owner

I've this issue that is blocking the release for now: #1381

@mrMigles
Copy link

mrMigles commented Apr 4, 2023

Hi,
@tchiotludo, we're also interesting in AKHQ version with this fix, and as I can see #1381 already closed.
Could you please help us to understand approximately date of release with this fix?
Thank you!

tchiotludo pushed a commit that referenced this pull request Apr 4, 2023
- Adding stop condition in newest sort to prevent extra polling 
- Fixing wrong number of records with pagination

close #192
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants