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

Extend / change API behavior for sending/receiving messages #11

Open
PHameete opened this issue Dec 5, 2018 · 0 comments
Open

Extend / change API behavior for sending/receiving messages #11

PHameete opened this issue Dec 5, 2018 · 0 comments
Assignees

Comments

@PHameete
Copy link
Contributor

PHameete commented Dec 5, 2018

Referring to #10

If you create a consumer for a topic, and produce a message for that topic directly afterwards on the same thread, you will likely not receive the message on the consumer.

This is not the behavior you would expect, and it also makes unit testing difficult.

Two possible solutions come to my mind:

  1. Make consumer creation synchronous by forcing it to fetch partition info before returning
  2. Allow consumers to fetch by offset specifically, and let producers return the offset of a produced message.
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

No branches or pull requests

2 participants