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

No errors or warnings when a topic does not exist and auto-create is off #348

Closed
skandragon opened this issue Aug 12, 2015 · 5 comments
Closed

Comments

@skandragon
Copy link

./rdkafka_example -b "broker-01:9092" -t flarg -p 0

My application also behaves the same way. Ideally, an error should be presented in some way to indicate this configuration is bogus.

@edenhill
Copy link
Contributor

Good point.
This will be propagated asynchronously, meaning:

  • consumer: returns rkmessage->err with UNKNOWN_TOPIC
  • producer: if produce() is called before internal metadata fetch is complete: dr_cb with err==UNKNOWN_TOPIC
  • producer: if produce() is called after internal metadata fetch is complete: will fail immediately and return err==UNKNOWN_TOPIC

@skandragon
Copy link
Author

Is that how it happens now, or how it will happen with a fix?

@edenhill
Copy link
Contributor

This is how it will happen very soon.

@edenhill
Copy link
Contributor

Or well, the producer behaviour is already like this, only the consumer needs adjusting.

@edenhill
Copy link
Contributor

There, that should do it. Please verify on your end too.

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

No branches or pull requests

2 participants