-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Bug: cluster admin refresh medatadata report error when set Metadata.Full
to false.
#2069
Comments
Consider the following scenario: For a totally new Kafka cluster, there do not exist any topics yet, user tries to fetch metadata, then creates the topic by calling At the moment, this is not allowed, I think this is a bug. |
The docs do state:
I too don't get the intuition of that though. |
This comment was marked as outdated.
This comment was marked as outdated.
Thank you for taking the time to raise this issue. However, it has not had any activity on it in the past 90 days and will be closed in 30 days if no updates occur. |
Versions
When there is no topic in the Kafka cluster, metadata cannot be reported, if we set
Metadata.Full
to false.Please specify real version numbers or git SHAs, not just "Latest" since that changes fairly regularly.
Configuration
What configuration values are you using for Sarama and Kafka?
Logs
When filing an issue please provide logs from Sarama and Kafka if at all
possible. You can set
sarama.Logger
to alog.Logger
to capture Sarama debugoutput.
logs: CLICK ME
Problem Description
The text was updated successfully, but these errors were encountered: